Slopey

Hi Pete, Yes - I think there's a problem with semantics here. His reference to "running" AirHauler really just means the installer, which has FSUIPC4 included. I'll go and email him and get him to uninstall and re-install FSX, and install FSUIPC4 from here - and we can try that and see if it works. If it does, I'll then get him to install AirHauler, and we can see if that works. (as an aside - not setting anything which would affect control surfaces on the failure front - it's the vacuum system/ASI/VSI/DI/AI, and flaps and gear only on the hydraulics). Let me go back and get some definate answers, and I'll report back. Kind Regards, Duncan

Hi Pete, I'm not doing anything controller based with AH and FSUIPC. All I do is read lat/long/vsi etc. The only writes are the mission text window, and toggling failures. Note that if he installs FSX clean, and then installs FSUIPC4 from your website (without going near the AH installer), he still gets it. It's definately not an AH problem as he can reproduce it without running our installer. Cheers, Duncan (AirHauler Developer).

Hi Pete, Just to follow up from the AH side. Was working fine until they installed FSUIPC, and now the yoke doesn't work. It's not AirHauler, as it's not even running when they get these issues. If they start FS natively and create a flight, it still doesn't work. If they do a bare FSX install, it works. If they then install FSUIPC4, it doesn't. As I understand it the Yoke doesn't use FSUIPC for connection to FSX so dunno what's up with that. (however I do note the Saitek forum is littered with users having problems with the yoke) Kind Regards, Duncan.

Hi Pete, never mind - just a shot in the dark. I was hoping the bottom left text message would be stored at an address you might have come across before, and could be interrogated. :) Cheers, S.

Just a quick one for Pete, When in FSX and using "instant replay", there's a message in the bottom left of the screen which says: "Replay: XXX - ESC to Stop" where XXX is the time remaining. Would it be possible to check for that message (it's the same place as the "BRAKES" and "SIMULATION PAUSED - Press P to continue") to determine if 0628 should be 1 or 0? You've probably thought of this already - I seem to remember doing something similar a few years ago and checking memory locations for specific text to set a flag with. Just a thought, Cheers, S

Ah ha!!! Perfect - works like a charm!! Many thanks phenty - I didn't realise I could use the double directly! Works perfectly now! Many thanks to both!! :D :D :D (I'll let you know if FSX uses the values correctly Pete!).

Actually, scratch that - I've tried it again, and it's now not working (yes, you're correct, set - process - sleep, typo at my end ;) ) I'll see if I can get it to work again, and I'll report it to MS.

Hi Pete, I'll check that for you (off the top of my head, unless I pop up the Payload dialog in FS and get them to Ok it, it doesn't). (In answer to a previous query btw, the fs date reported by FS9 does appear to be Zulu). I have the correct number of payload stations. I've worked out a way to get it to work but I'm not sure why it is - I'm sure you'll know ;) If I write each value with an FSUIPC.Process after I assign it, then "sleep" for 3 seconds, it works perfectly. But if I write them all first, then do a Process. It doesn't work. i.e. if I want to load 1,2,3,4,5,6 into the first 6 payload stations, then set - sleep - process in a loop works ok and I get 1,2,3,4,5,6 in FS. If I set them to the values first, then do a process at the end of the loop, I get 1,6,6,6,6,6 in FS. So - I've found a workaround, so not too much of a problem - my user will just need to wait a little minute while the handling agents load up the plane :)

Hi all, (FSUIPC 4.40, FSX) I'm trying to write payload information to FS in VB.net using the .Net client DLL, but I'm having problems - I'm almost sure it's due to the way I'm handling byte arrays and conversion from doubles - I'm not 100% up to speed on that. Anyway: I've declared an array of payload offsets with: Public myPayload(60) As FSUIPC.Offset(Of Byte()) For n = 0 To 60 myPayload(n) = New FSUIPC.Offset(Of Byte())(&H1400 + (&H30 * (n - 1)), 8) Next Any after an FSUIPC.Process, I can read the payload values for a given number of stations using For n = 0 To stations - 1 myArray(n) = BitConverter.ToDouble(myPayload(n + 1).Value, 0) Next And that works perfectly. Now, once I've changed the values, I try and write them back with (cargoArray() holds the station weight values as doubles) Dim dblarr() As Double = {0} Dim test() As Byte = Array.CreateInstance(GetType(Byte), Buffer.ByteLength(dblarr)) For n = 0 To stations - 1 dblarr(0) = cargoArray(n) Buffer.BlockCopy(BitConverter.GetBytes(CDbl(cargoArray(n))), 0, test, 0, Buffer.ByteLength(BitConverter.GetBytes(CDbl(cargoArray(n))))) myPayload(n).Value = test Next FSUIPCConnection.Process() When I run this code, all the payload stations get set to the value in the last station I set. If I run an FSUIPCConnection.Process after setting each myPayload(x) element, I get varying results as if it's using certain values to set multiple payload stations - for example, if I populate cargoArray with an incrementing value from 1 to 10 and set that to the appropriate payload station (so I should see 1 to 10 assigned per payload station in FS), the first 3 are 1, the next 5 are 7 and the last 2 are 10. Does anyone have any thoughts? Am I converting the double to a byte value in the appropriate manner? Have I missed something obvious? Many thanks, Slopey.

IIRC you can change the colour of the text to white from the FSUIPC options/ini file? But its either white, or red.

Hi Pete, In Both ;) Don't worry about doing it - I'm looking it anyway and will report back :) Just wanted to check in case it was an easy one! Will let you know later today. Cheers, Slopey/Duncan.

Hi All, Is the day of year value at 023E a local time or zulu time value? Kind Regards, S.

Hi There, excuse my naivety, but how does a simulator with 360 degrees of pitch actually work? Not the mechanics, but the forces on the user. If I put an aircraft into a sudden climb/dive, or loop, there are G forces acting on me keeping me (or trying not to) in the seat. With a static simulator on the ground, would gravity not interfere at pitches above +/- 90 degrees to give an inappropriate sensation? Just curious! Cheers, S.

Oh - and before I forget: 0B6D DI/Heading - this fails ALL heading indicators in the cockpit - even the magnetic compass, which is a little wierd, but it does fail them.

Just to follow up, so far I've tested 0B64 ADF 0B65 ASI 0B66 ALT 0B67 AI 0B6D DI 0B6E VSI And they all work as expected. 0B73 Vacuum - doesn't appear to work, however, I'm not sure if all it does is fail the gauge. It certainly doesn't fail the instruments you'd expect to fail with a vacuum failure. Also, COM1/2 on 3BDA/0B68 I can't get to fail either (and possibly the same for Nav1/2?) - it's always possible to contact ATC with the fail flag set, but I guess that's something internal to FSX. Good news on the hyrdaulic front - I would have got round it by continually setting the appropriate value to whatever it was when the "failure" occured, but it'll be neater with the next version :) Anyway - hope that's of some use. Cheers, S.