• 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 SDK and gmax

Messages
549
Country
nicaragua
A good friend gave me the possibility to start making FSX aircraft, but I have lots of doubts to be cleared yet, for example:
When I create a new FSX material, I have to go to maps, diffuse and then select the texture map.
But when I apply it to the model the model turns grey, like gmax's native materials.
The plane I used to make this experiment was my Su-26, which, as you may have noticed, was mapped and working fine with the FS9 SDK.
So why does this happen when I switch to the FSX material?

Another thing:
I export an untextured object with FSX SDK and the screen freezes and the only way to solve that is by terminating the task.
Why does that happen?

Thanks in advance! :)
 
Make sure you have the blue and white checkered button 'depressed' (on) for your materials to show up. If it is not 'on', the material will be plain gray.
 
I export an untextured object with FSX SDK and the screen freezes and the only way to solve that is by terminating the task.
Why does that happen?

Thanks in advance! :)

I havent heard of the screen freezing before. But I would definately make sure most of your parts are textured and mapped before putting them in FSX as FSX will show them in pure black and sometimes they stack up into the center CG of the plane.
 
Thanks!
The freezing is really weird:
That bar on the bottom of the gmax's UI fills until 89% and then gmax freezes when the dialog of the X to mdl should appear...
 
The true expert at XtoMDL, Bill Leaming, is at OshKosh presently. He could better explain it and possibly know what it is. Give him several days to get back and read it if no one else chimes in.


Bill
 
Ok, so now I have this problem:
Su-26_issue.jpg
See the differences on the lightning of the plane...
This didn't happen before I added reflection or bump map...
I even thought it was different materials applied, but no...
Can you help me!? :confused:
 
This happens to me when I do not have the Bump Map correct.

You need all of the components of the FSX 'high realism' texture to get it to work right. What you are seeing is the aileron is shaded upside down. I think you have an 'old' texture in there and the aileron is still mapped to it. Make sure all the exterior has the new Texture mapped to it. Same with the landing gear struts.


With the extreme FSX textures (bump mapping, reflections, speculars), you need each of the textures in there, and done right. If the Bump map isnt done right, this can happen also.

Here are all 5 of a typical regular textures using the FSX material system.

Diffuse Color texture
Bump map
Illumination map (optional)
Specular Color texture
GlobalEnv_AC_Chrome texture

I just use a gray texture sometimes for the Specular map, a light gray texture. The Bump map is the main thing here, and it appears that your fuselage and wings are 'proper' from what I can see..



Bill
 
So, you're saying that I need to make all the maps (specular, bump and diffuse) and all have to be in DDS right? It's because the diffuse texture is still a bitmap...
Oh, and it isn't just the ailerons... Only the cockpit and the wheels don't have this problem...

Thanks!
 
Last edited:
Hey Expand,

Eeeks. Dont get me wrong. I was just saying that in the small screenshot, it looks like only the aileron and landing gear struts look like the material arent 'taking' properly on the materials. They appear to have their shadows flipped upside down.

Materials; You can use Bitmaps in FSX. They just dont perform as well and will not work in DX-10 Sample mode in FSX. So Bitmaps shouldnt be the problem.

You can create 'basic' FSX materials with Diffuse texture 'only'. But if you are doing the 'big kahoonah' super textures for FSX that feature all the features like Specular mapping, reflection mapping, bump mapping, then you will need 'all' of their sub-parts (mentioned just now) for them to function or they will have weird appearence disorders such as flipped shadows.

That is what I am saying. I cannot see your model that well in that screenshot, so I am having to go by that and this is the advice I am offering. I am not the worlds best modeller or advice person. Just offering you my bit of help in what I know from past experience.

I hope that helps.

Making these materials with perhaps 50 various settings in 'each' material is nerve racking, (to me). What I try to do, now that I have a few planes, is import parts from other model projects that have proper materials I need and then change the bitmaps out to the new project and I have instantly imported preset materials into my new plane project. This speeds up the materials setup processes and having little mistakes in all the settings are minimized right off the bat. In your case, you are starting from scratch and I feel your pain. There is alot to do. You'll get there though.

