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

FS2004 VC Rain

Messages
366
Country
us-maryland
It's me again...

With the FS9 SDKs for MakeMDL and GMax Aircraft Creation physically in my hands I've followed every step precisely to create the necessary nodes (polys, NOT dummys) and objects in hopes of applying the VC rain effect to my new toy... I mean development project. Unfortunately, when I go to map either of the textures called for by the SDKs, GMax stops me with a "Bitmap unsupported" error. Looking at the details of the bitmaps I see nothing obvious... like dimensions out-of-wack.

Did I miss something?
 
You will need to create "dummy bitmaps" for use in Max/GMax/FSDS. You need only the VCRainMoving0000.bmp and VCRainStopped0000.bmp textures. These two files are DXT3 compressed bitmaps, which Max/GMax/FSDS cannot "read."

Load them into DXTBMP.exe or Imagetool.exe, and convert them to Targa (.tga) format.

You could simply use "blank" .jpg, .tga, 24bit .bmp, or .psd textures, but by using the "real ones" you can then "see" the "rain drops" in GMax's UVW Editor and rotate the UVW Mapped vertices to adjust the "flow of the raindrops" in a more believable manner. It's hardly likely "rain drops" would be moving forwards (towards the nose) for example, nor would they flow "up the window..." :)

What I've done is create a ..\Common Textures sub-folder within my ..\GMax Projects folder, so that I don't have to have the same "dummy textures" in every project's ..\texture folder!
Code:
..\GMax Projects
..........\Common Textures
...............\VCRainMoving0000.tga
...............\VCRainStopped0000.tga
...........\FS2004 Aircraft
.................\DA42
.........................\Textures
.........................\UVW Maps
.................\CJ1+
.........................\Textures
.........................\UVW Maps
...........\FSX Aircraft
...pattern repeated for every aircraft project.
 
Last edited:
Thanks for answering...

It's not the heiarchy that I have issue with, mine is as it should be (as you described and the SDK outlines). It seems we think alike about our project file structures too...

My problem starts when I attempt to load and apply the textures but what you've given me should solve the problem:
Load them into DXTBMP.exe or... and convert them to Targa (.tga) format.

I was wondering if I had to create the texture, which I sort of have to by reformatting the already existing ones. THAT should fix it!

Thank you.
 
That's why I answered your specific question first, and only later described my organizational scheme... ;)

Some people may think that I'm severely anal retentive, but...

...I've got nearly 1 million files scattered across the twelve hard drives on my network...

In spite of my efforts to keep stuff organized, I've no doubt that more than a few of those files will never be found again! :rotfl:

So yes, I tend to name parts in a project's scene, and keep those bitmaps, UVW Maps, etc. that belong to that project in sub-folders within that project's folder name. I even go so far as to name the Materials used in a project with the same name that the bitmap itself uses! :D
 
Bill... you are they way you are because of your education, experience and knowledge from helping others. I NEVER think of you, or any like you, as anally retentive... Everything you and others share with me is appreciate far more than I could ever express in an online forum. And, as a side note, I answered you from work so I couldn't add my usual pleasant language... had to be quick and to the point.

So, with that said...

Your guidance has assisted me in perfectly applying the VC rain effects to my aircraft. Tested flawlessly... well, after a couple times adjusting the orientations of each UVW mapping so the drops "flowed" correctly.

I've noticed that more often than not, the SDKs have a tendency to either make assumptions or just not cover things a simples as this. Also, the GMax SDK says "*.bmp" while the MakeMDL SDK states "*.tga".:):)
 
Oh, I wasn't implying that you might be one of "those people," just that there are some who do tend to think I'm far too concerned with maintaining strict standards... :D

You are absolutely correct in your estimation of the SDK's assumption of a priori knowledge. To be fair, the FSX SDKs are far better than any of the previous release's SDKs, but there's still way too much that's unexplained.

That's likely why my very first freeware model that began life as an FS2k2 product, was under continuous development for nearly two years before finally seeing the light of day as an FS2004 release (TBM20GT). Before the AVSIM "hack" destroyed the library, it had achieved a remarkable 37k+ downloads... :cool:

To be perfectly frank, I've learned most of what I know through the good grace of other people's posts. As a consequence, I strongly feel the obligation to pass it along whenever possible.

The sad reality is that there are far too many places where information is exchanged and archived. The inevitable result is that there's a constant "reinventing of the wheel" taking place.
 
Back
Top