A variable that would be useful for FSUIPC to be able to mod

[Patrick_Waugh]

In a panel.cfg, there is an section that is optional:

Day=255,255,255

Night=10,10,10

Luminous=40,120,60

Where the above values are RGB colors used to calculate the "color" of bitmaps in the sim according to formulas in the Panel SDK.

Many of us panel designers "turn off" the panel "light" while allowing luminous instruments with it on, by lowering the "Night" variable similar to above, so that PANEL_LIGHT does not add light to the panel.bmp.

Now, what would be cool is to be able to programatically adjust this, as then one could easily implement anti-dazzle lights, or allow the pilot to adjust the luminesnce of his/her instruments.

Just thought I would throw out this idea.

Patrick

[Pete Dowson]

Now, what would be cool is to be able to programatically adjust this, as then one could easily implement anti-dazzle lights, or allow the pilot to adjust the luminesnce of his/her instruments.

Just thought I would throw out this idea.

Nice, but have you any idea at all howe to get at such things "programmatically"? I haven't. I've no idea about ANY of the graphics stuff in FS. You might want to suggest this to the guys at places like Aerosoft. It is more their area of expertise I think.

Regards

Pete

[Patrick_Waugh]

Those variables are read in from the panel.cfg and stored somewhere, just like the variables you already have found.

So, not sure why you think it is another area entirely, but I'll take your word for it.

See those simple values are used by the panel system to compute the color to display each frame based on published formulas.

I'm sure it would be hard to track down where it is getting stored, just as it was likely for the many other variables you found.

[Pete Dowson]

Those variables are read in from the panel.cfg and stored somewhere, just like the variables you already have found.

So you have the correct Token Variable name for it? If it is as you say then it should be easy enough for someone to write a Gauge to control it.

So, not sure why you think it is another area entirely, but I'll take your word for it.

By "area" I mean "graphics" as opposed to, say, aircraft position or engine data or weather and so on.

See those simple values are used by the panel system to compute the color to display each frame based on published formulas.

See, you know much more about that stuff than I do.

If you can locate the information you need to read (and write?) I'll be glad to map it to an FSUIPC offset for you, but it will need someone who understands that subject (I used area before and you misunderstood me) to go find it and know how to use it. This is how many things have been built in FSUIPC. I have spent many thousands of hours hacking and tracing through disassembled parts of FS to find things, but always things I would be able to recognise if I saw them. Other folks have contributed for other areas, and so the edifice has been built, over time.

I'm sure it would be hard to track down where it is getting stored, just as it was likely for the many other variables you found.

If it is so easy, please go ahead and let me know. Thanks!

Regards,

Pete

[Patrick_Waugh]

Peter,

I think you mis-read my last statement, and seem to be intent on reading negative into it.

I'm sorry I seem to have upset you somehow. I was just asking if something had been done, or could be done. I was not implying it would be easy to accomplish, nor did I state such.

I do not have the tools needed to disassemble and trace through the code, and don't expect you to go hunting them for me. Just was hoping that others had alread solved it. Sorry to create such a bother.

Patrick

[Pete Dowson]

I think you mis-read my last statement, and seem to be intent on reading negative into it.

Not negative. It's just that you are asking for something I don't know how to provide without spending many many hours trying to look for something I don't really understand, in parts of FS I've never been before. And, on top of this, it is after three years of FS2004 when I really have to look forward to FSX instead. I've been "tidying up" all my modules over a period, ready, and hope to issue to another FSUIPC and WideFS update by the end of this week, hopefully the last before FSX.

I'm sorry I seem to have upset you somehow.

No, I'm not upset at all. I don't know how you read that. I am only saying if you or someone you know can tell me how to do it, I'll do it, but otherwise I'm afraid is isn't going to happen.

I do not have the tools needed to disassemble and trace through the code, and don't expect you to go hunting them for me. Just was hoping that others had alread solved it.

Possibly someone has, but if so they've presumably kept it to themselves. There are a lot of commercial add-ons which do some very clever things (Aerosoft being one, RealityXP another), but they keep the things they've discovered secret for obvious commercial reasons. Sorry.

If any reader here knows about these things and is willing to divulge details, please come forward.

Regards,

Pete

[Teepoun]

Hello,

 

I also search where is the "variable" corresponding to the parameter "Luminous" included in the "panel.cfg" of each aircraft.

Since the last post, the technology has evolved, and we could now achieve dynamic lighting of our "real" cockpits, with RGB LEDs strips.

This is the case for my own" 6 screens" cockpit, and where the electronic to drive the LEDs is not a problem for me (USB card with 3 PWM converters), but before I start this I need to know if this variable exists, and if it's possible to read but also to write it.
 

8 years later, maybe you have discovered it ...

Thank you for your reply.

 

Teepoun