jollylaus

Pete, Thanks for the answer. SIOC is the script that goes along with Opencockpits panels. Amongst other features it interfaces to the SIM through FSUIPC. To declare a SIOC variable, which shall read/write FSUIPC offsets, you need to specify the offset, and its related size (they call it length) as specified in your Offset Status document. Regarding the Active Sky ambient visibility parameter, if it's a 32 bit floating point, the size/length of that offset (0x863C) should in my mind be 4. Can you confirm this ? I made the following small test: I have set manually in AS a visibility of 5000. - Using a LUA script I can directly retrieve that value in Offset 0x863C without further post-processing (as you said above) I use the following variable declaration: AmbVis = math.floor(ipc.readFLT(0x863C)) - The corresponding SIOC Variable declaration like this: var 6015, name Amb_Vis, LINK FSUIPC_IN, Offset $863C, length 4 (using length 4 if my a.m. assumption is correct). What SIOC reads out of 0x863C in decimal and binary format is the following : A totally different and inconclusive value compared to the LUA reading, so there is apparently something different/wrong here. The high number has lead me to the assumption that I need to 'postprocess' the value, but you correctly explained me that this is stupid. So in a nutshell my remaining question is if the size of offset 0x863C is 4 ? Many thanks, Johannes

Hi Pete, I struggle to read the Ambient Visibility Offset in meters. I'm using a SIOC script to read, interprete, and process this offset. In the end I want to have it assigned to a SIOC variable in meters. If I understand correctly the Ambient Visibility is a 32 bit floating type, i.e. length 8, and hence to be devided by 65536 * 65536. If I code it it like this in SIOC, it reads zero only. What am I doing wrong here ? Thanks in advance, Johannes

Hi Pete, as I expected it may be a silly problem, and you have well spotted it: I had baked the misalignment into my Default flight ....... Most probably I would never have identified that. We have a say in german: sometimes you don't the forest because of the trees. Many thanks, Johannes

Hi, I have recently upgraded my PC hard- and software to P3D V4/4.1. Since then I experince the issue that at first attempt to move the aircraft forward it turns right. Once I move my (separate) steering tiller the NLG goes straight, and then everything is ok. - I have configured my two Saitek Rudder pedals, and the tiller, as 'sent direct to FSUIPC' for calibration - I have disabled all controller axes in P3D - The USB controller functionality in W10 shows that rudder pedals and tiller potentiometers are working fine - Despite the above, after P3D start up, but before applying any controller input, I observe an 'initial' setting of the tiller axis of -4320 input, although it's calibrated nullzone is at 677: It may be a silly thing, but I don't get to it. Any idea? Many thanks, Johannes

Pete, you're great ! Many thanks. Johannes

Hi Pete, I'm not surprised by your question. Today I'm still on P3D V3 & FSUIPC 4. I will for shure migrate to P3D V4 / FSUIPC 5 in the future, but for many reasons this will need to go along with big soft & hardware changes to my current HC, and hence will not happen in short term (also pending on ProSim 737 V2 availability). I fully understand that you don't want to invest time in V4 anymore, so if you offer to consider my request for V5 it is absolutely fine for me. Thanks a lot for taking up my suggestion, Johannes

Pete, I have sent to you a mail with the API document. BR, Johannes

Hi Pete Is it / would it be possible to allocate FSUPIC offsets in order to interface with some of the AS weather information contained in their as_btstrp.dll ? This would allow us cockpit builders to implement through LUA/Sioc scripts extra functions like vibration generation for in flight turbulences, or weather controlled external strobe lights, which would become active in precipitation/cloud conditions only. Michael (‘Polarisfly’) has already applied such nice features in his home cockpit ( http://b737sim.blogspot.de/ ) by using an specific dll to access AS data. However I can’t get this dll run on my system, so I think the more clever solution would be to have that possibility through FSUIPC offsets. The following parameters listed in the Active Sky Application Programming Interface (API) document are required to achieve the above features: - AmbientIcing - AmbientTurbulence - InCloud - ExportedPrecipType - ExportedPrecipRate - ExportedAmbientVisibility Thanks and regards, Johannes