BAW019

Cheers Thomas - that seems to work fine 😃 Many thanks, Ian

I've written my own upper EICAS that shows the current throttle lever positions on the N1 gauges (0-100%). This helps me sync my throttle levers to the auto-throttle settings before I disconnect it. This works perfectly for the default 737 but for the default 747 I get unexpected results. I've calibrated (and use) throttle axis 1 and 2 via FSUIPC and I've used the options pages of FSUIPC to map 1-<12, 2->34 for the 747 profile (the profile specific box is checked). However for the default 747 although throttle 1 correctly maps engines 1 & 2 as 0-100%, throttle 2 maps engines 3 & 4 as 50%-100% - they never goes below half when throttle lever 2 is fully closed. I've dumped the raw data from offsets 3332-3336 and with my throttles closed I get 0, 0, 8192, 8192 (as opposed to 0,0 for the 737). Anyone know where I'm going wrong? For info I'm using Prepar3D v4.3 with payware FSUIPC v5 on Window 7 64 bit. Thanks for any suggestions and apologies if I'm being a dufus! Regards Ian

Solved it! The Flight Model\General slider in the Settings\Realism menu appears to affect the battery. Anything less than the halfway mark and the battery stays fully charged. Thanks for the input Pete - I suspected FSUIPC was innocent in all this but thought I should throw it out there. Regards Ian

This has me stumped - would be grateful for any ideas from any of you out there! I have a new installation of FSX on my Office PC for testing purposes. There's nothing fancy about it, it's simply FSX Acceleration with no add-ons except FSUIPC. When I shut down the default 737's engines with the start levers they spool down to zero on N1 and N2 but when I switch to battery power the battery never drains. I've left it for over an hour and it's still at 24v and 37amps. Just to try to drain it I've got all the lights on and the pitot/anti-ice heaters are blazing away, the APU is off, the engines are off and the power selector is set to 'BATT', but nothing seems to drain it. I've double-checked and the FSUIPC option to keep the battery alive is not checked so I'm baffled. What did I miss? Cheers Ian

Ah, that explains it. Many thanks Pete - most useful! Regards Ian

Thanks Pete, unfortunately they only seem to have 88 bytes and I need a min 90 and pref up to 200 bytes. Are there other areas I can use that won't trample over vPilot/Squawkbox/FSInn and ActiveSky? (Not sure if they all use custom offsets!). Regards Ian

Hi Pete, I've revamped my flight instrument software and it now uses a lot of custom offets (about 90 so far). I wondered if you could point me to a block of addresses in FSUIPC that are currently free (say 150-200 to allow for expansion)? I'm not after you allocating these to me as l'll never put my software on the market (it's too bespoke), but it would be useful to know that I won't be sharing offsets with other software that I might use eg vPilot. Thanks for anything you can pass on, no worries if you can't - I'll use the first chunk of x6D88. Regards Ian

Hi Pete, this is a real stab in the dark but maybe you can help. I'm trying to write a driver for my GoFlight MCP Pro and I noticed that you wrote GFDisplay a while back. The SDK has long since vanished from the GoFlight website but it occured to me that you might have a copy of the documentation for it lying about? I need the calling conventions for each entry point in GFDev.DLL. Am expecting a "No" but thought I'd ask :o) Regards Ian

OK, too bad. Thank all the same. Nope, Wideview reads the tailnumbers and uses them to match up the liveries, I'm just interested in feeding it the data it's expecting Ah, rats. OK. That is bad news from this perspective. See previous reply Of course. I'm asking you this stuff so that I'm better equipped to continue my conversation with him. Interesting point - I'll pass it to Luciano. Ian

Hi Peter, obviously it's early days yet (but not too early for Microsoft to post an advert on their site!). http://www.microsoft.com/games/flight/ Do you have any info about it yet? (Will FSUIPC be compatible with the new Flight Sim?) Cheers Ian

Hi Pete, Just a quick note of thanks for putting in the bit switches for the hydraulic pumps. They work fine and make things much easier from my perspective! All the best Ian

Sorry all, got hijacked by work. Delighted to report the problem seems to be fixed by the latest version of FSUIPC -thanks Peter. For the record, for me it was FSX and the Go Flight modules were GF-166A, GF-48 and GF-MCP Pro. Thanks again Ian

Hi Peter, it occurs to me I might be hijacking pumrigar's topic which I'd rather not do! I'll wait till you've sorted him out them I'll pick this up again - I have a work around so it's not urgent. All the best both! Ian

For info, I've also recently found that all my Goflight modules light up during the initial load of FSX (as usual) but as soon as that's complete and I'm at the gate they go dark (new behaviour - they stayed lit before). As a work-around I've removed the GoFlight component from the FSX.xml file and I launch it manually once FSX has finished loading. The modules light up and work fine after that but it's odd that it's recently started doing this. I'm at work at the moment so I can't verify the component versions but when I get home I'll check I'm on the latest ones and try to run some tests. Ian

Thanks Pete, I don't remember seeing them in the camera.cfg but will have another look to be safe! All the best Ian