Jump to content
The simFlight Network Forums

Flusi2004

Members
  • Posts

    16
  • Joined

  • Last visited

Everything posted by Flusi2004

  1. As I wrote in my last post after a new installation of the normal 727 it works now without lua and offset with the binding Throttle.... ex1. And of course, if I tried the 727 super the lua file was in the fsuipc folder and the correct entry in the ini. And I found out, that throttle bindings in the super moves the reverse axis.. Any way, the normal 727 works and for the 727 Super I will wait for an update from FSS. For now it is ok for me. Thanks again. Klaus
  2. Here the log with list lvars FSUIPC7.log
  3. Hi John, you make a really great support but it is quite tiring for me because english is not my native language and I don't unterstood all your instructions. Yes, I have tested also the offset and the lua without succsess. But now the normal 727-200 works with the settings Throttle... ...ex1 . Because most of the time I fly twins, lever one of the Bravo is binding to two axes. I have tried the same FSUIPC settings for the 727 Super but that doesn't work. OK, FSS is only a early access and sure there will be updates in the future. Perhaps they will be a solution.To your interest in the attachment the last log and ini files. Thanks again, Klaus FSUIPC7.ini FSUIPC7.log
  4. FSS released 3 Boeing 727. 727F, 727-200 and 727-200 Super. The " Super" is an extension pack of the 727-200. Of course I have tried to use with the Super the same FSUIPC Profile like the normal 727-200. But doesn't work. I think, it is a problem with the FSS progamming because the ERJ 170 from FSS has the same issue. Klaus
  5. Hi John, I have tried many hours today. New installation of the 727 and FSUIPC, disable Win Defender, try Lua Script etc. Strange, the original 727-200 works now with the normal FSUIPC axis assignment but the 727-200 Super accepted only the assignment with MSFS axis. I'm giving up now, because all other planes works fine with FSUIPC. Any way, great support and thanks! Klaus
  6. Sorry for the late reply, I didn't want to check before friday. Yes,I can move the throttle with the mouse and also if I use the axis settings in MSFS. And yes, if I tried to move the throttle with FSUIPC I also have a noise but no movement. I have checked other foren, and found that serveral simmers have problems with the FSS AC. Some means, the reason is the copy protection if useing a third party add on. May be, because all other AC, and I own many, works very fine with FSUIPC. And this is the main thing for me. Klaus
  7. Sorry, although I have been using FSUIPC since FS98 I am not a profi, but I have done "my very best" ;). The B727 Super doesn't have a calibration option in the EFB, for this time I used the mouse to move the throttles in the VC, here the result. Klaus FSUIPC7.log
  8. Hi John, thanks for the quick reply. I have tried all axis settings : direct FSUIPC, MSFS throttle, MSFS throttle ex1 etc. but the same issue. Throttle lever in the VC doesn't move but I hear the upspooling engine for a millisecond and then the engine goes in idle again. I disable all MSFS axis with an emty profile, same issue. I create an emty FSUIPC ini, but same issue. Only if I assign the axis with MSFS settings all works fine. Sure, I can always change my profile in MSFS if I want to fly FSS AC, but I love FSUIPC, because FSUIPC change his profile automatically. The logfile is the last try with an emty FSUIPC ini. Thanks for help again. Klaus FSUIPC7.ini LOG.zip
  9. Hi, I have been using FSUIPC since the beginning, but I can't solve this problem. FSUIPC doesn't work with the throttle axis of the FSS planes in MSFS (Embraer 170, B 727 Super). All other AC works fine and also the MSFS axis assignment works, all throttle axis are recognised. But the throttle axis (no movement).of the FSS planes doesn't work with FSUIPC 7. I have tried serveral settings and calibrations, but no success. Thanks for help. Klaus Test 727 FSUIPC7.log FSUIPC7.JoyScan.csv
  10. It works! I didn´t understood, (sorry, I am a senior) that I have to delete the general calibrations settings. I thought there are deleted automaticlally if I choose a specific profile Thanks for your patience. Sonja
  11. I have forgotten to check the axis log, sorry for that. Here the log again, but only a part, because the whole logfile is 800kb. But I am afraid, that there is no solution. I can not calibrate the throttle axis, if I sent them direct to MSFS (throttle Axis set ex). All other Axis options sent with fsuipc to MSFS doesn´t work. I found serveral Threads in the forums with the same reports.Even PMDG recommends in a forum not to use PMDG with FSUIPC, because there are unknown issues with their products if FSUIPC is running. But that's a pity, many Addon needs FSUPC (P2ATC...). Anyway, if you have any ideas please let me know. Thanks Sonja FSUIPC71.log
  12. Hi John, thanks for reply. Somthing goes wrong. Now also the AFE from the PMDG doesn`t work correct if FSUIC is running. After stopping FSUIPC all works normal. And no issue with the Superconny 4 engines jetliner with FSUIPC or the PMDG 737 for example, only the PMDG DC6 has an issue with FSUIPC. Thanks for help again Sonja FSUIPC7.ini FSUIPC7.log
  13. Hi, I know, that there is a general issue between PMDG and FSUIPC. But is meanwhile a solution for the throttle issue? I send my throttles from the DC6 with "Throttle 1 - 4 Throttle Axis set Ex" to MSFS. But after moving the throttles into a forward position (taxi) they doesn´t go back to idle in the sim , the stayed at manifold 30. Also if I assign the throttles only with the MSFS Menue, same issue. I have to shut down the FSUIPC, when it is all fine, but restart FSUIPC same issue. So I am unable to land the DC6, because I can not set the throttle to Idle if FSUIPC is running. Thanks for help Sonja
×
×
  • 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.