Jump to content
The simFlight Network Forums

BAW019

Members
  • Posts

    183
  • Joined

  • Last visited

Posts posted by BAW019

  1. 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

  2. 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

     

  3. 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

  4. 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 

  5. Sorry, I've no idea how to do that either. I'm not familiar with widevieW or any of the interfaces it uses.

    OK, too bad. Thank all the same.

    You think you should be able to change the tail number dynamically, through FSUIPC, in such a way that it somehow gets to WidevieW? Not sure how that would work.

    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

    All of the AI data read by FSUIPC for TCAS type displays is read-only. I don't know of any way to change any of it.

    Ah, rats. OK. That is bad news from this perspective.

    How? And how would it help WidevieW? What is it doing?

    See previous reply

    Have you asked Luciano at all? Seems more up his street, After all, he did write WidevieW.

    Of course. I'm asking you this stuff so that I'm better equipped to continue my conversation with him.

    Seems to me that WidevieW should be matching planes by aircraft title, not tail numbers -- after all that's the way virtually everything else selects aircraft by, including FS itself, and of course FSUIPC. Tail numbers aren't necessarily unique, whilst aircraft titles have to be (for menu and flight selection purposes).

    Interesting point - I'll pass it to Luciano.

    Ian

  6. 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!

    17. Offset 341E ("Hydraulic switch") now contains separate bits for each possibly hydraulic pump, 2^0 = pump12^3 = pump 4. These switches are tested and working.

    All the best

    Ian

  7. Hi Sascha, hi Volker

    I realise the next version may be well into the testing phase, but if you're still accepting ideas for fixes can you tweak the 'paste' function in the route string dialog?

    If I right-click and select PASTE, my clipboard text is inserted at the cursor. But if I'm typing in the route string box and press CTRL+V (to paste an enroute segment from the VATSIM route finder) it replaces the entire contents of the box rather than just inserting my route segments, so I lose what I just typed.

    Not a major flaw but it'd be nice if you could take a look!

    All the best

    Ian

  8. Hi all, I've possibly asked this before but is there any way the Flightplan window can be made into a stand-alone window (ie not part of the map window)?

    It takes up a fair chunk of my map (I use FSC on a notebook) and since I can only add waypoints if it's open it leaves me very little space on the map to look

    around.

    Cheers!

    All the best,

    Ian

  9. 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

  10. 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

  11. Hi guys, I'm not sure but think I may have found a problem with the measuring tool. The problem is that the heading shown by the measuring tool seems to change depending on the longitude at the map's centre. For example, if you centre the map on London then zoom right out to see as much of Europe as you can you find that it doesn't matter where you place the mouse cursor, any measurement due North will give a heading of 0 and 180 degrees - just as you'd expect. But if you then re-centre the map on a longitude East or West of Longitude zero and repeat the excercie you get a completely different heading for due North. Since I'm using due north as test data the latitude should have no effect and in fact the map shows lines of longitude that I'm tracing in order to estimate due north. If you centre the map on California you get a due north of about 160 degrees and in fact the value shown for due north is different wherever you centre the map which is confusing me no end! Am I doing something wrong or is this by design? Also, is the same processing used in the headings shown on the flight plan? Cheers, and sorry to be a pain! (Equally sorry if I'm being stupid!)

    Ian

    FSC 8.5 (thought in this test I'm running FSC stand-alone, without FSX running)

  12. Hiya - don't know if this helps at all but during a recent fly-in to airports in that region I also found that the transitions at other airports weren't in the AIRAC cycle but they''re all base on local fixes and intersections so you can build them yourself really easily and really quickly.

    Create a new flight plan with nothing in it then use the transition charts to simply click on each navaid until the transition is complete then save it as a route segment. You can then load it into a new flight plan and build your FP around it.

    Hope that helps,

    Ian

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.