• 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 Bell 429 exporting issues

Messages
1,451
Country
mexico
Hello

Nowadays, I am designing a Bell 429 originally in 3ds max. After months of learning how 3ds max and Gmax works, I finally get my basic mesh in Gmax with all its textures. I exported from 3ds max as 3ds mesh studio format, then piece by piece, start to weld the vertices created during the exporting process. Finally, updating the textures in targa format (1024x1024 pixel res.). Before to export to Gmax, I applied an Xform modifier to everything in the scene and collapsed all stacks.

Once in Gmax and before attempting any animation, I was trying to export the model to FS9 using a combination of middleman, ULE & makemdl.exe stand alone. I did it first without any texture and the model showed up in FS9 nicely. I was happy with such achievement, so I worked hard to give the model all textures to work. Using only materials with the channel "diffuse" in "blink" mode. I took care not to get to 60k polys with a single material

The disappointing truth came when I tried to export the first time with textures; the export in "chunks" was a failure. Just by adding textures, all went to the trash can; no matter if the model looks well in Gmax. Here are some pictures:

In Gmax:
sample_Gmax_02.jpg


sample_Gmax_01.jpg


Now in Flight Simulator 2004 after being exported. I did not get any error message during the exporting process...:confused::confused::confused:

Look this weird windows...
sample_2.jpg


sample_3.jpg


sample_1.jpg


Any ideas?
In advance, thank you.
Sergio Kauffman.

P.S. By the way, I know the idea to put to work the rotors if they are oriented in the "y" axis; however, how would be the way to tell FS9 that another rotor is oriented differently. The helicopter has two different orientations and the tutorials regarding props are for FSX only... The FSX' version is a frame method and it is not like in FS9. In the pictures above, I did not tried or used any animation.
 

Attachments

  • sample_3.jpg
    sample_3.jpg
    120.7 KB · Views: 499
  • sample_2.jpg
    sample_2.jpg
    186 KB · Views: 471
  • sample_Gmax_01.jpg
    sample_Gmax_01.jpg
    211.6 KB · Views: 525
  • sample_Gmax_02.jpg
    sample_Gmax_02.jpg
    220.9 KB · Views: 525
  • sample_1.jpg
    sample_1.jpg
    259.2 KB · Views: 591
Ok, you said you applied the Xform modifier prior to export. You must use the Reset Xform in the Utilities panel not the Xform Modifier. The Xform modifier will not reset the scale and that is the problem.
The missing poly are inverted so you need to convert to edit poly and flip those reversed polys. This happens a lot when using 3ds mesh export.
 
Hello Paul

I made a mistake in the explanation. I performed all Xform actions from the utilities panel and no with an Xform modifier (how could I said that...:eek:). In Gmax, I double checked all scales and transformations and everything was at 100%. No scaling issues at sight...o_O

On the other hand, thanks for the head up with the Xform modifier and the flipped polygon normals. You said that there are polygons flipped; nevertheless at naked eye, I couldn't spot any; in Gmax everything looks "well mapped" and shows "as it should". :confused::confused::confused:

I will verify this issue and check again the normals with the information you've kindly gave me and see what's happens next.

Kindest regards,
Sergio.
 
That's another option to work.

Many people says that panda x files has different syntax than the ones generated in Gmax. I already have the plugin installed for my 3ds max version (in the correct bit version); let's see what happens.

Ahh, another thing... panda exporter does not work well with animations for FS9 if I can recall...:confused::confused::confused:

