-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
FSDS 3 texture problem
- Thread starter croplus
- Start date
Check your bitmaps and make sure they aren't 24 bit. 24 bit textures will show in FSDS, but won't work in FS.
Scattered parts from FSDS can be fixed in a few different ways. You can export .x file from FSDS and compile is manually. You can try dragging each part axis to the center of the model (hold the shift key while dragging to move the axis). Another method is to pick a parent part and link the others to it.
Scattered parts from FSDS can be fixed in a few different ways. You can export .x file from FSDS and compile is manually. You can try dragging each part axis to the center of the model (hold the shift key while dragging to move the axis). Another method is to pick a parent part and link the others to it.
adr179
Resource contributor
- Messages
- 259
- Country
Hey guys, read this:http://www.scenerydesign.org/forum/showthread.php?t=2520
topic so You'll be able to envise the gravity of this problem. My textures were definitely not 24bit and all this actually has nothing to do with the textures formats by itself.
topic so You'll be able to envise the gravity of this problem. My textures were definitely not 24bit and all this actually has nothing to do with the textures formats by itself.
adr179
Resource contributor
- Messages
- 259
- Country
As sure as I can be. In the DS I'm looking at a perfectly "dressed up" model of a low poly aircraft, but when exported as a scenery model, some polys of a part that has a part texture asignment are textured and others are not
.Something like that never happened with ver 2.
Just guessing out loud: if some of us have this problem and others don't, what is that people with problems have in common OS wise?
I guess this would be close to impossible to find out. I have two PC's with quite different configurations of software installed, but results are the same on both.
.Something like that never happened with ver 2. Just guessing out loud: if some of us have this problem and others don't, what is that people with problems have in common OS wise?
I guess this would be close to impossible to find out. I have two PC's with quite different configurations of software installed, but results are the same on both.
Last edited:
I think I had a simular problem a few weeks ago.
You copied the texture name into the Texture dialog?
This will show up in FSDS but the part will not have a rference to the texture list.
Open all parts or polygons and add the texture from the texture list.
After this work you can see your model also textured in FS
You copied the texture name into the Texture dialog?
This will show up in FSDS but the part will not have a rference to the texture list.
Open all parts or polygons and add the texture from the texture list.
After this work you can see your model also textured in FS
adr179
Resource contributor
- Messages
- 259
- Country
But this are basics of design in FSDS and, yes ALL this steps were done twice from the original file that hadn't had any textures assigned, texture name added
to the texture list, texture path added in the project properties , ALL parts had textures assigned to them (just adding texture name to the texture list does nothing to the part or poly texturing). Furthermore the same was tried on my other comp. - results are the same.
Interestingly enough, another fsd file also from same source, but with texture
assignments present works out fine.
to the texture list, texture path added in the project properties , ALL parts had textures assigned to them (just adding texture name to the texture list does nothing to the part or poly texturing). Furthermore the same was tried on my other comp. - results are the same.
Interestingly enough, another fsd file also from same source, but with texture
assignments present works out fine.
The interesting thing is, that your tires are textured.
So there seems to be a mistake done when you textured the rest of the bus.
If you textured all of the bus by clicking into the texture list and all textures have the correct format in your texture folder then I do not have any further idea...
Sorry
So there seems to be a mistake done when you textured the rest of the bus.
If you textured all of the bus by clicking into the texture list and all textures have the correct format in your texture folder then I do not have any further idea...
Sorry
How do you select your texture. I have had the same problem using Part Texture assignment (F4) some times the textures dosen't show up in FS. But if I select textures via polygon texture then i works. It takes more time, but it works every time....
Hope it helps
Claus
Hope it helps
Claus
adr179
Resource contributor
- Messages
- 259
- Country
Great! The only problem here is, that the aircraft I'm having problem with has
1265 polys and I really don't want to spend the rest of my life texturing it!
But as I already mentioned something is sypthomatic (keep in mind, I'm converting other's people sources, mostly designed in FSDS 2): I have no problems with the project files that had the textures already assigned and I can check and see that those were assigned as part textures. After some lighter arrangements and rescaling to meters (they were mainly designed with unit feet), I get a nicely looking static aircraft with low to modest number of polys, that compile as scenery mdl, so I can place them with bglcomp using compilation xml file.
But in case of the Saratoga fsc, there were no textures assigned, so I made my own template, started asigning textures as part textures to the project file and got a nicely looking "dressed up" aircraft. I bielieve, that if something really is wrong with my procedure, it would already show up in the design, but so far everthing looks fine. The problem is, that only after the compilation the final result in the simulation is as already described. Since already three members of this forums reported having the same problem, the explanation can't be so simple, that all three of us are doing the same mistake.
But if version 3 of FSDS works for some people and it doesn't work for some others we are doomed, because finding out the reason for this behaviour is next to impossible with millions of possible combinations of software we have on our machines. So, I'm again asking if there is someone who would be willing to try to solve my problem. I can send both the *.fsc and texture files to a person interested to help.
1265 polys and I really don't want to spend the rest of my life texturing it!
But as I already mentioned something is sypthomatic (keep in mind, I'm converting other's people sources, mostly designed in FSDS 2): I have no problems with the project files that had the textures already assigned and I can check and see that those were assigned as part textures. After some lighter arrangements and rescaling to meters (they were mainly designed with unit feet), I get a nicely looking static aircraft with low to modest number of polys, that compile as scenery mdl, so I can place them with bglcomp using compilation xml file.
But in case of the Saratoga fsc, there were no textures assigned, so I made my own template, started asigning textures as part textures to the project file and got a nicely looking "dressed up" aircraft. I bielieve, that if something really is wrong with my procedure, it would already show up in the design, but so far everthing looks fine. The problem is, that only after the compilation the final result in the simulation is as already described. Since already three members of this forums reported having the same problem, the explanation can't be so simple, that all three of us are doing the same mistake.
But if version 3 of FSDS works for some people and it doesn't work for some others we are doomed, because finding out the reason for this behaviour is next to impossible with millions of possible combinations of software we have on our machines. So, I'm again asking if there is someone who would be willing to try to solve my problem. I can send both the *.fsc and texture files to a person interested to help.
Last edited:
I think Claus hit the nail on the head. I don't use F4 part texturing for anything other than a simple box shape. I've been using polygon texturing for anything complex. Maybe that's the reason I haven't had any problems. Once the object has lots of polys with different orientations, F4 won't cut it.
I use PArt Texturing more than poly Texturing and you can belevieve me it works! If possible send the file to me and I will have a look.
I have some time this afternoon but will be out of the office on the weekend!
Please think of also sendng the Texture Files, otherwise I have more problems
I have some time this afternoon but will be out of the office on the weekend!
Please think of also sendng the Texture Files, otherwise I have more problems
- Messages
- 26
- Country
I think there may be a subtle incompatibility between FSDS vsersions 2 & 3. I upgraded to v3 partway through building a model of the Tyne bridge, and some parts failed to display correctly in fs9 with some polygons appearing untextured.
I found the only way to fix this was to create the affected parts afresh in FSDSv3 - simply retexturing the parts didn't work for me.
I'm afraid this is a rather negative message - I'd be very pleased to find out if someone has a real solution!
Cheers,
Chris
I found the only way to fix this was to create the affected parts afresh in FSDSv3 - simply retexturing the parts didn't work for me.
I'm afraid this is a rather negative message - I'd be very pleased to find out if someone has a real solution!
Cheers,
Chris
I have successfully imported several complex FSDSv2 scenery projects into V3 and never had the described texture problems. The one thing I did learn that if I was going to remap the textures in V3 be sure you clear the left -over v2 textures. The bus at the start of this thread looks like what happens when a texture has been applied but is of the wrong format. Can't be sure without the texture file and .fsc.
Cheers---------Paul
Cheers---------Paul
- Messages
- 305
- Country
Well I can assure you that Abacus has no interest in fixing this problem.
Three emails later with no reply for a month, they don't care. It's only up to the owners of these products to try to find a solution.
I have had the same frustrating problem, moved me to learn Gmax with no luck.
I tried making a video to show Abacus what is going on,
http://media.putfile.com/FSDS-Problem
but they still didn't give a reply.
From now on I am refusing to purchase products from Abacus because of their lousy and poor customer/technical service.
Three emails later with no reply for a month, they don't care. It's only up to the owners of these products to try to find a solution.
I have had the same frustrating problem, moved me to learn Gmax with no luck.
I tried making a video to show Abacus what is going on,
http://media.putfile.com/FSDS-Problem
but they still didn't give a reply.
From now on I am refusing to purchase products from Abacus because of their lousy and poor customer/technical service.
