Creating "Call-up" gauges

Probably doesn't make sense yet, but allow me to elaborate.

A friend and I are reworking the panel (and VC) for the Aerialfoundry CF-188 hornet. It has three main MFD's, one left, one right, and one down low and centre. These three have certain functions, such as HSI, attitude, engine info.

We have included eric marciano's Radar gauge that pops up in the 2D panel right overtop of the right MFD by pressing SHIFT+7, it is fixed and locked in position right overtop of it to look as if you just switched the display info on the MFD.

We are trying to do the same thing for the Virtual cockpit, but are absolutely stuck. What we want, is to be able to use the HSI (right MFD) whenever we want in flight, but simply click a button (or press a key command) and have the Radar pop up over the right MFD in the VC.

Is this even possible? Is it really complicated to do? If you don't understand what I'm asking, I can provide images to try and explain.

We're both very smart people and pick things up quickly, and would be more than willing to build the gauges ourselves. WE just need to know if the efforts are in vain, or if its actually possible to do. And if so, where do we start so we can learn how to do this?

Thanks in advance for any and all assistance!

-Rob
 

n4gix

Resource contributor
Rob, what you want to do is possible, but only if you have access to the .max or .gmax file and can modify the VCockpit layout.

What is required is a separate gauge polygon for the "radar display" that would show/hide on command over the existing MFD gauge polygon.

From what you've written though, I suspect that you do not have access to the model files, so unfortunately the above is of no help whatever... :rolleyes:
 
Ah ok... so I guess the only way to do it would be to get in contact with Aerialfoundry and somehow get a hold of the source files...

Probably not going to happen. :p


Okay, second idea then. Both of the MFD's are able to switch between various windows. For example, the right MFD can go from forward look HSI, or complete HSI, and some other little things. These are all different windows within the one gauge. After looking at the gauge itself, it looks like it is basically just code that brings up the next display when you click the button.
What if I was to include the Eric's Radar gauge *within* this gauge, and add the code so its just another one of the displays that the MFD has the option of cycling? Does that make any sense?

Boy.. I wish things were as simple as they are in my head.

Thanks for the help!! :D



P.S. Just had another idea as I was explaining your post to this friend of mine. Eric's Radar guage also has the ability to switch between multiple different modes. Would it be possible to add another mode that just makes it invidible? The modes include forward sweep, vertical scan, global view, etc. But one mode is just a blank screen. Any chance we could modify this or add yet another mode that takes it one step further to no blank screen at all? Thanks again!
 

n4gix

Resource contributor
Sorry to say, none of those ideas will work either... :banghead:

1. You cannot load another gauge within a gauge.

2. XML and C gauges cannot overlap each other

3. You cannot modify a compiled .gau file without the source C code, which of course would be as likely as getting the model's source file! :eek:
 
Heh, appreciate all the info again, even if it's bad news!

Thanks for your time. I guess I'm done with this idea for now. :rolleyes:

Most of the things that go through my head, I usually just discard almost immediately because it just ain't feasible! Fun to think about though. Thinking big is how things get done 'round here, eh? :p
 
Heh, appreciate all the info again, even if it's bad news!

Thanks for your time. I guess I'm done with this idea for now. :rolleyes:

Most of the things that go through my head, I usually just discard almost immediately because it just ain't feasible! Fun to think about though. Thinking big is how things get done 'round here, eh? :p

Thinking big 'is' what gets you ahead.

Imagine taking a step back in time to FS3, and dreaming about FSX. How, you say, could you have a VC with 120,000 vertices, 2048 size DDS textures, a GPS system, cars below driving on highways, ships at sea, clouds reflecting off of the oceans... All from a simple DOS program..
 
Top