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

Hi all, I was rummaging around last night trying to figure out how to select a particular camera with a hardware switch when I stumbled over these controls VIEW_AUX_00...05 An old post from Pete D mentioned that he was aware of them but didn't know what they were so it got me wondering if anyone ever figured out how to control them? They're clearly a collection of additional cameras and they're exactly what I'm looking for because I can invoke each of them from a single key press or button push but I'd be interested to know if anyone figured out how to configure the view type, angles, zoom etc? Cheers all Ian

Hi Pete, I've tried the latest beta (4.541) and the problem appears to be solved so many thanks your efforts! All the best Ian

Thanks Peter, sorry for the delay, something cropped up last night and am at work at the moment. However I'll take a look at the new version when I get in this evening and report back asap, Best as always! Ian

Hi Pete I'm getting abends starting FSX with the new beta module FSUIPC 4.5.3.9 The previous beta worked fine but with this one the FSX form opens as a completely black window and after several seconds I get the "FSX has encountered a problem and needs to close" dialog. The FSUIPC log is pretty sparse so I'm including it below and I took a look in the Event log - the abend is also shown below. Let me know if you have time to look at this and need anything other info: All the best Ian System Spec =========== Gigabyte Alive STAT2 Glan motherboard Dual 3.0Ghz AMD Athlon CPU (3gb) ATI Radeon HD4800 graphics card Sound Blaster Audigy sound card ATI High Def Audio sound driver Maxronix MX98715 Ethernet adapter Windows XP SP3 FSX 10.0.616370.0 FSUIPC 4.5.3.9 GoFlight Inc GFDevFSX.exe 1.76.0.5 ********* FSUIPC4, Version 4.539 by Pete Dowson ********* Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" User Name="Ian Niblo" User Addr="xxxxxxxxxxxxxxxxx" FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=255 1187 System time = 29/09/2009 18:44:30 1187 FLT UNC path = "\\FLIGHTSIM\MyDocsFSX\" 1187 FS UNC path = "\\FLIGHTSIM\Microsoft Flight Simulator X\" 1969 LogOptions=00000000 00000001 1969 SimConnect_Open succeeded: waiting to check version okay Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 29/09/2009 Time: 18:40:27 User: N/A Computer: FLIGHTSIM Description: Faulting application gfdevfsx.exe, version 1.76.0.5, faulting module gfdevfsx.exe, version 1.76.0.5, fault address 0x000268da. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 67 66 64 ure gfd 0018: 65 76 66 73 78 2e 65 78 evfsx.ex 0020: 65 20 31 2e 37 36 2e 30 e 1.76.0 0028: 2e 35 20 69 6e 20 67 66 .5 in gf 0030: 64 65 76 66 73 78 2e 65 devfsx.e 0038: 78 65 20 31 2e 37 36 2e xe 1.76. 0040: 30 2e 35 20 61 74 20 6f 0.5 at o 0048: 66 66 73 65 74 20 30 30 ffset 00 0050: 30 32 36 38 64 61 0d 0a 0268da..

Ah rightyho, thanks Pete! Ian

Hi Pete I noticed there's a drop-down box on on one of the FSUIPC config tabs that allows us to select which data is shown as the TCAS identifier. But there doesn't appear to be an option to show the multiplayer callsign. Is it possible to add that so programs like FSCommander display our VATSIM callsigns agains the displayed aircraft? All the best Ian

Exellent idea, thanks Peter. Must be honest that hadn't occured to me but it's a good solution that I can work into my code quite easily! Best as always, Ian

Hi Peter, I appreciate this is squeezing a square plug into a round hole but I was wondering if the "Battery Never Dies" check box in the FSUIPC dialogs has an accessible offset I can use? (I'm trying to simulate ground power). The offset at x32F6 seems to offer some control over that checkbox but only in so far as it seems to disable the option itself. I'm really after a switch that toggles the battery behviour (normal or lasts forever). My new overhead panel has a switch for ground power and at certain airports (logic tba) I want to light up the Ground Power Available annunciator. By flicking the switch when that light is on my battery will never die, effectively simulating external power. At other airports with no ground power I won't have this option so I'll be left with a normal battery life and an APU. Not essential but it'd be a nice addition to my overhead if it's possible? Have a good bank holiday, All the best Ian

Hi Pete, the offset is 6e4f6e65 but don't forget that this it's now reporting combatfs.exe as the failing module, not FSUIPC. Thanks again! Ian

Hi Peter, got a little further this time but I'm now getting an abend in the CFS1 exe when I click Fly Now. I''ve installed CFS2 and the FSUIPC.DLL works so I'll have a play over the weekend to see what's available to me. I wouldn't spend any more time on this Peter, it's really just an experiment to see how much of my homebuild could be 'plumbed' into a fighter sim but it's no real biggy if I can't get it working, and as you said yourself these combat sims are really old! Appreciated the help though! Ian