Thanks Johnman.
:(
 
Last edited:
Hello Sergio,
If I Remember correctly - all the animations worked Properly - with the exception - on My Cessna 152 - the Nose Strut would Not Compress - Textures - Lights - Wheels - Prop - Controls - That Nose Wheel Strut had us all Baffled over at the Old "Suclaro" Form - But I would try it - I'm sure they have updated the Program Since I tried using it !?? - and You May NOT Run into It !! - Good Luck - Johnman :cool:
 
Ok Johnman, it worth the shoot! Thanks for the clarification.

Kindest regards,
Sergio.
 
This is a story that begins with "Once upon a time."
I know how frustrating it is. When I started modelling for FS9 I used FSDS. Exporting worked without a hitch. I moved to gMax and became extremely frustrated with gMax trying to learn how to use it. I literally would pound my head against the keyboard. Then I tried 3ds Max and the world was good again. At the time I had both FS9 and FSX but my computer was not fast enough to run FSX so I continued to model for FS9. All the frustrations returned, all the problems you are running into I ran into. I tried everything including Panda but it was one headache after another nonstop. This went on for over a year. I finally made a decision. I upgraded my system to run FSX and started exporting my models for FSX. I was very happy then and I have never looked back.

This is the best advice I can give you on the subject.
 
Hey Paul - I agree - Pretty much down the Line - and Fsds is the "King" for Export - However - Its Geometry Creation really needs updating - Fsx/3DsMax is the answer - however - it created a wholenuther room FULL of Boogiemen - the first being - setting up the Export Module and Files so they Work - Animation (EEK)(actually Pretty Simple) - But another Bump in the learning Curve - and now I have gone to War with Textures and the Virtual Cockpit "Dragon". - and All the Information Necessary is out there - but Widely scattered and totally Unorganized ! - Two things in Conclusion - In the 15 or so Years that I have been Modeling - and Loving it !! - I Have Yet to come to the point in a Models Creation - where I can say - Welp - That one is done - Lets start a New One ! - I never seem to Finnish One - And Also - I am positive that the Knowledge is Available - On This Form - to show Sergio how to go from 3DsMax - to F2004 - with out all the extra Converting and Gmax - this is Not to Deny Sergio the Opportunity - to Dig through the Forms Himself - in His Quest for Knowledge - Sometimes the smallest Nugget can lead to a Solution !! - Johnman :cool:
 
Hello dear friends!!!

Yes you're right! I love to digg in the forums. the problem is that most topics are for FSX and Prepar3d. This is really simple: I browsed all forums and hit the FS2004 category filter and I've read them all. After that, I continued my search in the rest of the threads. Also, I have models already done by you guys. As I mentioned before, my base of learning. I have studied by observing the textures of the models the way that most of you have disposed the mapping techniques. Specially the helicopter models designed by Jordan Moore, Devin brothers and Rory Kelly.

Regarding to migrate to another platform: it is a big YES. I will do the effort to provide this helicopter for FSX users. The former textures are in 2048x2048 in order to be FSX and Prepar3d consistent. Let me explain how I thought about the project planning:

1.- First, create a model with all parts possible to be able to provide variations of the same helicopter family. In the recent snapshoots, you can see
floats, radome, winch, a set of different antennas, etc. Of course, there are more pieces of hardware which can be added later.

2.- I followed the designer "mantra" learned here: "Design your part or component, map it and apply textures right away!" If I am right, the most basic
scheme of materials and textures are for FS9. This is the first reason to insist in FS9 and the second, it's because many people (like me) are still
using this simulator. Despite all problems mentioned, the reality is that this model can be upgraded to FSX and Prepar3d adding bump maps and
taking care of material's consistency.

3.- Once I have done the step 2, in theory I have 3 variations of the same model: for FS9, FSX and Prepar3d. Between steps 2 and 3, it's a good idea
to start testing the exporting methods (that's what I am trying to do now). Since I don't own a copy of FSX nor Prepar3d, I am seriously
constrained in this regard.

4.- Start working on animations. This will take me another bunch of head aches. Since I am not a programmer, I'll need to learn new stuff.

5.- The last stand: make working gauges to fit as closest as possible the helicopter systems. It all depends on my very basic skills with XML gauge
knowledge, of course. In the past, I was able to program in C++; however, the methods have been greatly improved since I learned the language
(20 years ago...) and now, everything looks so different that I am not familiar with the language anymore. Another hiccup and perhaps I will need
to learn it again.

6.- Sound system? Not a problem, I've done several sound systems that fits exactly my personal taste.

As you may see, I have a big mountain to climb. When I began this personal project, I knew that it wouldn't be easy. So, I am thankful with all of you, because you are a very important part in this process.

Take care and have a nice day/evening/night.
Sergio.
 
Hello Sergio,
If I may comment on Your Very Honest Outlook Statement - Fsx can be purchased very inexpensively on Ebay - that's how I got Mine - Just make sure that You get the Deluxe or Gold Edition - which will contain the sdk ! Also - Someone please correct Me if I am wrong - the Fsx Sdk - is the same as P3d v1,v2,and v3 - You should be able to Drag and drop Your Model from Fsx into the P3d's - And Modeling Gauges Would only Be something to do if You wanted to - as All the Gauges You could Possibly want to use in the near future have been created - in all Formats - and are available for Your use - However Making them appear on a Panel in the Sim can be a bit of Smoke and Mirrors - But I'm getting a handle on it -If You Follow the sdk - Animations Are easy and so is Adding Lights All in the sdk ! and I know very Little C++ or "XMLish" - And to make Your Mountain easier to climb - there is always Someone on the form Who is Happy to Help !! Keep coming back ! - Johnman :cool:
 
Johnman, hi!!!

Thanks for your kind words an support. It feels good to be here and much better, to feel the friendship of all you guys; I really appreciate this.
I took this this very seriously and I realize now that it is a mistake; actually... it is very fun!!! If I can shift paradigms, perhaps the puzzle should start to take shape.

I will keep climbing, but in a much calmer rhythm.
;)
 
Hello lads

I made it... it was a silly thing. Just unchecked the "has reflecting maps" when I used makemdl.exe and that fixed the problem. Also, I was reading more notes about ULE and I think that the LOD order was wrong in the last conversation we had. Now everything is like a charm. I will give the LOD names I used:

Exterior:
  1. project_40: prop0_still
  2. project_50: prop0_slow
  3. project_60: prop0_blurred
  4. project_100: fuselage with no animations yet.
  5. project_70: prop_still
  6. project_80: prop_slow
  7. project_90: prop_blurred
  8. project_200: all parts in the cabin; no animations either.
  9. project: I created the famous dummy sphere with 32 segments.
Then, I made a copy of the "X" files in regard of what I need as interior and shuffled the names:
  1. project_interior_75: prop_still
  2. project_interior_85: prop_slow
  3. project_interior_95: prop_blurred
  4. project_interior_250: all parts in the cabin; no animations either.
  5. project_interior: Another dummy sphere.
That made the trick, nothing missing and the rotors animated and shown as they should.
Of course, I am using the old disc as slow and blurred animations. Resuming:

a.- Rotor animations at the low LODs.
b.- The rest of the exterior fuselage (not animated yet and this may be changing in the
future).
c.- Complete cabin.

This precise order is avoiding to have the unwanted transparency in the fuselage and VC.

I brought some friends to the party...
429_vorona_08.jpg


429_vorona_07.jpg


Thanks again and have a very nice day.
Sergio.
;)
 
