Virtual Cockpits

[Guest]

Nice job Paul,I have followed as many postings related to VC and have failed to get my interior to appear in FS. Did you have to name the interior parts with special prefix? Also when I export according to others instructions the export fails. The export BGL does not make the two 12K files that it should so I can add the interior.x to the list and the write the MDL. I am at my resource end!!What is the gig here? I haven't even got to the mapping and guage files yet. Should there be something done there at this point as well?Any help will be appreciated!!Steven

[Guest]

Hi StevenMilton wrote a piece earlier in this topic about how to do it.However the first question I must ask is1 FSDS or GMAX2 If GMAX are you are using Middleman or just MAKEMDL.3 Milton's message refers I believe to using MAKEMDL.exe only.4. IF you use middleman the you need to groups place the VC in an INTERIOR group and the aircraft in an EXTERIOR group.5 Now to see these thing in FS you need to go the hierarchy utility.The exterior pivot show be set to the COG point which is 0,0,0 in my aircraft.I have built the interior group 20 metres left of the aircraft so using the Hierarchy utility again I set the pivot to -20,0,0.Run the middleman utility save the file as a .mdl- middleman does all the bgl splitting and reconverting for you so it is relatively simple.Finally once compiled, move the mdl from GMAX to your desired aircraft model folder.You need to set the eye point reference from the aircraft cfg file.I work in metres and the GMAX coordinate system works X, Y and Z but this eyepoint reference works as Y X and Z and in feet from the reference point which is different from from the COG but in my file the COFG and REF point occupies the same coordinates 0,0,0.You need to determine where a pilot sits in the exterior (not interior) model a get this eye point value.Your panel cfg file also must include a VC reference. Be sure that if you are borrowing a panel cfg to modify to your requirements it has this entry. Look at one of the default aircraft panel cfg files.That is as much as I know. I will complete all the parts in the VC and then find out what to do next.Hope this helpsPaul H

[Guest]

>Hi All >>Back again. Thanks for all the postings. >>Fr Bill I realise you are busy at the moment but your reply >has me somewhat intrigued? >Am I going about things in the right fashion or am I going >to end up frustrated? (not that I haven't been there with >this project already). >Again you have suggested a number of possibilities on how to >proceed but I neither know what these are or which one is >right for me. Hi Paul!I have no problem sharing freely whatever I've learned with anyone, whether their project is destined to be freeware or payware, unless of course it is 'something totally never-before-done,' in which case that project needs to see public release first... :)What I do lack is time...I notice that you've spent a considerable amount of time modeling 3d switches for the overhead and knobs for the AP panel. Since there isn't a way to 'animate' them though, I am curious what you've got in mind? Something I've always had in mind to try would be to model static things - such as a gauge frame - in 3d and then apply the texture/gauge files to lend a bit of depth to the illusion. These features, not being animated, should be fairly easy to accomplish.Understand that the way that you obtain animated gauges in a VC is through the use of transparent 'projection panels' on which they are displayed. In practice, you will need to subdivide your VC cockpit into a series of relatively flat areas that are on the same plane when viewed from the left or right, and then draw a set of planar surfaces that are the exact shape/size to 'fit' each of those areas.Please, do not even consider designing a VC without gauge backlighting! An otherwise stellar model will be rendered useless at night otherwise... :)The various methods of nighttime gauge illumination predicate the specific design technique used, so this is where an early determination of which you are going to use for each subsection will save time and frustration in the long run. Here is a very brief description of each method:Basic Method #11) Apply a fixed panel background to the physical VC panel.2) Project gauges onto the planar $VC surfaces, with VC_L.bmp mask in the 'Self-Illumination' slot in the Material Editor.Chief weakness of this method is that when panel lights are turned on, the entire projection surface will turn flat black, hiding/obscuring the background panel's image.Basic Method #21) Do exactly as above, but apply appropriate sections of the VC background image to each of the planar projection panels via an entry in the panel.cfg file.This will overcome the 'flat black' problem as described above, but will not allow you to use 'spot' or 'flood' lighting, as described in the Advanced Methods listed below.Advanced Method #11) Apply a fixed panel backgroud to the physical VC panel.2) Design your 'planar surfaces' as a set of individual objects the exact size and shape of the gauges themselves.3) Group them logically into 'sets.'4) Apply the $VC.bmp texture to each 'set,' with a VC_L.bmp mask assigned to the 'Self-Illumination' slot in the Material Editor.The advantage of this method is that this will eliminate the weakness of the "Basic Method" completely. Where there is no projection surface, there will be no 'flat black' to cover/obscure the background.In addition, you will be able to apply an Alpha Channel mask to the background.bmp in the Material Editor, providing a method of 'spotlighting' and/or 'floodlighting' appropriate areas of the panel - such as under-glareshield lights.Advanced Method #21) Similar to Advanced Method #1, except that 'holes' are cut into the VC background panel, and the planar projection surfaces are placed behind the VC background panel.2) As before, the 'holes' must be the exact size and shape of the gauges that will be used.Conclusion:From the descriptions of the two 'Advanced Methods,' it should be abundantly clear by now that one of the earliest decisions that must be made - before beginning the process! - is which gauges will be used in the model, and which method (or combination of methods!) will be used... :)I hope that this is a bit helpful.

