Marcel_Felde

I forgot to mention that I also saved a new default flight without weather - didn't help. But thanks for your hint! :) I deleted all expansion dll entries from the FSX.cfg and started everytime with the permission for one further module to load. It seems to be a problem between AseData.dll and FSUIPC - at least simulator works if one of both is disabled.

Hello everyone, My FSX worked well with FSUIPC for many months now. I installed Switzerland Pro X and some Switzerland Sceneries a few days ago and additonally FSUIPC 4.853 and 4.859m for testing out that friction stuff. That day, everything worked and FSX was usuable. Now, FSX crashes about 2-3 seconds after the flight has been loaded with a problem in weather.dll. The UI loads normally and can be used. I tried different aircrafts and sceneries, a restart of the computer. Nothing worked. Removing the FSUIPC.dll makes the simulator working. I deleted and reinstalled FSUIPC completely. Also removed all lua- and other files from the modules folder , tried out a reinstalltion after putting the FSUIPC4_Loader.dll in the modules folder (is listed in the FSX.cfg). I changed my system time settings to English (USA), but nothing helped. I know, that Pete is on holidays, but perhabs someone else has an idea how to solve the problem. Unfortunatelly I don't have a backup of my old FSUIPC version... Thanks in advance and greetings, Marcel

Thanks Pete for your hint - that solved some issues. :-) I don't have much knowledge on the offsets, datatypes etc. Do you mean 66C0 and 66C2 with two bytes apart or 66C3? On most needles I would have a bad feeling to have only 255 steps... Reinhard, the fuel quantity needles are those with the highest update rate because of the shaking of the needles. Will reduce the interval for the voltmeter etc. :)

Now I got it. :) Thank you so much Pete and Reinhard! Gauges seem to run more smoothly and those "zero stutters" are away. Only some needles behave odd but I will have to check them today.

Thanks for the hint, will look for it later when the computer is at the aircraft again. I checked the version number to be 4.84 in FSX, that is the case...

Hello Pete, Those three are just part of a longer list of variables. And for example, the fuel quantity displays depend on a circtuit breaker and the indication will swap and jitter depending on engine vibrations and aircraft movements. So on most needles I don't use FSX default offsets but my own system simulation. :) Greetings, Marcel

Hello Reinhard, Thank you very much! I implemented that code and at the moment it only saves new values if I do reload the lua script. Do you have an idea what I may have done wrong? I will install the new FSUIPC again, perhabs something went wrong here. Are you from Austria? :) Greetings, Marcel

Hello everyone, I am using the follwing script for some while to save L:Vars into FSUIPC offsets to use them in hardware gauges of Flight Illusion and Open Cockpits. It works but smooth needle movements are not possible. Additionally, the offsets are set to zero frequently which results in jittering of the needles as they try to return to zero for a micro second. I tried different variable formats but nothing did help, so I assume something is wrong within the script: function datasend(time) l = ipc.readLvar("NEEDLE_VERTICAL_SPEED_RIGHT") ipc.writeUW(0x66B1,l) n = ipc.readLvar("NEEDLE_FUEL_QUANTITY_LEFT") ipc.writeUW(0x66C0,n) m = ipc.readLvar("NEEDLE_FUEL_QUANTITY_RIGHT") ipc.writeUW(0x66C1,m) -- ipc.sleep(10) end event.timer(100, "datasend") ipc.writeSTR(0x3380, "Data Module initiated") ipc.writeSW(0x32FA, 3) Ipc.sleep has been commented out to ensure that this is not the cause for the "zero effect". There is a video on youtube (Home Cockpit Servo Driven Instrument Panel) that shows great needle movements but I failed in contacting the author of the video for help on my setup. I am looking forward for any help! Thank you and greetings, Marcel

I am glad if I could be of some help. Got the problem solved meanwhile. Was a problem with the driver of the USB2Serial Cable delivered with the hardware. I downloaded the driver for an older cable, and now the 196 works fine. ;-)

Great, great! It works now perfectly. Thank you very much! :D I prefer to use L:Vars because the systems are all based on this type of variables and I need the "mixture trick" also for some other features. ;-) Yes, I am also looking at the examples provided with FSUIPC. What I am trying just now is to save my local variables (for example the fuel quantity for both tanks) in those user defined offsets to assign them to the hardware gauges. There is a circuit breaker in the cockpit which has effect on the power supply of some gauges, so if this one is switched off, the fuel quantity pointers drop below zero. So I can't use the FS Offset for the quantity here but have to switch an L:Var via the circuit breaker which influences the L:Vars to be shown by the needles. I just run into trouble linking a Garmin 196 with FSX, can I put my question in this thread or is it better to open a new one?

At the moment the gauge does not more than displaying the values. It makes sense for some axis to not directly be used on the systems. For example, the mixture lever in the full forward position means that the ratio is set manually. So if the local variable of the lever has a value of greater than 90, leaning is done manually. If it is pulled back it is used as normal. The propeller setting doesn't work before the oil has a certain temperature so this lever will also not be used "directly" and the throttle will simulate loss of power caused by engine wear. The throttle was only a test to see if I get things working: To control L:Vars by the hardware. I could send you a gauge for testing. I read through the documentation of Lua and some examples here in the forum, but didn't get it yet. But keep on trying. :wink:

Thanks for the fast answer! :-) Do the lua scripts have to be started in a FS session or do they run automatically? L:AXIS_THROTTLE is a variable I want to use to get the position of the hardware lever which will be modified and saved into the FS Throttle setting. The value of both variables are displayed in a gauge. So it is a variable of my own. 1=L:AXIS_THROTTLE=SET,2 results in a display of "00002" in my gauge. 1=L:AXIS_THROTTLE=SET results in the display of "00000" also I am moving the axis. The axis works fine as I can see during asignment in FSUIPC.

Hello there, I am looking for a solution on using Gauges from Flight Illusion with L:Vars. In the software of FI, offsets from FSUIPC can be used to move the needles, and I read that there are user defined Offsets in FSUIPC available. Is there a way to read L:Vars and write them into those offsets? Another question: I created a Macro for a L:Var and wanted to asign an axis to it. The axis works, and if I asign "1=L:AXIS_THROTTLE=SET,2" to the variable, the value is correctly displayed in the variable. But if I use only "1=L:AXIS_THROTTLE=SET", the axis doesn't influence the variable. Any idea what the problem could be? Thanks a lot and greetings, Marcel