Last edited:
What a model!!!
I have been toying around with ULE for my current Dassault Mercure project and ended with the following assemblies:
  1. LOD0 (root) Fuselage
  2. LOD300 L wing
  3. LOD400 R wing
  4. LOD500 cabin
  5. LOD600 cockpit (to be replaced by VC for internal view)
I temporarily copied over the BGL_CALL32 block form external view to internal view, and renamed LOD_x to INTERIOR_x. What came out was a model that showed all exterior assemblies in VC view, but since I did not call a separate assembly, model size was the same, plus perhapse a few KBs. Note that it is currently at about 4.5 MB MDL !!!
So, later on I will just call parts 1 t 5 and add the BGL_CALL32 for the VC assembly, and...SHAZAM! this will save you compile taime and make the model more efficient :)

May I ask you what the dummy sphere is for?
 
Hello Mario

Thank you, mine is not efficient at all 9,647 kb... And there is still much to do :duck:
I was overwhelmed with the window and windshield cuts; to many loops to keep curvature in the fuselage... which eventually I ruined with an error that went unnoticed and now, I am not able to find it. If you take a closer look, you'll notice that I spoiled the model by three major things: the nose, the width of the fuselage and a pair of vertices that I can not see in the connection between the tail and fuselage.

The dummy sphere, helped me to correct issues when exporting... sometimes do the job, and other times I need to remove it from compilation. You're seeing a "miracle", because many times I don't know exactly what's happening between Gmax, ULE and FS9. On the other hand, I am not sure to understand what are you explaining to me. I am not very familiar with X files structure. :(

