Pastinya kalian sudah tidak asing lagi kan dengan Airbus A320.I just want the full range -16200 (levers at idle) to 16200 (max) to stay like that in the plane.FSX Delta Airlines BAe Concorde X FSLabs. As part of the modernisation program started in 2006, Airbus has been working on the A320E (Enhanced) of which the New Engine Option is the last step.Flight Sim Labs is currently focusing on several different flight simulation products. In an effort to keep improving their narrow-body workhorse, Airbus now has on offer the A320 NEO (New Engine Option) as opposed to the A320 CEO (Current Engine Option). Airbus A320 Specs show a modernised A320.
Fslabs Delta A320 Download The LiveriesHere you can download the liveries requested by our customers. Of course, we have something for our Airbus captains we have a whole bunch of different registrations for the FSLabs version of the A320X REQUESTED LIVERIES. Painted using the official ConcordeX paint kit.fslabs a320. You must own the ConcordeX from FSLabs. Textures only model not included. Repaint for the FSLabs ConcordeX in a fictional Delta 'Spirit of America' livery to satisfy supersonic needs with FSPassengersX airline.Fslabs Delta A320 Full Thrust IsI think I have understood the problem nowIt's the FSLabs A320. Full thrust is +16383, not 16200.First of all thanks for the insight. Note the range for the values, 0 to 16383.Your 16200 values are just the limits provided by your input levers. Normal "direct calibration' gets you 0 to 16383, because the values are written directly into the simulators engine values using Sim Vars as followsShared Cockpit (Pilot only, transmitted to Co-pilot if in a helicopter, not-transmitted otherwise).That is an extract from the P3D SimConnect SDK.I am just wondering, if I won't loose half of the resolution for that now. Consequently the levers in the plane are in the middle and not at idle.I understand I can now redefine the detend zones, set the Idle range from now between -1.00 and -0.97 to 0.00 to 0.03. Now in the FSLabs tool I see the range between 0 and 1.000. Between this range the detend zones are defined.Now if I use the FSUIPC calibration (I understood I have to to get the Sync functionality), I get a range of 0 to 16383, as you mentioned. Without FSUIPC calibration, apparently with the standard -16384 to 16383 range, I see the range between -1.000 (idle) and 1.000 (max). They also have a range display. It is a special option provided to try to cope with some different add-on practices (notably, in this case, the Wilco A320).Normally, the 4-Throttles, 4-mixtures and 4-Prop pitch calibrations result in an output with either a range which includesThe reverse zone, or, if the " no reverse zone " option is checked, a range from 0 (idle) to 16383 (max). This may help:UseAxisControlsForNRZ=No : This is a facility for the section(s) of the INI file, not. But here is an excerpt from the FSUIPC Advanced User guide (on one of the first few pages in fact). It is a pity you didn't show me your INI file as I requested, as I could advise more accurately. From 0 to 1.00 gives a delta of just 1.00.So I think in that case the Addon would need -16384 to 16383 for the idle to max range.I hope it is understandable with my "German" english.Possibly. ![]() Do you fly on keyboard only, or are you still using assignments in P3D? If you assign ANY joystick button or axis in FSUIPC you MUST disable controllers completely in P3D or you will get conflicts occurring. You have no yoke (aileron. It is rather different therefore.And. The default one is therefore being used for the 777, and that still has "UseAxiscontrolsForNRZ=No". Could you update, please? The current version is 5.122.It also shows me that you have a default calibration section and just the one Profile, for the A320. After all, they ALL have Full thrust at +16383 and the Idle in the same place (0 or -16384 depending on which FS control method you set FSUIPC to use), so the throttle syncing should be identical too.BTW the INI file tells me you are still on 5.103, a very early version of FSUIPC5. What do you expect it to do if you move only one?!And what are the values actually arriving IN and going OUT? Where are you reading the 12/23 etc, only in the INI? Are you reloading the INI file all the time?To view the IN values all the time, in real time, go to FSUIPC Logging tab, enable Axis logging, and Console Log, then run P3d in Windowed mode so you can see both it and the Log output both at the same time.Really, without knowing how your throttle inputs are behaving I can't comment, apart from my comment that it is really nonsense to move only one throttle and trying to sync multiple positions on Thr2 with just one postion on Thr1.I have enabled Axis logging, and Console window, but I do not see any values appearing in the console window when I move the throttles. "Sync" is trying to match the output values for both of the two Throttles. I have both levers in Idle position and sync reads 12/23.Just for testing, then I move only Throttle 2 up to the medium position and Sync still reads 12/23.Well, what is the point of moving only one throttle? You are effectively telling FSUIPC to equate your meiddle Thr2 position to the idl Throttle1 position. You can still calibrate in FSUIPC even without assignment.It really puzzles me. You need to do that, or not use FSUIPC for assignment. Surah mulk full textThe other way it to calibrate and sync first with that option set No, then change it afterwards and "reload" the calibrations.The fix internally, which I will implement, is basically that - ignore the "Yes" setting whilst recording sync points. It is using the -16384 to +16383 range for the throttle to be sync'd, but the 0-16383 range for the master throttle.This is actually a really good catch, so thank you! It's an original bug, dating right back to when the sync option was implemented! Amazing that it has never been reported before!And you found a good work-around for your case - copy over the sync positions from a "UseAxisControlsForNRZ=No" calibration. That implies the "UseAxisControlsForNRZ" option is only adversely affecting the vlues input to the syncing operation.I've managed to do some tests here, now, and, indeed, it is the " UseAxisControlsForNRZ" option which is messing up the sync point making facility. You'd need to ZIP it up and either attach it or send it to me by Email.However, I'm unlikely to be able to do much more for you now until Thursday, so if you can manage okay without the sync line for now, maybe we can continue then?Interesting. I really at this stage only wanted to see the value of each axis being sent to FS as you moved the two levers together from idle to max using the Sync line as it is at present.Then maybe a separate log with the same but with the Sync line removed or "commented out" (precede it with a ) so i can see the good or bad effects of the sync that you say you get.There is a debugging option i can get you to enable which logs a lot more stuff - including raw input values - even whilst in Calibration, but that log will be hige.
0 Comments
Leave a Reply. |
AuthorClarissa ArchivesCategories |