nauwa

I doubt it would be a hardware problem as when I look at the "axis assignment tab" in FSUIPC, it still works giving me perfect values from -16383 to + 16383, it just don't send it to the offset (or I can't read it from the offset). It might be on the SIOC side, but I don't see the difference from the other offsets I read from FSX via FSUIPC that continues to work when the offset from the axis don't Well, I'll try more tomorrow with logging ON. Regards Johan

Thanks for the fast reply Pete! Well I fired it up today to try to log some data for you, but to my surprise everything worked OK, for a while, then it started to send 65536 or 0, nothing between. Restarted both computers and tried again. At first all OK, but after about 30 minutes I lost all data on the offset, only receiving 0, no matter how I turn my potentiometer. Really strange behaviour. I'll continue to test and will log next attempt. Regards Johan

Hi Pete, I'm trying to assign an axis to "send to FSUIPC offset". The axis is connected to a Leo Bodnar joystick interface. I assign the axis to Offset x66E5 as a word. In the FSUIPC Axis assignment tab everything looks good, moving the axis gives me values from -16383 to +16383, but when I read offset x66E5 I get nothing. Well, i do get some glitches near middle of the axis. The most strange thing is that it worked perfect for a few minutes in the beginning, but then died without me doing anything. The hardware is working, perfect stable values from the potentiometer, and I still get perfect values in the "Axis assignment tab", but on the Offset, nothing. FSUIPC version 4.868 Running SIOC version 4.3 on networked computer via WideFS 6.991 where I try to read offset x66E5 Do you have any idéas? Regards Johan

Dear Sirs, We are using FSUIPC and WideFS latest versions with FS2004. In our SAAB Viggen cockpit simulator, we need other self made programs as well, to fully simulate the cockpit behaviour. In early stages of the cockpit, we used joystick buttons to send commands by widefs to the client programs, worked fine. Today, the cockpit has grown, and we are not able to use joystick buttons due to the many switches. Instead we have used free offcets in FSUIPC to send the data. This make it possible to use Opencockpits IOCards and SIOC to program the logics in the simulator. But as we started to send the commands this way, there is a notisable delay in the communication between the cockpit and our other programs. When we test on one computer running all programs there is no such delay, so we think it is in widefs. Does anybody have any idea if it's possible to solve this delay, btw. we are running the sim on 4 computers on a 100mbit network.

I don't have a clue where to look, but I will continue my research. The only thing I know is that there is an option in FS to set it to on or off. Thanks Pete for the quick reply Johan

I wonder if it's possible to change the g-force value when the screen begins to "black out". In my SAAB Viggen cockpit simulator, I have a working g-suit, g-simulation in the ejection seat and now a possibility to dim all cockpit lights. The original Viggen simulator dim the cockpit when exeeding +6G, but MSFS darkens the screen above +4G. I would like to be able to change in FS so the screen "blacks out" when exeeding +6G so I have it in sync with my hardware. Perhaps an idéa for next FSUIPC version if it is possible. Regards Johan Nauwelaertz de Agé The Mobile Flightsimulators Sweden