Looking forward to see what you've been working on!
Take care and hope to know about you more often.
:wave:
 
Alright, If you want to check my progress there are some screenshots in the projects section of my site (click on my signature). Here I present to you my current ASM file LOD section:

Code:
model_outside    label    BGLCODE
    IFMSK    model_crash_skip,dict_0_crash_check,-1
    BGL_CALL model_crash
model_crash_skip label BGLCODE

LOD_0    label    BGLCODE
    BGL_CALL_32    LOD_0L
LOD_1    label    BGLCODE
    BGL_CALL_32    LOD_1L
LOD_2    label    BGLCODE
    BGL_CALL_32    LOD_2L
LOD_3    label    BGLCODE
    BGL_CALL_32    LOD_3L
LOD_4    label    BGLCODE
    BGL_CALL_32    LOD_4L
   
    BGL_RETURN

model_inside  label    BGLCODE

INSIDE_0   label   BGLCODE
    BGL_CALL_32    LOD_0L
INSIDE_1   label   BGLCODE
    BGL_CALL_32    LOD_1L
INSIDE_2   label   BGLCODE
    BGL_CALL_32    LOD_2L
INSIDE_3   label   BGLCODE
    BGL_CALL_32    LOD_3L
INSIDE_4   label   BGLCODE
    BGL_CALL_32    LOD_4L
   
    BGL_RETURN
model_shadow label BGLCODE

SHADOW_0   label   BGLCODE
    BGL_CALL_32    LOD_0L
SHADOW_1   label   BGLCODE
    BGL_CALL_32    LOD_1L
SHADOW_2   label   BGLCODE
    BGL_CALL_32    LOD_2L
SHADOW_3   label   BGLCODE
    BGL_CALL_32    LOD_3L
SHADOW_4   label   BGLCODE
    BGL_CALL_32    LOD_4L
   
    BGL_RETURN

note how the model_inside section calls again LOD_0L to LOD_4L. LOD_4L is actually the low-res cockpit for outside model. One day I will drop there the LOD for DVC. As you know, you export the X file, and MakeMDL generates the ASM files, these are called by these LOD-xL entries... Technically there is no difference between a virtual cockpit LOD and an outside one, and yes, you CAN have click-spots on the external view (what about door handles?)
 
Mario
Your progress on the Mercure is fantastic!!! Well done my friend, and it was said by a fan of your aircrafts!:wizard:
Now, I know more than yesterday and I got it; this is brilliant!!!. Thank you very much for the explanation in regard the main ASM file and of course I will going to try it. :D:D:D

By the way, I use XML Copy Editor; to work with gauges and X files. Google it, it is free and works like a charm.

Keep up the good work!
Sergio.
:wave:
 
@Mario Noriega:
Hello my friend, I just want to ask if you are always having hard time with ULE or its just the LOD naming convention fuzziness that is driving me insane?
I recently fixed some mayor problems in the model and now I am not able to export it again using the LOD's as before... The same whole story from the beginning. :mad::mad::mad:

I only wish how to predict when the LOD names will/would cause exporting issues (I know... that's have been told and it is not fully understood, it's just my bubble being burst again) :confused::confused::confused:

