Radio Stack Mod.

 

I would love to see an area available for custom radios/avionics. I use the Reality XP 530 and would have dual 530s if possible. The one works just fine now.

 

On the airspeed. It is what it is as long as it doesn't peak out past the gauge. Remember this is 'indicated or calibrated' airspeed and it will be almost always be lower than TAS.

 

Ray

 

I went for my first night flight in the Orbx area last night. Wow. Great instrument and panel lights. More kudos to the development team.

 

Ray

If I could just go crazy with the radio panel, I would make the entire area free from 3d knobs. I personally can live with it as is and be very happy. Given the choice I would move the two Reality XP 530s to the left stack to be closer to my old eyes and maybe use them in the panel more without having to use the popup, but, that is ideal and certainly not a specific request.

I guess we are demanding the same with the free radio area, Ray. Seems like a good idea as long as the folks not tweaking still receive the 3D models as it is now. I would drop in two RXP and my weather radar and would be set.

I guess we are demanding the same with the free radio area, Ray. Seems like a good idea as long as the folks not tweaking still receive the 3D models as it is now. I would drop in two RXP and my weather radar and would be set.

 

Yep, I agree. Dual 530s and Weather Radar would be great. I would put the GNS on the left side to use the radios in the GNS units and save two full slots.

 

Ray

CoolP, thanks. Makes sense now.

 

Too low and slow

Dave

From what I see here it seems that many useful addons could be placed on the panel. Would members of this forum be interested in a DIY panel model unencumbered by those knobs and radios? If so, let me know what exactly you would want to see removed, and I'll see whether I can work it in. Best give me a picture (the way Ray does, that's most helpful).

On simple solution would be to add a <Visibility> tag to the current 3d radio knobs, then add an L:var to a tiny XML "gauge" that will set the L:var to 1 if the gauge is present. By commenting out this little control gauge in the panel.cfg file, the 3d knobs would not be seen...

 

EDIT: Having read the remainder of the thread, it occurs to me that you wouldn't actually need to have two different models, if you expand the above suggestion to include automatically displaying multiple "radio stack" options.

1. Default would be the current model
    
   
2. Left_Flat_Stack.xml would swap the default mesh for left side flat mesh
    
   
3. Right_Flat_Stack.xml would swap the default mesh for right side flat mesh
   

In your [Vcockpit01] section, simply commenting out these two tiny XML gauges would be the default. Removing the comment marks would load the gauge, causing the "flat panel option" to be displayed, and hide the current 3d mesh:

 

//gaugenn=Left_Flat_Stack, 0,0,1,1

//gaugenn+1=RIght_Flat_Stack, 0,0,1,1

 

This is just a simple suggestion from someone who likes to think "outside the box..." :p0306:

You are right, the manual lists VNE and VNO. That 170 kts VMO limit came from the placard in the cockpit. Good point on the ski ops.

 

Makes sense, but the placard also has some VA on it, so how to handle that one? It's way lower.

 

Not to be read the wrong way, my questions on the speeds are nitpicking and only arise from interest, not because I think that important items are affected on that beautiful plane.

 

VA - is the Maneuvering speed. Turbulent air penetration speed. It is always going to be lower , this is to keep the wings attached.

 

Ray

Sounds like a great tip from Bill. While I haven't understood a word on the actual code stuff (cause is my brain), my guess is that it will help the Basler gauge dev for sure. Being able to switch the panel style on the fly, right? Neat!

On to a tangent. I have been working on a slightly different paint scheme for the Navy C40. I now have a C40 and a C40A. If they are different enough that anyone has an interest I can upload the new one to the library. Seeing as how it is totally fictional, there is no right or wrong, just different.

I wonder what Ray is doing when he isn't painting Navy themes. ^_^ :Peace: Either way, nice jobs, Ray.

Great job Ray. Go Navy! I like them both with a slight preference to the top one. Don't know why. Maybe more contrast???

I wonder what Ray is doing when he isn't painting Navy themes. ^_^ :Peace: Either way, nice jobs, Ray.

 

Actually, I have been cruising around the Miami area checking out that photoscenery package for the City 2012 X. And I flew the King Air tutorial from Mt. Vernon to Bowerman. I read a few pages of the new PC Pilot magazine, and I drafted another section on the Saitek Cockpit review. I've been busy.

 

Ray

Great job Ray. Go Navy! I like them both with a slight preference to the top one. Don't know why. Maybe more contrast???

Plus t'other one has got the star and bars flipped ...

Right, I have got a draft DIY panel version for those of you who want to experiment but truth to tell I am beginning to have doubts about it. It seems such a strange idea to do 2D gauges on a 3D panel. Haven't tried it myself, but here it is:

 

https://dl.dropbox.com/u/51024107/DIY_panel_01.zip

 

There are three polys following the current radio and AP locations thus:

 

DIY Model of previous post updated - now has a long planar poly on the left referencing VC_01, and the smaller bit below the Garmins pointing to VC_02.