shortspecialbus

As far as your first point, that's what I've historically done. What's normally on that is the yoke, rudder, and toe brakes. That's it. As far as controllers go, out of things that have axis, I have: a.) PFC Yoke b.) Saitek TPM c.) Saitek Cessna Trim Wheel d.) CH Pedals e.) GoFlight TQ6 As far as profiles, I kinda do have one for a lot of different aircraft, at least in a manner of speaking. The A2A Cub gets a profile with trim set to the wheel and throttle only set to the Saitek TPM. I disable mixture because while the Cub itself doesn't have a mixture, it will pay attention to the mixture axis. It also gets an axis to carb heat (which actually works as a toggle in this plane) The A2A Cherokee and 172 get a profile with trim set to the wheel and throttle and mixture set to the Saitek TPM. The Cherokee also gets an axis to an offset for a little lua script for Carb Heat :) The A2A 182 and Lancair Legacy V2 get a profile with trim set only to buttons (annoying desync issues between the axis and the buttons otherwise, and I prefer electric trim on those 2 planes for various reasons) and Throttle, Prop, and Mixture set to the TPM. The 182 also gets an axis for cowl flaps. The A2A Spitfire gets trim on the wheel, and throttle, mixture, and radiator flap go on the GoFlight TQ6 as I prefer that style throttle for a spitfire. (I know it makes no sense with a yoke ;) ) The PMDG planes get trim on buttons only, and the Spoilers, Flaps, and Throttles go on the TQ6. So, yeah, because I like the controls for each plane to be different (or sometimes an axis doesn't really work to have enabled, in the case of the trim and/or mixture in those specific cases) I have a lot of profiles, haha. There really are few common controls as a result. Don't even ask me what I do with the Saitek Switch Panel and/or GoFlight LGT-II ;) As far as your last point, that should work for what I'm looking for. I believe some of the A2A planes will do something funky with the elevator and aileron axis, so I may experiment with that as well. Addon planes have been getting pretty complex and not always entirely documented as to what they do. I like that idea, and will go back to disabling joystick in P3D as that's more along what I'm looking for, I think. Thanks much! -stefan Edit: The initial setup isn't that hard, you were gracious enough to do a "based off of" thing quite some time ago for aircraft profiles, which means I load the closest one and work from that. Also, that list there is the entirety of what I fly, except I still need to configure the A2A B-17 and the Majestic Q400, which I haven't gotten around to on the new computer.

Hi, Historically, I've always disabled the joystick in FSX/P3D and used FSUIPC to calibrate and assign everything, as I have a multitude of controllers and what I want as an axis for something in one aircraft, I don't want it in another, or I want it as something else. FSUIPC has worked great for this! However, because of some add-on aircraft that don't always play nice with that, I'm trying something new. I took a few axis that are always the same in every aircraft and set them up solely through P3D. That works fine. However, I also want to set the throttle levers on my GoFlight TQ6 to be Engine 1 Throttle and Engine 2 Throttle, at least for the PMDG aircraft. However, I don't want those axis (axes? How do I plural that anyways?) to be functional on, say, my Cherokee, since I use my saitek TPM for that. Using only FSUIPC, this is trivial and I've done it for probably over 10 years now. The problem I'm having is, how do I set the axis in P3D controls, but "block" it somehow, presumably using FSUIPC? I've tried various axis assignment options for said axis, including ignoring, sending to FSUIPC calibration, setting to <UNUSED> and anything else I can think of, but it always gets through to P3D. Is there any way to block it? Or am I going about this the wrong way? Really the issue I'm having is that the PMDG planes get squirrely whenever I use FSUIPC to control their throttles. They advise against it. Sometimes I'm able to get it to work properly, but on my new build, I don't seem to be able to, so I'd like to try using P3D for those ax(i/e)s. Any thoughts? Thanks, -stefan Brief edit: What I've always done in FSUIPC for joysticks is disable in FSX/P3D, create an aircraft profile, and assign an axis to something by sending it direct to FSUIPC calibration for, say, Throttle/Slew Altitude or whatever.

What aircraft? What joysticks? -stefan

I should be the last one in the world to comment on typos, but I really just have to say that the idea of a "Fear Lever" in an airplane is probably my favorite concept ever. -stefan

Ok. I started getting that and a StackHash error today after several months of no problems at all and no changes made at all. Seems others are getting this as well, based on a few posts in the CTD forum on AVSIM. I'll look into it a bit more. Thanks, -stefan

