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

FSXA recent concerns

jyarddog

jyarddog

Messages
2,388
Country
us-washington
I always mess around making FS9 stuff work in FSX, fairly successful but many problems, as you know. Usually one will see the trees with black boxes around them. go to MCX and find the trees in the library, and in texture editor you see the black boxes. We change that with “set default transparency” and it changes and all is well. then you can export mdl or export scenery and save the whole library.
Lately I have seen the trees with the false background.... go to MCX, do the above and you already see the trees trans looking ok in MCX!!!! and it ALREADY says ‘always’, ‘greater’ and ‘128’ (as if it has already been corrected- but it hasn’t).
Anyway- since seasonal from FS9 don’t work I change the textures to just plain trees.bmp This does work. I save the thing as export scenery which saves the whole library. BUT- if I do so I lose about 200 kb out of the library! .... maybe something small, but it bothers me. I tried saving as FSX bgl and also tried FS9 bgl (i.e. xtomdl vs makemdl) – no difference- still lose something there. Recently did this on some other scenery and I lost TONS of hangars and such. In the game I still had the library which IS3 found and I could replace each lost item if I wanted, but I chose to reload the orig lib and leave it be. any ideas why this stuff happens and the other questions above? Bob
 
Hi Bob,

Even if you load a fs2004 mdl ModelConverterX will try to set the right material settings if it detects a transparent texture.

About the smaller file. Like you said maybe some seasonal tuning was lost, that had most likely been made by manual asm tweaking. So the compilers don't support it.

But missing whole buildings. Did you get a box to set variables at the start? Could be some buildings have conditions and you set the variables for those conditions to be false.
 
So MCX will now try to set the proper trans if it detects one? In the past I would see a tree with a black box. I would then set default trans and the trans would be corrected. I then go to FSX and see trees with good trans. Now the trees still show with the false background even though MCX showed them as corrected.

The seasonals problem I expected since this is a change from FS9 scenery to FSX. I merely switched the texture from a _wi to a su or rather just the straight bmp. This worked as expected.
There were many variable boxes. I never touch those. Evidently if I see a variable in those boxes that say false I should change them to 'true"? (I assume this means to change the 0 to a 1 where it says 'value'?) Bob

--------------------------
In those boxes on the left whenever it said 33B the value was 0. anything else seemed to have a 1. I just tried changing the 33B to value 1. made my changes and compiled- No change still lost kbs. Original size is 1257. After switching the trees from tres_wi.bmp to trees.bmp the new size of the library in 1067. In FSX I can't tell what I lost. It seems that it may be something very small and not really noticeable.
[In the recent past I lost tons of stuff! <------ But the library still showed up with IS3 and I could, if needed, manually replace lost items using IS3. ]
 
Last edited:
33B is the distance to the object, so 0 should give the most detailed representation normally. Maybe some of the other variables resulted in parts missing.
 
Last time I compiled, I did so as FSX bgl (xtomdl) and lost only about 100 kb. ..... more acceptable. Just can't understand, why the trans shows fine in a fs9 item in MCX but does not show fixed in FSX. Bob
 
You must log in or register to reply here.
Back
Top