Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by Morten

  1. Well, my friend Fabio, now when finally you MADE IT and everything now works so great, we don't want silly P3D amauteur "v5 update" to spoil everything, and leave you back to point zero after all your many hard steps you've been through already!!!
  2. Problem seems now to be solved! Turned out to be caused by USB overload and/or an involved USB hub
  3. Yep. After a rather long developing period, FCR has been working great for a long time, for v4.3, 4.4 and 4.5! That is, however, if one stick to the rules in every detail: 1. With sim set to same FPS as FCR, as you already noticed. (I'm also flying PMDG) 2. For replay, let the same airplane as used in recording, load FULLY up in P3D's default scenery and time. 3. Then load FCR and unpause the session - then wait again till the airplane is FULLY loaded. 4. Then finally hit the play button on the FCR, and you're running! In addition to this, my experience is that if you sta
  4. Hi Dave Stay away from P3Dv5!!! and stick to version 4.5 the next couple of month! A scandal is going on these days. Version 5 is not at all ready - LM customers are hijacked as involuntary beta testers! Flight sim developers has already made a common statement towards LM with protest! LM hired an inexperienced kid to manage LM programming! Fabio's Replay app is working perfectly okay with LM version 4.5!
  5. Reconfigured both Throttles and Yoke to "direct FS assignment" and disabled power eco bull savings on USB ... All problems seems so far solved by those actions /Morten
  6. I will check out your other suggestions regarding to USB problems and see if this helps. Will also check this
  7. Pete, it is related to the thread that you closed the other day: From this thread:
  8. Okay, then...! In that respect I can certainly recognize the "funny" part of the yoke suddenly going completely bananas just before landing, about one out of 10 times (as mentioned to you before), but as irritating as it is, I can actually deal with that by just setting the sim on pause and replugging the USB connection and all returns to normal again...almost rutine! :) However dealing with a throttle quadrant that I have to re-calibrate in FSUIPC because the calibration has been lost every time I startup the PC and fly the PMDG in a new session, is pretty damn hard to deal with!
  9. Hi there I recently in another post learned that calibration of joysticks handling PMDG aircraft tend to make unpredictable troubles: "If you want to assign in FSUIPC, for PMDG aircraft Send to FS as Normal Axis AND select the "Axis_" controls. And do not calibrate in FSUIPC no matter where you assign" In my case, most of my avionics are controlled by commercial "joysticks", consisting of yoke, spoilers, mixture, pedals, etc, which have calibration tool software along with the equipment - However my 4 throttle quadrant consists entirely of homebuilt equipment! Would anyone pe
  10. Well sorry for my part also, but what you don't seem to realize is when your customers finally has done all assigning and calibration according to your comprehensive and relatively complex manual, they will usually only return to you for help if something goes wrong - that could be months or even years after. Because of that it is obviously essential that you stick to the exact same terms as used in in your own FSUIPC manual and program. No vague and "agreed terms" please, which would have the tendency to confuse everyone else than folks in your own staff. Put on top of that language barrier
  11. Hi Pete May I ask you to please answer me precisely, specifically and directly according to my questions. Which of the following environments would you recommend me to calibrate my PMDG: 1. Send to FS as normal axis inside the FSUIPC environment? OR 2. Calibrate my axis entirely inside the P3Dv4 settings environment? Morten
  12. Hi Pete 1. In my specific situation I'm using PMDG 777 most often. However occasionally I use these other aircraft for VFR: 2. Standard P3Dv4 Mooney Bravo aircraft 3. Third party DC3 by Daniel Fuernkaess, Manfred Jahn, Alexander M. Metzger, Hans-Joerg Naegele, Mike Cyul, Warwick Carter, Jan Visser So in this particular situation of mine what would you advise me to do regarding calibration methods and profile systems for each aircraft? Regards, Morten PS. Actually my very least occasional problems is NOT with my rudder/brake pedals (occasionally the pedals are
  13. Thanks indeed Pete for taking your time and getting back to me with a quick response... I'll look into your answer in depth and get back to you if any further questions. Regards, Morten
  14. Hi Thomas If this is really the case in relation to PMDG, this is very cruisel for me and my settings! However you were a bit fast in your answer, so please confirm if I got you right: Types of axis assignments as it shows up in your program: 1. Send direct to FSUIPC Calibration 2. Send to FS as normal axis 3. Send to FSUIPC Offset So what you are telling us is that we have to stick to No.2 "Send to FS as normal axis" in the case of PMDG. CORRECT? As it is my separate yoke, pedals and 4 quadrant throttles are all currently assigned to No.1 "Send direct to FSUI
  15. Hi there Thomas I much appreciate your interest for this subject. However I'm sorry to tell you that you unfortunately completely missed out the very obvious and straightforward point to the subject, which is simply to add a version number to the zip file. That's all! Cheers my friend
  16. Hello Pete Really now, that is not a reasonable argument: (Because) "That it has always been the case". Old men as we are, better be rational and keep evaluating according to development in our present time. In other words, plane and simple, naming a Zip file according to the relevant version number is what EVERY other developer does in these days, away from you! About detail properties for the "Install FSUIP5.exe": It says, file version which obviously gives no clue to the present FSUICP version 5.154 in this relevant case!
  17. Hi There On your site you kindly inform us about this: If you download a version which is not the same as displayed on this page, *please* empty your browser's cache or make sure you have specified the right download folder, thank you. Also try pressing Ctrl-F5 which should force a direct reload of the page in case your ISP is caching any links on this page. However unfortunately your download zips only show: "FSUIPC5.zip" without any version number whatsoever. If one after the extraction of the zip file then check the actual "Install FSUIP5.exe" one will only get the version
  18. Come on Pete, what do you take me for! Of course I know all about that. But at the time parking brakes had already been released by me long time before this blocking occured. However as I wrote above, this issue has now been completely solved with help from John. Thanks Pete for that reminder!
  19. Yes! The "Direct to FSUIPC" choice solved the blocked foot brakes after landing! Thanks John!!! (Pedals regarding to steering is however still chosen to be "Direct to FS", as it was the only way to solve my PMDG 777 steering problems - strange...but whatever it takes!) Cheers, Morten
  20. Oh dear...not quite, actually. By disabling P3Dv4.4s own joystick controllers and sending everything through FSUIPC - including the brake on my pedals: "to FS as normal axis" I get an allround perfect and steering setup - EXCEPT for the fact that brakes now seems to block 100% whenever I start taxing and after landing. When taxing I have to hit the food brake in order to release brakes which I haven't touched in the first place at all! Upon landing, it's not enough to hit the food brake twice (as in the good old FSX days). The only way I can release brakes here is when turning the Autobrake
  21. Fully agree - hate those beeps, not knowing what the heck is going on...
  22. Ahhh okay.... I'm afraid that you misunderstood me using the term "sensitive" - I'm not literally referring to the joysticks as the being sensitive. They are working perfect now in EVERY sense! What I was referring to was what was my experience with the newest version of P3Dv4.4 being ultra sensitive/intolerant to mixes between buttons assigned directly under the options of P3Dv4.4 and axis assigned under FSUIPC - with the result of joysticks going bananas! Although not a purely correct mix - anyway at least tolerated in P3D versions up to v 4.4. All according to what I wrote earlier:
  23. What?? "all the fuss" .......? I was struggling my arms off in order to get things right here - I finally ended up with succes, as you well know partly through your advice to disable P3D controls, and partly through my own experiment of letting pedals axes go through "Send to FS as normal axis". So no more "fuss", just happiness. But you asked me about some analytic questions, which I answered. Nothing more to it. 😃 Yes indeed, I'm off flying! Cheers, Morten
  24. Throttles: "direct to FSUIPC calibration" Spoilers: "direct to FSUIPC calibration" PropPitch: "direct to FSUIPC calibration" Mixture: "direct to FSUIPC calibration" Yoke: all axes: "direct to FSUIPC calibration" Hat switch on yoke: "Send to FS as normal axis" (NEW assignment) Pedals, rudder: "Send to FS as normal axis" (fairly NEW assignment. Solved front wheel steering problems ) Pedals, brakes: "Send to FS as normal axis" (fairly NEW assignment) P3D "Use Controllers": Disabled (fairly NEW assignment. Solved throttles unable to be calibrated correctly and yoke going ban
  • 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.