Hi, Just reporting a g3d.dll crash that wasn't caught. I'm not expecting you to fix it, but in case you wanted some data on a g3d.dll crash that FSUPIC didn't catch, here you go: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58 Exception code: 0xc0000005 Fault offset: 0x0006fdf2 Faulting process id: 0xbb0 Faulting application start time: 0x01ce437bd75fcddf Faulting application path: F:\Microsoft Flight Simulator X\fsx.exe Faulting module path: F:\Microsoft Flight Simulator X\g3d.dll Report Id: c972f6d2-af77-11e2-aac7-5404a63ca55d fsuipc log: ********* FSUIPC4, Version 4.86 by Pete Dowson ********* Running inside FSX on Windows 7 Module base=64380000 User Name="REDACTED" User Addr="REDACTED" FSUIPC4 Key is provided WideFS7 Key is provided 1934 System time = 27/04/2013 14:17:37 1934 FLT UNC path = "C:\Users\FSX\Documents\Flight Simulator X Files\" 1950 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1965 FS UNC path = "F:\Microsoft Flight Simulator X\" 2293 LogOptions=00000000 00000001 2293 SIM1 Frictions access gained 2293 Wind smoothing fix is fully installed 2293 G3D.DLL fix attempt installed ok 2293 SimConnect_Open succeeded: waiting to check version okay 2293 Trying to use SimConnect Acc/SP2 Oct07 3713 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 3713 Initialising SimConnect data requests now 3713 FSUIPC Menu entry added 3728 F:\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT 3728 F:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 14773 F:\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_PiperJ3_t\PiperJ3t.AIR 138123 Weather Mode now = Theme 145237 System time = 27/04/2013 14:20:00, Simulator time = 11:17:39 (19:17Z) 145299 Aircraft="A2A Piper Cub Tundra CF-DCW" 202411 Starting everything now ... 202411 Using "F:\FSX Addons\GoFlight\GFDEV.DLL", version 2.2.1.0 202411 GoFlight GFTQ6 detected: 1 device 202411 GoFlight GFMCPPRO detected: 1 device 202411 GoFlight GFEFIS detected: 1 device 205687 Advanced Weather Interface Enabled 215078 Weather Mode now = Custom 215188 Weather Mode now = Theme 215234 Weather Mode now = Custom 217996 Weather Mode now = Theme 218042 Weather Mode now = Custom 227917 Sim stopped: average frame rate for last 28 secs = 29.0 fps 325231 Sim stopped: average frame rate for last 97 secs = 29.6 fps 1761969 Sim stopped: average frame rate for last 1432 secs = 29.5 fps 2021117 Weather Mode now = Theme 2021164 Weather Mode now = Custom This undoubtedly is a different error than the one you've coded around, but I'm posting this in hopes that it might help get a fix for other g3d.dll crashes, even if less common. Thanks! -stefan

Appears to work to me! ********* FSUIPC4, Version 4.825 by Pete Dowson ********* User Name="REDACTED" User Addr="REDACTED" FSUIPC4 Key is provided WideFS7 Key is provided Running inside Prepar3D on Windows 7 Module base=120F0000 687 System time = 25/04/2012 17:36:22 733 FLT UNC path = "\\MEGATRON\Users\stefan\Documents\Prepar3D Files\" 733 Trying C:\Prepar3D\Modules\SimConnectP3D.dll 749 Found it: trying to connect 765 FS UNC path = "C:\Prepar3D\" 1108 LogOptions=00000000 00000001 1108 Wind smoothing fix is fully installed 1108 G3D.DLL fix attempt installed ok 1108 SimConnect_Open succeeded: waiting to check version okay 1108 Trying to use SimConnect Prepar3D 4009 Running in "Lockheed Martin® Prepar3D®", Version: 1.3.3708.0 (SimConnect: 1.3.0.0) 4009 Initialising SimConnect data requests now 4009 FSUIPC Menu entry added 4041 C:\Prepar3D\FLIGHTS\OTHER\Prepar3D.FLT 4041 C:\Prepar3D\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.AIR 48204 System time = 25/04/2012 17:37:09, Simulator time = 11:00:02 (15:00Z) 48267 Aircraft="Mooney Bravo With G1000" 48891 Starting everything now ... 50186 Advanced Weather Interface Enabled 320691 *** G3D bad pointer trapped and crash prevented *** 1250972 *** G3D bad pointer trapped and crash prevented *** 6034634 Sim stopped: average frame rate for last 5867 secs = 29.8 fps 7884509 *** G3D bad pointer trapped and crash prevented *** 7964522 *** G3D bad pointer trapped and crash prevented *** 8173532 Sim stopped: average frame rate for last 2126 secs = 30.0 fps 8185934 System time = 25/04/2012 19:52:47, Simulator time = 09:13:34 (22:13Z) 8185934 *** FSUIPC log file being closed Average frame rate for running time of 8010 secs = 29.8 fps G3D fix: Passes 1399489, Null pointers 0, Bad pointers 8, Separate instances 4 Memory managed: 3313 Allocs, 3313 Freed ********* FSUIPC Log file closed *********** -stefan

Alright, I've flown across most of new zealand and no g3d.dll crash, which I got pretty much every other time. I think it's good. Does it log traps anywhere? -stefan

I got an unexpected visit from some friends and some bourbon, so flightsim wasn't happening today as it turned out. I'll shoot for tomorrow afternoon. -stefan

Will do. I should have time to test it later this afternoon (CDT) Thanks! -stefan

Thanks, I really do appreciate it. If my overusage of that word in the last post hadn't already made that clear, haha -stefan

Hi Pete, I hate to bump this, but it doesn't look like LM responded at all in the thread. P3D runs significantly better for me than FSX, so I'd really like to convert to it, however the g3d.dll crashes seem more common. If I can get rid of those, I'd be exceptionally happy. In the absence of comments from LM, and if it's a quick fix for you, I'd really appreciate it if you could put the fix in as it would make a world of a difference. I certainly won't begrudge you if you don't wish to, since your reasoning is valid and it's your program anyways, but I'd appreciate it. :) Thanks, -stefan

I'll forward that along I guess, then. Thanks! -stefan

Hi, Does the same fix that you use for FSX g3d.dll crashes work in Prepar3D? It seems myself and other users are experiencing g3d.dll crashes in prepar3d. There's a thread here with more info: http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=859 Any thoughts on this? I'd love to switch permanently to prepar3d. Thanks! -stefan