• 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 latest dev. releases texture problem

robystar

robystar

Messages
5,214
Hi Arno,

Having dowloaded the latest development releases I encountered some difficulties in rendering textures the last couple of days.
At first I thought it was because MCX could not find the textures, so I deleted all texture search paths and put in only the one that referred to the mdl in question, but no textures showed. Then I tried a bgl and no textures showed either.
Today I downloaded your latest dev. release and deleted all former instances of MCX before installing the new one.
But no textures are showing.
I also noticed that, although I deleted all previous instances of MCX the texture search path is still the one that I chose before.
Can you help me out because it is probably me that is doing something wrong here as I have not seen anybody else mentioning this.

Tks,

Roby

PS I see no show day and night options any longer either.
 
Last edited:
Hi,

I'll take a look later today. Maybe the two updates I did earlier this week broke something.

About the search path. As long as you install the new version in a folder with the same name your settings are carried over.
 
Hi Arno,

Apparently to erase the entries in the texture search path was not a good idea.
I had to delete the MCX user config folder in the user\app data\ local low folder (took a while to find it) to get the original search path entries back.
I also deleted the latest dev. release and installed an older one.
Now everything works again.
Still have to find out if it also works in the newest dev rel. but just wanted to let you know: do not bother to check it as it was almost definitely due to my deleting the default entries in the texture search path.
Roby

Update:
- textures now also show in latest dev.rel.
- but still no sign of an option for day view and night view.
 
Last edited:
Hi Roby,

I see the bar to control some of the preview settings is indeed hidden, going to fix that ASAP.
 
Fixed it now, so the development release that will be online in about 30 minutes should be working fine again.
 
Thank you Arno, all seems to work beautifully now.
I was also at first missled but then pleasantly surprised by the updated mass converter workings (It got rid of some textures and I was wondering if I had accidentally deleted them until I saw a texture.cfg instead).
I also managed to add a Gmax made rotating radar mdl to my Sketchup made mdl using the LOD maker but it is somewhat difficult to position the extra mdl.
I therefore used the attached object editor to find the coordinates for the spot the radar had to be placed at and then moved it there.
I wonder if there is an easier way?

Roby
 
Hi Roby,

I think at the moment there is no easier way. The import LOD function assumes both objects have the same origin already, but to make it a more general merge function it would indeed be useful if you can specify an offset. I'll put that on the wishlist :).
 
You must log in or register to reply here.
Back
Top