Seems to me, that when you modify part names, size and/or its design (meaning, by changing somehow the overall shape and polygon count as result), the LODs start to fail. I think I will need to test new ways to rename and export LODs. Now that I am adding more details to the VC, the polygon count is rising dramatically (83,019 polys at this moment)...

I have some questions:

1.- When you edit the project.asm file is before or after running "RUN_ASM_SCALE"?
2.- I opened my main asm file and has different options than yours, and when I do the same as you do, I have messages from BGLC_9.exe telling me that I have syntax errors. For example, characters not defined or unknown.

I'm a little bit lost here. Here is the main asm code:
Code:
; compile with BGLC /MDL C:\Users\antaris\Desktop\project\project.asm
    db  'R','I','F','F'
    dd  aircraft_model_end - $ - 4
    db  'M','D','L','8'

    db  'M','D','L','H'
visual_model_header  label dword
    dd  visual_model_header_end - $ - 4
    dd  0
    dd  0
    dd  258
    dd  0
    dd  0
    dd  156
    db  'F','S','8','0'
    dd  2304
visual_model_header_end  label dword

    db  'D','I','C','T'                                                
param_extension_dictionary     label dword                             
    dd  28
    dict_0_engine0 equ 152
    dd 2,152,4, 0FBD8EE2Ch, 04E9C39A7h, 063AA27B5h, 00FE5E72Fh
param_extension_dictionary_end  label dword                             

    db  'B','B','O','X'  
    dd  bbox_end - $ - 4 
    df  -170.316, -35.068, -242.982 
    df  170.316, 92.817, 170.316 
bbox_end label word      

    db  'I','S','F','T'  
    dd  ver_end - $ - 4 
    db  "MakeMDL - FS90 (9.00.030612.02)",0
ver_end label word      

    db  'B','G','L',' '                                                
    dd  aircraft_model_end - $ - 4                                     
aircraft_model    label    BGLCODE                                     
    VPOSITION    no_model,0,258,AIRCRAFT_PARAMS.llapbh.lla               
    VFILE_MARKER AIRCRAFT_PARAMS.texture_dir                           

    IFMSK           inside,AIRCRAFT_PARAMS.gen_model,GEN_MODEL_OUTSIDE+GEN_MODEL_DISPLAY
    BGL_CALL        shadow                                             
    VPOSITION       no_model,0,258,AIRCRAFT_PARAMS.llapbh.lla           
    SUPER_SCALE     no_model,0,0,6                                    
    VINSTANCE_CALL  model_outside,AIRCRAFT_PARAMS.llapbh.pbh           
no_model    label   BGLCODE                                            
    BGL_RETURN                                                         
shadow    label    BGLCODE                                             
    BGL_IF  AIRCRAFT_PARAMS.gen_model,GEN_MODEL_NOSHADOW               
        BGL_RETURN                                                     
    BGL_ENDIF                                                          
    SHADOW_VPOSITION    AIRCRAFT_PARAMS.llapbh.lla                     
    SUPER_SCALE         shadow_out,0,258,6                             
    SHADOW_VICALL       model_shadow,AIRCRAFT_PARAMS.llapbh.pbh       
shadow_out    label     BGLCODE                                        
    BGL_RETURN                                                         

inside label     BGLCODE                                               
    IFMSK        inside2,AIRCRAFT_PARAMS.gen_model,GEN_MODEL_FRONT       
inside1    label    BGLCODE                                              
    BGL_RETURN                                                                 
inside2    label    BGLCODE                                              
    IFMSK        inside3,AIRCRAFT_PARAMS.gen_model,GEN_MODEL_DOWNWARD    
    BGL_CALL     shadow                                                        
    BGL_RETURN                                                                 
inside3    label    BGLCODE                                              
    VPOSITION    no_model,0,258,AIRCRAFT_PARAMS.llapbh.lla                  
    SUPER_SCALE  no_model,0,0,6                                           
    VINSTANCE_CALL  model_inside,AIRCRAFT_PARAMS.llapbh.pbh                
    BGL_RETURN                                                             

