Patrick_Waugh

Peter, Did you ever get my email request? Patrick

Ah thx Peter. For some reason, in my rush I had forgotten to extract the programmers guide you wrote and put it in my docs directory of my project where I would see it. You have rather complete docs, so I'm sure that will answer my question. Lately, I have just been in way too much of a hurry and I need to spend some quality RTFM time ;) So, now I have a design delima. I want my users to be able to assign keypresses and joystick buttons to switches and buttons on my panels. I'm trying to determine the best way to do this. I could use DirectInput, but I'm guessing it might be better to assign things to unused FS events and then have them assign them through FSUIPC. That way I don't have to hardcode it, or relay on reading in a config file. Patrick

Not sure if I can help. I'm not really clear on what you are needing. Sounds like you have a switch, and FS9 can't "see" it. If FS9 can't see it, seems you have to fix that first. Then, assign whatever keypress/button it generates assigned to: Increase/Decrease Helo Gov Beep (in FSUIPC) or the same in FS9's assignment dialog. Patrick

Can I discover with a read what key or joystick button a user has assinged to a particular function through the FS assignments dialog? Also, under "simulation" commands in FS-Interrogate2, I notice things like offset 2911 - Hot Button number 0-39[1], etc. What is all that, and is this documented anywhere? Thanks, Patrick

Will do Peter.

Yes, I'm using 2005 as well, and I'm still getting it. I'll play around with things and see if I can figure it out when I get some extra time.

I get the following warning: LINK : warning LNK4098: defaultlib 'LIBC' conflicts with use of other libs; use /NODEFAULTLIB:library and I'm using the LIBC.lib from the latest platform SDK. Using MS Visual Studio Pro, and just wondering if anyone knows of any library conflicts, or what I might check. Patrick

Peter, Be happy, my new panel will be requiring a registered version of FSUIPC. Patrick

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

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.

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