[Guest]

Thanks for your time Paul,I am using Gmax4. IF you use middleman the you need to groups place the VC in an INTERIOR group and the aircraft in an EXTERIOR group.What is this "middleman" stuff and where do I get it. Like I said in another post I have tried the two group thing and still get no results.5 Now to see these thing in FS you need to go the hierarchy utility.What utility are you refering to here?Steven

[Guest]

Stevenhttp://thegreatptmd.tripod.com/ is the location of middleman. Installation instructions included. You might check you have the latest version of makemdl.exe available from microsoftThere is reference to another utility called mdlcommander, I have not used this but I believe it allows access to the xfile (the go between state of your gmax project and the final mdl file), to make changes to material and lighting effects.I digress as this is not required for VC design.Ok the Hierarchy utility is the third tab in the right frame of gmax you know where you bang in the numbers or select a primitive shape. The third tab has a rectangle with 3 smaller rectangles below it.Select that tab and click on the affect pivot only button. The use the toolbar move icon to move the exterior pivot to coordinates 0.0.0 and the interior pivot to the x offset position,y and z coordinates (-20 (in my project) 0.0) Remember to turn off the affect pivot button function once each pivot is moved.export and middleman will do the rest. There are various middleman options that need to ticked when middleman runs, if you run into trouble chances are that one of these options either needs to be ticked or unticked. You have a choice.Paul

[Guest]

Thanks Fr BillThe fog is slowly lifting.My intentions at the moment are to design the cockpit with the instrument gauge bases. These bases will be in the correct locations and hopefully set-up in such a way that accomodating the gauges is straight forward. For example the main forwad panel gauge bases all occupy the same plane.Once complete I will take a screen shot in GMAX or FS which will form a basis for the 2d panel artwork.Once that is complete I will consider the advanced options you refer to. From your information I may well have to redo some of the work already.I am a aware that I may use too many resources if I try and display too many gauges. Striking the balance will be the key.Would any gauge programmer hazzard a guess on the gauge limits/frame rate balance.Thanks again for the time.Paul H

[Guest]

>Thanks Fr Bill >>The fog is slowly lifting. Well, that's the intention. It's a whole lot easier to model in VFR conditions... :)The following are some prototype images of a popular bizjet's VC panel. Because of the size of this cockpit, it has been subdivided into a total of seven separate areas, each with it's own UVW map and $ and _L textures.P1 (left half of main panel)P2 (right half of main panel)P3 (glareshield AP console & center pillar compass housing)P4 (left knee switch panel)P5 (ECU/FMS center console)P6 (right knee switch panel)P7 (overhead switch console)The first image is from GMax, and shows P1's UVW map. Since I want hi-resolution on all gauges, the $textures are all 1024x1024. Notice that the planar surface is actually a clone of the main panel, cut into two 'halves', and pulled a fraction of a inch away from the main panels surface. The 3d modeled portion of the entire panel/glareshield has been mapped and a base texture applied (with major gauge positions pre-located). The actual gauges are applied to the $P1 panel via the panel.cfg file.The next pictures illustrate the backlighted gauges from various angles. Note that these are not the actual gauges that will be used, but are mostly default gauges used as placeholders for the 'proof of concept' testing that has been done. In practice, I'd tweak the lightmaps so that the external bezels on the PFD would't 'glow in the dark' :)

[Guest]

Thanks Paul,I figured out what you meant by the hierarchy utiliy just after I sent the post. I am farmiliar with that area after some stuggle to remember where it was several days back. I have just downloaded and installed the two programs you mentioned and followed the instructions carefully and even cut all but a few cockpit parts from the model to try to simplify it and make the "experimental" time shorter. Still nothing shows up in FS VC mode.Steven

[Guest]

SWEET! Another Beechjet soon to come.Looking good!

[Guest]

Sucesss, I have found the interior! It must have been the old MAKEMDL.exe as the problem. I went backward a few steps and set up without the commander program. I made a complete copy of the model and didthe two group thing and the BGL export. I then redid the export and used the MDL output. The mdl made both files and TADA!!!All that was needed then was to tweek the aircraft.cfg the get the pilot inside the cockpit instead of standing outside looking back at the plane wanting a ride inside for the first time.Thanks again for you contribution now on to the next thing, the gauges.Steve

[Guest]

>Sucesss, I have found the interior! It must have been the >old MAKEMDL.exe as the problem. I went backward a few steps >and set up without the commander program. I made a complete >copy of the model and didthe two group thing and the BGL >export. I then redid the export and used the MDL output. >The mdl made both files and TADA!!! I'm happy that you got it working. I see to recall asking if you were using the latest MakeMDL.exe program... If you're wise though, you'll put both MiddleMan and MDLCommander back in the path. Trust me, you will find it useful before long... :)