September 28, 201312 yr Commercial Member For FS2Crew Airbus Voice Control users, please note that we've updated FS2Crew Airbus voice control. It's now compatible with Version 1.15. Best, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 28, 201312 yr Ailchim, lemme tell you... You're really a pain in the &@($*!!! Damn! Sent from my HTC Desire using Tapatalk 2 Please re-read the Terms of Service. http://forum.avsim.net/page/AVSIM%20Pages/terms_of_use.html This type of post is unacceptable and offensive. Please don't do that again. Sincerely, Chase My 2017 Build: Liquid Cooled i7 7700K CPU idle @ 4.2GHz | MSI GTX 1080 Gaming X 8G | 16GB's DDR4 4000 RAM | ASUS 27" 144hz Gaming Monitor | MSI Z270 M7 Motherboard | Windows 10 | Samsung 960 EVO M.2 500GB SSD
September 28, 201312 yr Can be an issue with my G940 joystick? In FSUIPC my 940 throttle goes from the -16300 values from 16300. Ok when I move back the joystick throttle to back idle FSUIPC reads 0, bat if I force the joystick more to back, reads -16300. You understand? So the entire joystick movement goes from 0 to 16300 and only less than a millimetre for the range of 0 to -16300... It's strange. It seems to be the 940. Enviado desde mi iPhone 5 con Tapatalk Pro In windows joystick control, how does it behave (outside the sim, in the windows control panel). This should tell you if you have a wanky or sticky potentiometer. Al Stiff
September 28, 201312 yr In windows joystick control, how does it behave (outside the sim, in the windows control panel). This should tell you if you have a wanky or sticky potentiometer. Yes, agreed - @Jose88, open the Windows calibration dialogue and check the range of movement. I went through this recently with a set of rudder pedals that had a bad pot - you could actually see the range getting smaller with each repeated press. Also, in FSUIPC, check to see if you've selected a reverse range for the throttle - if so, then depending on how you've set it up, it might account for the very small negative range. Resetting the axis might help cure the problem. I used a G940 for a year and really enjoyed it, but I found it was really temperamental - it would sometimes get eccentric and finally the whole unit died on me after about a year's service. You might be able to find more help for it on the Avsim hardware controllers forum - and, again, Pete Dowson is really great about providing FSUIPC support on his dedicated forum over at Simflight. Feel free to PM me if you want to keep working through it. Happy to continue reading and posting here but if it's not an Airbus problem, we might want to move to another table, so to speak... B) For FS2Crew Airbus Voice Control users, please note that we've updated FS2Crew Airbus voice control. It's now compatible with Version 1.15. Best, Glad to hear it. I've been simming for decades but I'm pretty new on the tubeliner scene - this might be my first FS2Crew purchase. Or the button version. Or both. Or the combo edition for the NGX. So many airplanes, so little time.... Sigh... Alan Ampolsk"Ah, Paula, they are firing at me!"-- Saint-Exupery
September 28, 201312 yr In FSUIPC my 940 throttle goes from the -16300 values from 16300. Ok when I move back the joystick throttle to back idle FSUIPC reads 0, bat if I force the joystick more to back, reads -16300. You understand? So the entire joystick movement goes from 0 to 16300 and only less than a millimetre for the range of 0 to -16300... It's strange. It seems to be the 940. Just some food for thought, José. I'm too using a G940 combo but that's with the throttles being bound to the FSX settings only. The Airbus works out of the box with that setup and I would therefore recommend to at least exclude the plane from your current FSUIPC calibration. You can do this when you tick the aircraft specific settings in FSUIPC and then reset the throttle calibration so that the throttle axis isn't affected by FSUIPC for just that plane. This leaves it intact for all other planes and liveries. Well, if you still like to use FSUIPC calibrated Airbus throttles, make sure to tick the 'no reverse' option. This might explain the negative values you are seeing. FSUIPC currently assumes some reverse range. If you wanted to use that reverse range, you have to define a spot where 'zero' (throttle) would be. Below this point, negative values come alive (causing reverse thrust), above it, positive wins (forward thrust). I'd say that there currently is such a point in your setup, which explains why that millimetre you mentioned makes such a difference. The FSUIPC manual helps on setting up such soft detents. In short. Just stick with pure FSX throttles on the Airbus in regard to the G940. No hassle, no setup. :smile:
September 28, 201312 yr Yes, agreed - @Jose88, open the Windows calibration dialogue and check the range of movement. I went through this recently with a set of rudder pedals that had a bad pot - you could actually see the range getting smaller with each repeated press. Also, in FSUIPC, check to see if you've selected a reverse range for the throttle - if so, then depending on how you've set it up, it might account for the very small negative range. Resetting the axis might help cure the problem. I used a G940 for a year and really enjoyed it, but I found it was really temperamental - it would sometimes get eccentric and finally the whole unit died on me after about a year's service. You might be able to find more help for it on the Avsim hardware controllers forum - and, again, Pete Dowson is really great about providing FSUIPC support on his dedicated forum over at Simflight. Feel free to PM me if you want to keep working through it. Happy to continue reading and posting here but if it's not an Airbus problem, we might want to move to another table, so to speak... Just some food for thought, José. I'm too using a G940 combo but that's with the throttles being bound to the FSX settings only. The Airbus works out of the box with that setup and I would therefore recommend to at least exclude the plane from your current FSUIPC calibration. You can do this when you tick the aircraft specific settings in FSUIPC and then reset the throttle calibration so that the throttle axis isn't affected by FSUIPC for just that plane. This leaves it intact for all other planes and liveries. Well, if you still like to use FSUIPC calibrated Airbus throttles, make sure to tick the 'no reverse' option. This might explain the negative values you are seeing. FSUIPC currently assumes some reverse range. If you wanted to use that reverse range, you have to define a spot where 'zero' (throttle) would be. Below this point, negative values come alive (causing reverse thrust), above it, positive wins (forward thrust). I'd say that there currently is such a point in your setup, which explains why that millimetre you mentioned makes such a difference. The FSUIPC manual helps on setting up such soft detents. In short. Just stick with pure FSX throttles on the Airbus in regard to the G940. No hassle, no setup. :smile: Ok was a problem in windows calibration. Now solved. All working perfect now! Throttle axis assigned via FSX for the AXE, and Profile Specific selected. One last question! What i need to make these change to all AXE variants? I don't see the same lines in my FSUIPC.ini that ones in the tutorial. These are my lines... [Profile.AXE] 1=Airbus A320 Iberia E-CILQ [Axes.AXE] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=1X,256,D,7,0,0,0 3=1Y,256,D,8,0,0,0 4=1R,256,D,3,0,0,0 5=2X,1,D,4,0,0,0 [JoystickCalibration.AXE] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=-16384,-512,512,16383 Elevator=-16302,-512,512,16383 Rudder=-16384,-512,512,16383 LeftBrake=-16384,16383 RightBrake=-16384,16383 Enviado desde mi iPhone 5 con Tapatalk Pro José Fco. Ibáñez /// i7 6700k (Delid) @ 4,6 Ghz /// Asrock Z170 OC Formula /// 16GB RAM G.Skill Ripjaws V 3200 /// GTX 1070 Founders Edition 8GB /// LG 27UD58 4K 27' // OCZ Vertex 4 SSD (X-Plane 10) & SAMSUNG 850 EVO SSD (P3D V3) /// Windows 10 Pro x64
September 28, 201312 yr José, mind you that we are turning the Aerosoft Airbus thread into a 'how to deal with throttles and FSUIPC' one. To give a short advise, unless you don't rely on using reversers with your hardware throttles, leave it to FSX to handle them. It saves you a lot of configuration and the addon devs some headaches. If one addon would really require FSUIPC's (calibration) help, you can always assign a plane specific profile. And if reversers are about the be operated, maybe use the full throttle range for forward thrust and the buttons to then apply steps of reverse thrust. This all works with the FSX assignments or the Logitech profiler (which itself uses default key commands) and therefore with every plane in FSX.
September 28, 201312 yr José, mind you that we are turning the Aerosoft Airbus thread into a 'how to deal with throttles and FSUIPC' one. To give a short advise, unless you don't rely on using reversers with your hardware throttles, leave it to FSX to handle them. It saves you a lot of configuration and the addon devs some headaches. If one addon would really require FSUIPC's (calibration) help, you can always assign a plane specific profile. And if reversers are about the be operated, maybe use the full throttle range for forward thrust and the buttons to then apply steps of reverse thrust. This all works with the FSX assignments or the Logitech profiler (which itself uses default key commands) and therefore with every plane in FSX. Ok sorry! Thanks for your opinion but I want to use FSUIPC instead of FSX. I use the reverses with my throttle levers. Enviado desde mi iPhone 5 con Tapatalk Pro José Fco. Ibáñez /// i7 6700k (Delid) @ 4,6 Ghz /// Asrock Z170 OC Formula /// 16GB RAM G.Skill Ripjaws V 3200 /// GTX 1070 Founders Edition 8GB /// LG 27UD58 4K 27' // OCZ Vertex 4 SSD (X-Plane 10) & SAMSUNG 850 EVO SSD (P3D V3) /// Windows 10 Pro x64
September 28, 201312 yr I see deal of the day at PCAviator is AEX, worth it? 30% $29.97Airbus X Extended Edition normally $42.75Aerosoft GmBH Expires 5 Oct 2013
September 28, 201312 yr I see deal of the day at PCAviator is AEX, worth it? 30% $29.97Airbus X Extended Edition normally $42.75Aerosoft GmBH Expires 5 Oct 2013 I guess one has to ask what they're after in an aircraft. This is my latest add-on (other than DX10 Fixer - which is a utility really, not an add-on) and with this purchase, I probably won't be making another for a while. You get a heck of a lot for your money here. A pretty sophisticated model, several aircraft variants, tons of liveries/liver manager, custom AXE FS2Crew, great graphics, great sounds, a cool tablet hosting feature that lets you run the FMC in a browser window on your tablet. This is my first modern 'sophisticated' tuberliner purchase and I'm going to be spending a long time learning from this one. The only thing that might disappoint initially is the apparent starkness of the VC. But when you look at it in detail, you realize it is well rendered and it's in fact very representative of the real thing. My 2 cents... [email protected] - ROG Strix Z790-E - 2X16Gb G.Skill Trident DDR5 6400 CL32 - MSI RTX 4090 Suprim X - WD SN850X 2 TB M.2 - XPG S70 Blade 2 TB M.2 - MSI A1000G PCIE5 1000 W 80+ Gold PSU - Liam Li 011 Dynamic Razer case - 58" Panasonic TC-58AX800U 4K - Pico 4 VR HMD - WinWing HOTAS Orion2 MAX - ProFlight Pedals - TrackIR 5 - W11 Pro (Passmark:12574, CPU:63110-Single:4785, GPU:50688)
September 28, 201312 yr But you can take your time to decide: Converted to Euros, I can have the PCAviator deal all year long at flightsimstore ... What happened to AVSIM
September 28, 201312 yr I see deal of the day at PCAviator is AEX, worth it? 30% $29.97Airbus X Extended Edition normally $42.75Aerosoft GmBH Expires 5 Oct 2013 Yes, it's worth it. It's not the NGX as far as funtionality but it's close enough to suspend disbelief. Enough that I fly both and don't feel like I'm cheating when I fly the Airbus X. It's got a lot of detail. Plus you get a sound pack, great model, excellent VC, an interative Co-pilot checklist, and a plane that simply works like it should (i.e. not full of bugs) with v1.15 now. It's probably the best tubeliner value on the market and at $30 it's a no brainer.
September 28, 201312 yr But you can take your time to decide: Converted to Euros, I can have the PCAviator deal all year long at flightsimstore ... True, for me it shows. Just bought it at PCA however but whatever. AER-177 Aerosoft - Airbus X Extended (Download) 0.00 USD$31.49
September 28, 201312 yr True, for me it shows. Just bought it at PCA however but whatever.AER-177 Aerosoft - Airbus X Extended (Download) 0.00 USD$31.49 Just a tip that first got me when I got the plane. Default loaded, it's full of fuel and at full cargo, which makes it a bear to get off the ground. Make sure you open the fuel planner and set the fuel and payload before taking it for a test flight. Forgot to do this on my first flight and thought I'd screwed something up. Should of dawned on me sooner lol.
September 28, 201312 yr True, for me it shows. Just bought it at PCA however but whatever.AER-177 Aerosoft - Airbus X Extended (Download) 0.00 USD$31.49 Get hotfix 18b from the Aerosoft Forums. And pls. note that the sound enhancement pack (compatible with v1.10 of the Airbus) requires a workaround to work with v1.15 of the Airbus. And you really, really should check out Dave's (Rumford) replacement voices for the Captain and the F/O ... What happened to AVSIM
Create an account or sign in to comment