I still run into of trouble on these super materials. It usually turns out to be one single missing tick somewhere in the Material settings. Just have to keep going over it till you find your faulty setting, out of place texture, etc.
 
Ok, thanks! :)

It's the shadows that are flipped: The part of the plane that's facing the sun is dark and the oposite side is lighten...
I know it is the bump map that is causing all these problems... But I don't know why...
 
A quick check to ensure you're barking up the right tree would be to simply remove the bump map assignments from your FSX Materials temporarily, then check in the sim.

If the shading issue disappears, then you have confirmed that the bump (normal) maps are at fault.

If they are, then you need to look at how you are creating them.

Are you using the nVidia plugin to generate them?
Are you moving the Red channel's data to the Alpha channel?
Are you filling the Red channel with pure black (0,0,0)?
Are you filling the Green channel with pure white (255,255,255)?
 
I unchecked the bump map. Nothing, the bump map is still on the plane.
I removed the bump map files and this happened:
Su26_issue.jpg
It got even worse... Now, only the ailerons are correctly lit and the rest of the fuselage and control surfaces is completelly upside down...
The only thing that seems to be escaping the problem is the cockpit texture which hasn't any bump map applyed...

I used that nvidia thingy to make the bump maps...
I saved the bump map with that nvidia software as DDS DXT 5....
I didn't alter anything else...
 
I used that nvidia thingy to make the bump maps...
I saved the bump map with that nvidia software as DDS DXT 5....
I didn't alter anything else...

You can't do that. It won't work properly at all. Fix your bump map(s) as I've described...

After using the nVidia "Normal" filter, click on the Channels tab in Photoshop, and Add an empty Alpha channel.

Select the "Red channel" tab, then Ctrl-A, Ctrl-X to select/cut the entire contents of the Red channel.

Select the empty Alpha channel and Ctrl-V to paste the buffer contents to the Alpha channel.

Select the Red channel and if necessary flood-fill it with pure black.

Select the Blue channel and paint the entire channel with pure white.

NOW Save As DDS/DXT5... :cool:

This is necessary because of the way MS/ACES wrote their shader code. Bump mapping uses only the Green and Alpha channels for their algorithim. The pure black Red and pure white Green channels effectively cancel one another out of the equation!
 
Ok! Thanks!! I'll try!
It worked!!
su26_success.jpg

Awesome! Thanks so much to both of you!! :D

Now I just need to find out how to animate the propeller and put on the gauges!
 
Last edited:
There is an interesting thread here on getting FSX props working. You might paruse through that.


Congrats on getting your material working. Good thinking Bill on the Bump map.
 
Ok! Thanks!! I'll try!
It worked!!

I was fairly certain that it would...

...as I've been there, done that, and spent quite a bit of time researching the issue of FSX "bump" (normal) maps some years ago.

With the sole exception of FSX, game engines use only the RGB channels for "normal" mapping, no Alpha needed!
 
Code:
<partinfo>
    <name>bay_door</name>
   <AnimLength>100</AnimLength>  
<animation>
<parameter>
<code>
(L:bay door,bool) 1;
if{ 100 }
els{ 0 }
</code>
     
</parameter>
	</animation>
</partinfo>

<partinfo>
<name>Bay_door_switch</name>
   <AnimLength>100</AnimLength>    
<animation>
           <parameter>
                 <sim>
                       <variable>bay door</variable>
                       <units>bool</units>
                 </sim>
           </parameter>
     </animation>

<mouseRect>
      <cursor>hand</cursor>
         <tooltiptext>Open/Close Missile Bay</tooltiptext>
         <callbackcode>
               (L:bay door,bool) ! (&gt;L:bay door,bool)
      </callbackcode>
</mouseRect>
</partinfo>

This is the FSX code of a missile bay + switch animation that worked fine in FS9 format..
The problem is as follows:
Both the parts appear on the Animation Manager, but the mouserect of the switch doesn't appear on the attachtool...
Does this have something to do with the code or I just forgot something... again... :D
Thanks!

Also: I followed this tutorial:
http://www.aerodynamika.com/cgi-bin/yabb/YaBB.cgi?num=1253030320
 
Last edited:
Back
Top