model_outside    label    BGLCODE
    IFMSK    model_crash_skip,dict_0_crash_check,-1
    BGL_CALL model_crash
model_crash_skip label BGLCODE

LOD_0    label    BGLCODE
    BGL_JUMP_32    LOD_0L
LOD_1    label    BGLCODE
    BGL_JUMP_32    LOD_1L
LOD_2    label    BGLCODE
    BGL_JUMP_32    LOD_2L
LOD_3    label    BGLCODE
    BGL_JUMP_32    LOD_3L
LOD_4    label    BGLCODE
    BGL_JUMP_32    LOD_4L
LOD_5    label    BGLCODE
    BGL_JUMP_32    LOD_5L
LOD_6    label    BGLCODE
    BGL_JUMP_32    LOD_6L
LOD_7    label    BGLCODE
    BGL_JUMP_32    LOD_7L
LOD_8    label    BGLCODE
    BGL_JUMP_32    LOD_8L
 
    BGL_RETURN

model_inside  label    BGLCODE

LOD_0    label    BGLCODE
    BGL_JUMP_32    LOD_0L
LOD_1    label    BGLCODE
    BGL_JUMP_32    LOD_1L
LOD_2    label    BGLCODE
    BGL_JUMP_32    LOD_2L
LOD_3    label    BGLCODE
    BGL_JUMP_32    LOD_3L
LOD_4    label    BGLCODE
    BGL_JUMP_32    LOD_4L
LOD_5    label    BGLCODE
    BGL_JUMP_32    LOD_5L
LOD_6    label    BGLCODE
    BGL_JUMP_32    LOD_6L
LOD_7    label    BGLCODE
    BGL_JUMP_32    LOD_7L
LOD_8    label    BGLCODE
    BGL_JUMP_32    LOD_8L

    BGL_RETURN
model_shadow label BGLCODE

SHADOW_0   label   BGLCODE
    BGL_JUMP_32    LOD_1L
SHADOW_1   label   BGLCODE
    BGL_JUMP_32    LOD_2L
SHADOW_2   label   BGLCODE
    BGL_JUMP_32    LOD_3L
SHADOW_3   label   BGLCODE
    BGL_JUMP_32    LOD_4L
SHADOW_4   label   BGLCODE
    BGL_JUMP_32    LOD_5L
SHADOW_5   label   BGLCODE
    BGL_JUMP_32    LOD_6L
SHADOW_6   label   BGLCODE
    BGL_JUMP_32    LOD_7L
SHADOW_7   label   BGLCODE
    BGL_JUMP_32    LOD_8L
SHADOW_8   label   BGLCODE
    BGL_JUMP_32    LOD_8L
   
    BGL_RETURN

LOD_0L    label    BGLCODE
    include    C:\Users\antaris\Desktop\project\project_0.asm
LOD_1L    label    BGLCODE
    include    C:\Users\antaris\Desktop\project\project_1.asm
LOD_2L    label    BGLCODE
    include    C:\Users\antaris\Desktop\project\project_2.asm
LOD_3L    label    BGLCODE
    include    C:\Users\antaris\Desktop\project\project_3.asm
LOD_4L    label    BGLCODE
    include    C:\Users\antaris\Desktop\project\project_4.asm
LOD_5L    label    BGLCODE
    include    C:\Users\antaris\Desktop\project\project_5.asm
LOD_6L    label    BGLCODE
    include    C:\Users\antaris\Desktop\project\project_6.asm
LOD_7L    label    BGLCODE
    include    C:\Users\antaris\Desktop\project\project_7.asm
LOD_8L    label    BGLCODE
    include    C:\Users\antaris\Desktop\project\project_8.asm



aircraft_model_end label     BGLCODE

Take care and have a nice weekend!
Sergio.
 
Last edited:
Back
Top