• 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 Model Converter error?

wideloadwhitford

wideloadwhitford

Messages
628
Country
unitedstates
I cannot explain what is going on here. Someone did mention similar files names before but I have changed the textures names and I get the same result.I have a total of 7 textures and it only outputs 4 in MDX. Has anyone ever seen this before?

mdx1.jpg


mdx2.jpg


Also if its relevant, these are my Export options.

gmaxk.jpg


Thanks, Ryan
 
Last edited:
Hi,

The only reason I can think of is that the other textures have been filtered out. But that would only happen if they are perpendicular to the ground (then they can not be projected on the ground correctly).
 
Ryan- just got your email about the .gmax file, and it's incredibly ironic that I have gotten the same problem with our scenery in the past few days.... :mad:

Arno- I can verify that the same problem is happening to me (in fact, I was about to start a new thread, but good thing that I checked this first). I simply added another layer as usual, gave it a texture, and the new layer does not show up in the layer box, even though it does in the viewport, which is strange.
 

Attachments

  • Capture1.jpg
    Capture1.jpg
    76.8 KB · Views: 445
  • Capture2.jpg
    Capture2.jpg
    104.5 KB · Views: 464
Hi,

Can any of you two send me a file that has this problem for debugging? Then I will take a look at it.
 
Hi,

I am not sure what is happening there. When I export the scene again I also seem to miss some materials. So that seems like a problem of the gamepack (if they are not in the MDL, MCX will never show them).

But with your GMax file loaded, my GMax is crashing all the time. So I can't investigate further.
 
Hi,

I have no idea. I never encountered this before. Not sure if the missing textures can have anything to do with it.
 
Arno,
I did extensive trial-and-error (3 hours) testing yesterday, and the results were surprising and throws you into circular logic:

1. I went into my LHZ ground file and added another layer as usual. I compiled this and the new layer DID show in the MCX ground dialog.

2. I then went into my MYR file (problem) and added the desired layer, compiled, and it did NOT show in the Mcx ground dialog.

3. Next, I went into the CSG ground (other problem) and added a new layer. I then opened MCX and the NEW test layer was in the dialog box, yet the layer that I need to show to make the runway appear darker did NOT. So basically the newer layer was read, but not all layers.

4) I tested all MDLs in an older version of MCX, and got the same results.

Here comes the fun part: circular logic.

If the problem was Mcx, then why would it work just fine for some but not others, which would make you think that it was a problem with the export. However, if there was an exporting problem, why would it work at all on any file and why would MCX draw that layer in the viewport? But if the old MCX gets the same error, that would indicate a problem with the model. Also, if it was the mdl, how ironic would it be that both Ryan and I got the same error at the same time? Stuff just isn't adding up.

I then thought that it may have to do with the fact that I used a jpg for the texture instead of .psd like I normally do. However, I soon realized that the ramp-light layer I needed at MYR was jpg, but the darker asphalt layer at CSG is in .psd format, so it wasn't reading specific layers with .psd or .jpg even though those texture types are already used elsewhere in those MDLs.

One last ditch effort: could installing the p3d sdk for 3dsmax have an effect on the fsx sdk for gmax?

Ryan- have you even installed the sdk for 3ds max? If so, I could somehow, some way, see a correlation, but other than that, no clue.

Arno, Hope this helps...


Sent from my iPhone using Tapatalk
 
I have not installed the 3ds gamepack. But I had this problem with my terminal also.

I just put my Terminal into the fs2004 gamepack and exported it, then opened it in MDX and all the textures show up. However, when I put the same .gmax file into the FSX Gamepack and export it, the results are not the same in MDX. Out of 7 textures only 3 show up. Something is wrong with gmax I believe but why would it start doing this now?
 

Attachments

This is only speculation but Microsoft wouldn't have been so cruel as to set a date that the SDK would cease to work would they.........?


Sent from my iPhone using Tapatalk
 
Hi,

I think it might be a case of the FSX gamepack being more picky on how you define your materials. I have read of naming issues resulting in wrong exports before. Sounds a lot like that.
 
You must log in or register to reply here.
Back
Top