Jump to content
The simFlight Network Forums

aburley

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About aburley

  • Rank
    Member
  1. Thanks, Andy! Now that the ASN patch is out, cant wait for my EGLL-KSFO flight tomrw!
  2. If ASN integrates / maninpulates weather the same as FSUIPC does, does this mean that if using ASN with FSUIPC 4.926, the settings for weather smoothing and turbulence / gusts / varience suppression in FSUIPC will have no effect? In only ask because i am in the process of reinstalling Windows, and was wondering what settings in FSUIPC i should use. With Active Sky Evo and 2012, the guys over at FSLabs suggested this in the fsuipc.ini file: TurbulenceRate=0.5,2.5 TubulenceDivisor=40,40,80,80 If this is no longer needed, then i can cross that off my installation checklist! :) Thanks, -A
  3. I have been reading what you write. Obviously misunderstood what you meant, thats all. This kind thing is new to me, so im having trouble getting my head around it. Its not a straight forward subject as im sure you can appreciate. From the documentation: "Elevator trim control input: –16383 to +16383" I understood that as 'the input from my controller [wheel] to the sim From above post " ...will almost always read the same value" I understood that as the AP trim when the AP is off would read the same as the control wheel input. "and 0BC2 is the indicator" As in what the AP is doing to the trim. So... 0BC2 is the trim value that is applied to the plane, be that from the hardware or AP. Offset 3338 seems to be the one for my wheel. Thanks. -A
  4. So to summarise, 0BC0 is the hardware input, 0BC2 is the AP 'input'. Match 0BC0 with 0BC2, job done. Excellent, thank you again, Pete!
  5. Exactly. I will be adjusting the wheel myself to match the output from the wheel to the FSX trim. In the FSUIPC for Programmers PDF, will 0BC0 be the one i need for the wheel (bearing in mind i have set a slight slope in calibration). Im very sorry, but im not seeing the offset for the current FS (AP applied) offset. Maybe 0BC2? Thanks for help, Pete.
  6. Say my trim axis at 100, flying level. The FS value would be the same. I then engage AP and ascend 3000ft, possibly change my airspeed and the FS trim value changes to say, 300. My wheel would still be on 100, causing a pitch change when the AP is disengagd. So my application will constantly read the FS value as it changes. Just before i disconnect the AP, i wil move the wheel so it matches. I found that moving the trim wheel does not affect the AP - some planes will disconnect the AP if it detects suffient input from an axis. Not so with the Carenado CT210, which is what i fly with. So i am not planning on using the trim disconnect option in FSUIPC when AP is engaged option in FSUIPC in this case. Good thought about running out of range on the wheel - i didnt think of that. Mind you, if i switch on the AP when the plane id trimmed, i would have thought that the 'adjustment' i need to make would be minimal. When flying the CT210, i dont like to use the AP; its mainly for when i need to leave my desk for a short while. When i return, i switch the AP off. The whole reason for me doing this is for those ocassions where i change speed, altitude, etc. using the AP functions and the trim would change. Like i say, its not a perfect solution to work around how they built the wheel - just as idea i was kicking around.
  7. Hi guys, I would like to write a small external utility that can read the FSUIPC output from a given axis, namely the Saitek Trim wheel. I would also like to read the current FS value of the trim setting. As we know, there is a problem with the Saitek wheel hereby it remembers its current position and throws that back to FSX when coming out of autpilot, causing a sudden pitch change. The reason i would like to read the two values is this: While AP is switched on the values of the wheel and the FSX trim differ as the autopilot changes the trim. If i could see the values in my application, i could match the wheel value with that of FSX, so the wheel is synced (albeit manually) when exiting AP. Probably not the cleanest way of doing it, but would be interesting to give it a stab. I read with interest this thread, but the wheel just doesnt feel right unfortunately. I know C# pretty well, and have the necessary .dll registered in Visual Studio. If i can get some pointers as to what offsets to read for an axis value and the FS value, etc., that would be very welcome. These are the only areas im getting lost on! :) Thank you for your help. -A
  8. "Why do you need different settings for selecting flaps going up to those going down?" I was trying to set ranges, for example flap 1 = range 0 - 100, flap 2 100-200, flap 3 200-300, etc. up to full flaps, taking 8 ranges detents. Then the same, but with the 'up' checkbox ticked, totalling 16 detents. I just saw the range option on the axis; didnt know about the flaps assignment. I have just got new hardware, so I have never done it before, and went about it the wrong way that all. Used the flaps assignment as you suggested - works a treat! Thanks for helping me out, Pete! :) -A
  9. Hi everyone! I have just got a Saitek throttle quadrant, which works great and is picked up by FSUIPC fine. I thought for the PMDG 737 NGX, i would use a spare axis on this unit to set up a profile specific setting to control the flaps. There are eight flap settings on the 737 NGX, and i have programmed my axis in increments all the way from flaps up to flaps full. Works fine. My problem comes when making the increments to bring the flaps back up - i can only have 10 ranges, and i have used 8 already just to get the flaps down all the way. I was wondering - is there some setting anywhere whereby i can automatically reverse my 'flaps down' increments to save re programming and hitting the limit of 10 ranges? Can the range limit of 10 be increased? Or am i unfortunately out of luck? I have the latest FSIUPC version (4.921f) as i write this if it helps to know. Thanks for your help, i appreciate your time. Adrian
  10. Hi again, Pete! Over the weekend, I have tried your suggestion about changing AutoScanDevices to No, and it has definitely helped. My controllers no longer disconnect when opening FSUIPC. Thank you for your help! Adrian
  11. I always leave my controllers plugged in all the time, and in the same USB ports, so im hopeful on the AutoScanDevices option. The 'never' flag would definitely be useful. Thanks again for all your suggestions, Pete! Very much appreciated! Adrian
  12. Thanks for replying so quick, Pete! "Is this all controls, axes and buttons? Does it only affect axes and buttons assigned in FSUIPC, or in FSX too?" Nothing is assigned in FSX - all FSUIPC. This issue affects all buttons and controls. Start FSX, they are fine. Open FSUIPC options, and nothing (and remain dead when returning back to FSX). So, they die when opening FSUIPC... Sometimes! :) I have not tried the autoscan config you mention - sounds interesting! Are there any drawbacks to making this change, for example will changes to assignments still be applied immediately? "A clean install!? It messes you installation up?" No, this problem has not caused long lasting problem - i am just thinking in the event that FSX has to be reinstalled for any other reason.
  13. Hi guys, Obviously, this is a Windows 8 thing, not a problem with FSUIPC. And this post is just a friendly suggestion to throw and idea out there. :) Using Windows 8, my sticks and throttles work fine, but sometimes if i open the FSUIPC option dialogue box (or any dialogue box within FSX), my controls suddenly stop responding when i close the box and return to FSX. The only fix is to restart FSX. Like i say, this only happens some of the time when opening the options, I cant seem to replicate the issue every time. I was setting up some profile specific buttons on the 777 last night, and on 5th restart of FSX, the controls were still alive after exiting the FSXUIP options. It can make setting up profiles frustrating for assigning buttons. It would be very handy to be able to access the options dialogue from outside FSX as a stand-alone application. That way, we would be able to assign buttons to a new aircraft without having to worry if the controls might stop working; set the profile specific new plane up in the 'seperate' application, start FSX and be done. I think this would save the 'hit and miss' nature of FSX on Windows 8 and save a ton of time setting up a clean install of FSX. Thanks! Adrian
  14. Hi Guys, real quick question here: When i press Fly Now and FSX starts, can i set FSUIPC to fire a keyboard command automatically everytime? There are a couple of things i need to do, but for example, pressing the Alt key for 2 seconds will hide the FSX menu at the top of the screen. How would this be done in FSUIPC? Thanks! :) Adrian
  15. Not sure if this helps, but this site contains the latest cycle of navaid updates for all of Europe - not for FSCommander, but for FSX itself. You should find they update the ones you find as missing. It might be worth re-running FSC's database manager after updating - Volker, would this need to be done? Let us know if it worked.
×
×
  • 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.