• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Windows 10/11 snafu / content thread

Hey all,

I'm trying to create scenery objects for CFS2 and I can't seem to get it right. I've built the model in FSDS3, I compile an aircraft mdl, then decompile it to an .scx with mdldis32. Then edit the header and enda to endobj. Use scasm to compile a bgl and I get an error in cfs2 or the model is not visible. I'm following weapons creation tutorials as I used to make weapons all of the time. I'm trying to create a tree line object so far consisting of a very simple textured box. Are static objects different than weapons? The other thing that is confusing is that one tutorial says,"Open the sca up in notepad (or wordpad) and delete everything from the top till where it says "; CRASH Detection" and replace it with:
Header( 1 90 -89 180 -179 )
LibID( xxxxxx xxxxxx xxxxxxx xxxxxxx ) ;any 4 32bit Hex numbers
LibObj("

the next one says,"
Go to the folder it was saved in and open the .SCA file in a text editor (notepad)

and delete all the text, etc. down to but not including the BGLVersion( 0800 )line."

The last one says,"Now, delete everything until you see ";*** Start of Main Aircraft Code ***"

Who is correct?

I know the BGLVersion( 800 ) version is the one I used successfully back in the day for weapons.


Thank you profusely for your help.

ShpHawK
 
also

I also cannot get cfs2 to render my model as an aircraft MDL. I have a feeling this is the larger part of the problem. It says MDL creation was successful, but CFS2 says Error the visual model cannot be displayed. I'm using mkmdl from the fs02 sdk. I have a feeling this is the larger part of the problem. Thanks again for the help.

ShpHawK
 
IIRC FSDS needs to be version 2.24(?) to create a CFS 2 mdl file. I think the software designer is receptive to requests for supplying this older version...
 
airportforwindows work with win10 I think it does the same job!!
after tweeking win10 I got the winhlp32 to work, anything seems possible, I think when programs do not work it sometime means there may be a security issue with that type of file.
hope this reply makes sence.
RJ.
 
Hi S,
Blimey!!!

Yes and no....there is very little difference between destroyable objects and scenery objects. One has two states and the other just one. Yes you can use your method and just not have two states ie undamaged and damaged, just don't have the first stage which is the destroyable version in the sca. The first description that you mention is the correct one, I think that's from Tango_Romeo?

Just a test please, re-your mdl conversions not showing up, make sure you're using a CFS2 compatible airfile, not a Fs9. I expect you are using a good airfile, but just asking the obvious first.

It's difficult get a clear picture of what you're doing, as you jump between BGL's and MDL's. Did you then try and make the tree as an mdl to see if it would show up as an ac, just to test it out?

Unfortunately as you know FSDS 3x will not export as a CFS2 compatible model, either an mdl or bgl. With an ac mdl making it CFS2 compatible, you can use MDLC (Mk_MDLC v2). It's here in the archive, install, and then run to convert your created mdl to be compatible. Please read Ivan's README that come's with it. Export from FSDS 3x as an ac mdl and then convert it using MDLC.

NOTE where I have said MDL or BGL, as you cannot convert BGL's using MDLC only MDL's.

You can sca or hex edit the mdl or bgl but TBH the easiest way is to get hold of FSDS 2.24, you can have this installed as well as FSDS 3x. This will make CFS2 compatible ac and scenery straight off without all the messing around m'larky. If you get FSDS 2.24 visual errors in the solid 3D perspective view pane, you can make the item in FSDS 3x and then open it in 2.24 (turning the view pane to display a non-solid mesh visual), and then export it direct to CFS2.

If you really want to go a merrily MDL hex editing kit to change headers etc, I've got a good kit that works, which I used to use years ago...but please just get FSDS 2.24...it will save time, disappointment and sanity...;)

Cheers

Shessi


Ha! Wot UT said!
 
So what do you want to make?


If you want to get your feet wet, I'm doing model conversions. I'm using Gmax and taking API macros and making them into destroyable models. Its a good way to learn Gmax.

If you have FSDS 3 you may want to ask if they can send you a copy of FSDS 2.24. Other wise Gmax will be your only option at this point.

We may be able to take a model made with FSDS 3 and export it into Gmax. The mapping will be lost (I think). Shessi or Allen would have to confirm that.
 
So what do you want to make?


If you want to get your feet wet, I'm doing model conversions. I'm using Gmax and taking API macros and making them into destroyable models. Its a good way to learn Gmax.

If you have FSDS 3 you may want to ask if they can send you a copy of FSDS 2.24. Other wise Gmax will be your only option at this point.

We may be able to take a model made with FSDS 3 and export it into Gmax. The mapping will be lost (I think). Shessi or Allen would have to confirm that.

Mapping will be fine if you Model Converter X to make the FSDS model to a .3ds. Object smoothing will be lost.
 
That would make things easier-ish. But you could then export it using Gmax. You may have to use the FS2004 sdk. Depending on what you want it for.

Allen did a wonderful .bat file for exploding objects. Actually he has made four different .bat files. one for weapons, Ships, Fs2002 sdk and one for the FS2004 SDK.
 
That would make things easier-ish. But you could then export it using Gmax. You may have to use the FS2004 sdk. Depending on what you want it for.

Allen did a wonderful .bat file for exploding objects. Actually he has made four different .bat files. one for weapons, Ships, Fs2002 sdk and one for the FS2004 SDK.

He may have to use gMax as from what I remember FSDS 2 won't install on Win7 or newer systems.
 
He may have to use gMax as from what I remember FSDS 2 won't install on Win7 or newer systems.

FSDS 2.24 is a 16 bit application, as such it will not install on a 64 bit system like mine, however, If you are running the correct version of 7, as I am, You can run windows xp mode, or use another 32 bit virtual machine. Though I haven't tried it yet, I'm pretty sure it should run on 32 bit windows 7. If I absolutely cannot stand xp mode, I will try it.

Thanks Shessi, Allen, UncleTgt, and Bloodhawk23. I really appreciate the help. I kind of thought I had to go back to 2.24. Bloodhawk23, I appreciate the offer, but I never really cared for the UI in Gmax. To me, FSDS is so much more intuitive.

ShpHawK


PS UncleTgt,

check out the Tetsuban thread. It's for you.
 
Not many have Win7 32bit. This mean most FSDS2 users will need to change to gMax or virtual machine the program. My understanding is that FSDS2 will run on Win7 64bit but can't register thing things so it is stuck "Trial Mode".

The only thing related to a virtual machine I have messed with is DOSBox to get MDLC working on 64bit systems.
 
Not many have Win7 32bit. This mean most FSDS2 users will need to change to gMax or virtual machine the program. My understanding is that FSDS2 will run on Win7 64bit but can't register thing things so it is stuck "Trial Mode".

The only thing related to a virtual machine I have messed with is DOSBox to get MDLC working on 64bit systems.


I can't even get 2.24 to install on my machine(7 x64). It says that FSDS 2.24 is not compatible with an x64 operating system. As long as you have a powerful enough machine, VM's are not difficult to work with, it's just a pain to have to move files from the guest to the host constantly. FSDS 3 runs great on a x64 machine. I only hope that the modeling I have done can be imported from 3 to 2.24. It would really bite to have to start over.I will post my findings here in the hopes that it helps someone in the future. Thanks Allen.

ShpHawK
 
"..I only hope that the modeling I have done can be imported from 3 to 2.24."

Yes they can.

That's how all my stuff is done. Build using 3.1 or 3.5, then into 2.24 to export for sims. Works very well.

The difference between FSDS 2 and 3 is that 3 adds FSX compatibility and a few extra animations, but is much much tighter on how you model, everything has to be spot on, otherwise compilation failures, whereas in 2 everything goes!

Cheers

Shessi
 
That’s not correct…
I've got it to run on a 64bit Windows 10, but it's very tricky, because you have to install and activate it on a 32 bit System first than go to the registry copy and save 3 entries on an USB stick, than copy the Whole Program Folder also on the USB stick. Now go to your 64bit System, paste first the Program Folder in your “Program” Folder (not into the Program (x86) Folder), then click on the 3 registry entries (they will go automatically in the correct Folder) and start the program as Administrator, you have it always to run as Administrator!!! Otherwise you will have Problem with textures.

You can find those entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\Abacus
HKEY_CURRENT_USER\Software\Abacus
HKEY_CLASSES_ROOT\Applications\FSdesign2.exe
You need all 3 entries (right click, copy, - and paste it on you USB stick)
Well as I said it’s tricky but it works finally for me.
wolfi
 
I forgot to mention,
Make always a backup of your windows installation before you do anything with your registry!!!

wolfi
 
I forgot to mention,
Make always a backup of your windows installation before you do anything with your registry!!!

wolfi


Holy crap Wolfi! That's awesome. I am going to do just that. If I haven't figured out making backups and saving often by now, I never will. Thanks. I just created a vm and got 2.24 running but that is a painin the ass, not to mention VMware uses a bunch of resources in the background. looks like I have my registry keys though. Thanks a bunch.

Chuck
 
Sure enough I was able to compile a working BGL on 2.24 and run it in cfs2. Still Wolfi's advice is the way to go. Now I have my proof of concept. MaskRider, expect a pm asking for permission to use some of your work. If my plan works, you may very well be interested. Thanks to everyone!

ShpHawK
 
Back
Top