• 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.

FSX textures not postioned

robystar

robystar

Messages
5,214
Hi,

I am not sure if this has anything to do with MCX or that there is something funny going on with GSU but I do no longer seem to be able to have the textures of my object positioned in MCX.
To make it clear what I mean:
1st screenshot is of the GSU skp and the 2nd one is when I import the dae in MCX and exchange the texture0 by the foto.bmp. If I convert it to dds through the mass texture converter it is flipped horizontally.
Can anyone check this out please?
Thanks,

Roby

PS I did not have this problem a couple of days ago and I did install the latest dev releases.
 
Last edited:
Hi,

Well I figured it out.
I loaded this bmp photo into GSU and so GSU makes a folder in documents including this bmp. So far so good except that MCX does not load this texture when it is a bmp and when I want to load the bmp from another location, MCX does not position the image any longer.
But when I change the texture0.bmp into texture0.jpg then it loads and positions the texture correctly.
 
Hi Arno,

Have you drowned?:)
The fact that an imported photo.bmp is not rendered by MCX is a pita.
It means having to convert the bmp into a jpeg for MCX to recognize it, back up the bmp and exchange it for the jpg and place it in the GSU document folder before MCX is able to visualize its positioning.
Any changes to the jpeg or conversion to another format results in MCX not rendering it probably positioned.
Something you did, has changed the normal procedure :confused:.
 
Hi Roby,

I was in Germany for my work most of the week.

This is a weird issue. The position of the texture has nothing to do with the format it is read from. So I am guessing it might find a different texture with the same name somewhere else on the search path.

Do you have an example object that shows this behaviour so that I can debug it?
 
Morning Arno,

Sorry, I cannot give you a sample object. I changed the original one and got rid of the bmp texture for it.
It boiled down to the fact that when I imported the Dae into MCX, the texture0.bmp GSU made, did not show up. Instead there was a random texture (probably from another texture0). In the material editor the diffuse texture is indeed texture0.bmp but does not show the right texture. When removing the entry and replacing it by the texture0.bmp from the documents folder of the object that GSU made, the texture shows but not positioned. When I change the texture0.bmp to texture0.jpg, it is positioned correctly again.
Well, that confused me quite a bit.
Later on I found out that even although MCX did not show a correct positioning, it was postioned correctly in FSX after conversion with the mass texture editor and exported as mdl.
 
OK. Maybe more a SketchUp issue in that case. But happy to hear you found a work around by now :).
 
arno said:
OK. Maybe more a SketchUp issue in that case. But happy to hear you found a work around by now :).
Click to expand...

Hi Arno,

Here's another odd issue with textures on objects imported frrom Sketchup; it's probably something in Sketchup, but on reading this thread I thought I would mention it.

I've confirmed the following a number of times now; If in Sketchup I import an image, then color a surface and use the color picker to match a color in the image, --- and then delete the picture -- I continue to see my chosen new color correctly in Sketchup. But when I import the object into MCX, that surface is invisable. Strange. Took me a while to figure out the cause.

Maybe it's not MCX, but it does mean I can't use this method to match colors.

Larry
 
Hi Larry,

Do you have the latest development release? About a week ago or so there was a bug with colours not being read correctly from the COLLADA file.

If you have the latest version already, can you send me a model with this issue for testing?
 
Hi Arno,

Just to be sure, I downloaded the latest version as of now, but still the same issue. However, after more experimenting it appears that if I try to match a color on any surface in my latest Sketchup model by using the color picker on a texture image that I have imported (say the side view of the boat), that surface is invisable in MCX. Reversing surfaces, coloring both sides, re-doing the surface, etc, does not work. That is, it does not matter if I had deleted the image used to match the color or not.

If however I color the surface with one of the built-in colors and just match my desired color by eye, the surface displays properly.

One more thing I just noticed: with the last two builds, on exporting the model with the offending color from MCX, I would get an 'unhandled' error message, but if I clicked continue, the export was successful although with a missing a surface. Once I just matched the color on the surface in question by eye, no more error message.

I can Email the model to you if it would still be helpful.

Larry
 
Hi Larry,

Thanks, I got your model. I see the material becomes completely transparent, that's why you don't see the polygons anymore. But according to the COLLADA specs that is correct, I feel SketchUp exported the material wrong.

You can always manually edit the material in the ModelConverterX material editor. By removing the alpha value from the color they show fine.
 
Hi Arno

Thanks so much for looking into this!

I guess the summary then is: unless you want to use the material editor in MCX, when working in Sketchup, and you wish to match a color in an imported image or texture, don't use the 'match color on screen' feature (on the image) on the Edit tab in the Materials window. It's really not a big deal if you know.

Larry
 
You must log in or register to reply here.
Back
Top