MDLC 190: Help needed

[BoeingvsAirbusNKL]

I have a problem to tell 'ya.

I tried converting a plane with Archisoft's MDLC V1.90. it says it has the files... but i looked, but it didn't have the .MD8, the .MD2 and the .MDT Files.

Is there anything anyone can tell or i can do?

 

[simonu]

Did it say
gmax.md2 not found
or
fsds.md2 not found


they are templates for cfs2 models built on the two construction programs

is it those you are missing? they are attached below disguised as txt files be sure to rename them

if you are not comfortable with using command line programs, you'd do well to download and install MK_mdlc LINK
the handy dandy GUI that makes it easy.

 

[sc7500]

Secondary Question

NOT Thread Theft !!!

This is part of my MkMDL.ini:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[KEYFRAME_NAME_LIST]
keyframe_name_1=userdefined0
keyframe_name_2=userdefined0
keyframe_name_3=userdefined0
keyframe_name_4=userdefined0
keyframe_name_5=userdefined0
keyframe_name_6=userdefined0
keyframe_name_7=userdefined0
keyframe_name_8=lever_stick_l_r ;l_aileron_key
keyframe_name_9=lever_stick_fore_aft ;elevator_key
keyframe_name_10=lever_pedals_l_r ;rudder_key
keyframe_name_11=lever_stick_l_r ;r_aileron_key
keyframe_name_12=userdefined0
keyframe_name_13=userdefined0
keyframe_name_14=userdefined0
keyframe_name_15=userdefined0
keyframe_name_16=userdefined0
keyframe_name_17=userdefined0
keyframe_name_18=userdefined0
keyframe_name_19=userdefined0
keyframe_name_20=userdefined0

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Should there be any additions to these Keyframe notes ?

I'm using the MK_MDL Version as Noted in Simon's link...

TIA
SC

 

[simonu]

NOT Thread Theft !!!

sc7500, relax man, I was just practising the modderator tools.

When mdlc does the convertion from FS9 to FS8, keyframe animations using fs9 variables, are exchanged with these fs8 variables automatically.
Heres what Ivan has to say about it in the readme

NOTES:
</f command>
some aircraft build by gmax (FS2004 SDK - MakeMDL) using

new Keyframe Animation Names (Exterior Parts) like as
L_Aileron_Key, R_Aileron_Key, Elevator_Key, L_Flap_Key, R_Flap_Key, Rudder_Key...
generate some new DICT SECTION GUIDs {0C30F248-0F3C-43AE-83FA-CD29F790AA3E}

OR

new Keyframe Animation Names (Interior Parts) like as
Switch_x...
generate some new DICT SECTION GUIDs {CFCBF645-206F-456C-A86C-0C0FAEC544C9}

in *.MDL file that CFS2 simulator engine could not identify and result some parts could not animate normally.

we could change these GUIDs from FS2004 to FS2002 like as
FS2004 Keyframe FS2002 Keyframe
L_Aileron_Key, R_Aileron_Key --> lever_pedals_l_r
Elevator_Key --> lever_stick_fore_aft
Rudder_Key --> lever_stick_l_r

that the FS2002 simulator engine will animate normally but CFS2 still could not
you could modify the settings in MDLC.INI by trail and errors

for examples: the FS2004 stock aircraft Curtiss Jenny
firstly, we could RUN "MDLC /a *.MDL" for output a SCASM source file and find some statements in the file header
;keyframe_name_8 FLOAT32 0xBC 4 {0C30F248-0F3C-43AE-83FA-CD29F790AA3E} AILERON LEFT DEFLECTION#grads#-1#50
;keyframe_name_9 FLOAT32 0xC0 4 {0C30F248-0F3C-43AE-83FA-CD29F790AA3E} ELEVATOR DEFLECTION#grads#1#50
;keyframe_name_10 FLOAT32 0xC4 4 {0C30F248-0F3C-43AE-83FA-CD29F790AA3E} RUDDER DEFLECTION#grads#1#50
;keyframe_name_11 FLOAT32 0xC8 4 {0C30F248-0F3C-43AE-83FA-CD29F790AA3E} AILERON RIGHT DEFLECTION#grads#-1#50

secondary, refer the rightest string such as "AILERON LEFT..", "ELEVATOR...", "RUDDER...", "AILERON RIGHT..."
we just modify some keyframe_name_n assignment settings in MDLC.INI as followings

[KEYFRAME_NAME_LIST]
keyframe_name_1=userdefined0
keyframe_name_2=userdefined0
keyframe_name_3=userdefined0
keyframe_name_4=userdefined0
keyframe_name_5=userdefined0
keyframe_name_6=userdefined0
keyframe_name_7=userdefined0
keyframe_name_8=lever_stick_l_r ;l_aileron_key
keyframe_name_9=lever_stick_fore_aft ;elevator_key
keyframe_name_10=lever_pedals_l_r ;rudder_key
keyframe_name_11=lever_stick_l_r ;r_aileron_key

then RUN the "MDLC /f *.MDL k" command will create a *.MD8 file with keyframe name setting

finally, NOW the MDLC could set the keyframe name automaticlly, just RUN "MDLC /f" command, you could
never worry about [KEYFRAME_NAME_LIST] setting.


</c command>
some FS2002 aircraft used "l_pct_trail_edge_flap0" or "r_pct_trail_edge_flap0" keyframe name,
when RUN "MDLC /c" command, the MDLC will replace them with "l_flap_key" or "r_flap_key" automaticlly.

I suspect one could have mdlc automatically switch any key frame for any other (r_cannopy to visor) for instance, but as I try to grasp what Ivan is saying, I think you have to set it up for each convertion by ripping the fs9 model to scasm, counting off the number of the keyframe_name you want to change. Set it in the ini. then run the convertion.
To be honest I havent fiddled with it.
its more fun to do it manually....

 

[sc7500]

LOL !

...sc7500, relax man, I was just practising the modderator tools.....

I wuz JUST being thorough !
SC

 

[BoeingvsAirbusNKL]

I figured out the problem.

I wasn't using the right MK_MDLC version.