I am creating a Tactical Situation Display (TSD) Gauge to replicate the one in the T-6B that I am currently flying, which is essentially a GPS gauge that only shows the MOAs we fly in, I have successfully gotten it to only show MOAs however I cannot change the color of the Airspace borders to white. Even after editing the ColorLayerAirspace variable it only seems to change the brightness of the Layer.

 

-Matthew Chase

Unfortunately, that's as far as I have gotten with Airspace color, too. Nor can the line width of Airspace be changed - AFAIK. Maybe we will get lucky and someone knows a way to deal with this.

 

Bob

I investigated airspace boundaries with the following results.

 

 

 

Not all types of boundary are implemented, and I believe the colours and line styles are hard-wired.

Thanks for your replies guys! It's more of a cosmetic thing I guess but I'm trying to make my gauge scan as similar to the real airplane as I can, but maybe theres just a little perfectionism mixed in there. I really appreciate the responses.

 

-Matt

USCG

Student Naval Aviator

Matt

 

I'm trying to do the same for a radar overlay , I think a clue might reside in the following link :-

 

https://www.google.com/url?q=http://forum.avsim.net/topic/259780-current-airspace-frequency/&sa=U&ei=LdCgT7L0KJHsmAXi7M3DCA&ved=0CAUQFjAA&client=internal-uds-cse&usg=AFQjCNE3YS3WGWACeOGiM_BJXuXT3pBBrw

 

Cheers

Karol

Matt

 

I'm trying to do the same for a radar overlay , I think a clue might reside in the following link :-

 

https://www.google.c...iM_BJXuXT3pBBrw

 

Cheers

Karol

 

I don't believe so, unfortunately. That link discusses the ability to display airspace types using the gps variable NearestAirspaceQuery, but that variable does not control the color when it is rendered.

 

It seems that Matt has already successfully used NearestAirspaceQuery when he says that he has gotten his display to show only MOAs.

 

Regards,

 

Bob

Propwash

 

The SDK does have color for airspaces , the problem being that there are multiple types as detailed

in that thread , each would need to have a color entry rather than the usual single color in the

custom draw.

I am assuming that each airspace has an "n" as shown in the nearest airspace thread.

Each airspace 'n' and color would need to be listed and defined in a macro , and the

macro called in the custom draw.

 

Cheers

Karol

To clarify my previous post (#3), I needed to add some missing ATC boundaries to FSX. I found the hard way that only those that have Text and Line entries in my table were acutally displayed. I assume from that the others aren't implemented.

I vaguely remember seeing 12 working airspaces, but cannot remember where ,

your 11 previously mentioned , plus ( '0' none ) would give the 12 airspaces.

Perhaps the balance of the 23 airspaces were to have been the subject of an update to FSX

that never eventuated .

 

It would be nice to be able to both change the boundary colors and to reduce the line

thickness.

 

Cheers

Karol

Propwash

 

The SDK does have color for airspaces , the problem being that there are multiple types as detailed

in that thread , each would need to have a color entry rather than the usual single color in the

custom draw.

I am assuming that each airspace has an "n" as shown in the nearest airspace thread.

Each airspace 'n' and color would need to be listed and defined in a macro , and the

macro called in the custom draw.

 

Cheers

Karol

 

Hi Karol,

 

Yeah, I am aware of the ColorLayerAirspaces variable and the various airspace types in the gps module. But, still, I am of the opinion that MGH is right when he says the color and line style appear hardwired.

 

However, if they could be changed, then I think you are correct that probably Microsoft would have used the airspace FAC_BV_TYPE value to identify individual airspaces. But the SDK gives no indication that this is possible or any suggestion of xml syntax.

 

Bob

Hi Bob

 

I suspect that you and MGH are right.

I think that FSX and its SDK's are an awesome platform even though it occassionally gives us

heartburn when we try to milk it.

I do hope that LM with their resources are able to unlock and publish further variables over time.

 

Cheers

Karol

I do hope that LM with their resources are able to unlock and publish further variables over time.

 

Karol,

 

What is LM, and what variables are locked?

 

Bob

Bob

 

LM are Lockheed Martin and their Prepar3D based on ESP a sim engine similar or compatible to FSX.

As is known MS stopped debugging and developing FSX several years ago , however LM have and

are continuing to evolve their platform to increase its capabilities as a simulation system for

land , sea , and air applications able to host multiple users with new viewing options.

To achieve that end requires further debugging and expansion of existing variables as well as

creation of totally new variables.

As they are embracing developers to provide addons , it is reasonable to presume that the new

variables will be published and that the SDK's will be expanded and improved.

While we are grateful that we have the SDK's for FSX they can be a puzzle for developers

to understand.

 

In the subject of this thread and the linked thread we have 23 airspaces that possibly exist

however no published variables for them whereby we can vary or control their appearance

in an instrument display.

As we try to replicate real world instruments and capabilities we need access to varaibles

to do so.

 

Unfortunately the preceeding does not help solve Matt's problem in FSX .

 

Cheers

Karol

LM have and are continuing to evolve their platform to increase its capabilities

 

I'm sure Lockheed Martin have some very talented people and I wish them luck. Prepar3D looks good so far. I hope they find that the market for Prepar3D (at least for the US$50 Academic license) is big enough to sustain its development. Are you a Prepar3D Registered Developer? If so, how thorough are their SDKs, and can you change airspace colors and line widths? And on that topic, I also hope that potential Developers view the market potential as big enough to spend their time on Prepar3D. Who knows? Time will tell I guess.

 

Anyway, I would object to any broad brushed implication that you cannot replicate real world instruments and capabilities in FSX owing to a lack of variables. Even with just XML there is so much that can be done, and done accurately. If that comment relates just to the airspace color issue, then point taken, you cannot change the airspace color or line width of the gps module.

 

Bob

LM have the in depth industrial technology base to implement some advanced features ,

in all fairness to MS the flight simulator has become hellishly complex and some

newer features really fall into the realm of specialist companies dealing in modern military

applications , systems and procedures.

In a word , I'm glad that LM are now doing these simulations.

I will be getting into Prepar3D by the end of the year when V2 is released , and start getting

their SDK's prior to that.

 

I agree, the replication of instruments in FSX is awesome thanks to talented and devoted

developers , but still we will always want better and better.

 

Cheers

Karol