Jump to content
The simFlight Network Forums

Hoang

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by Hoang

  1. 1 hour ago, Pete Dowson said:

    I didn't need to "reconsider" as I hadn't decided way back at the beginning of the year.

    There will be an FSUIPC5 for P3D4, but first release won't coincide with the rather rushed (in my opinion) release of P3D4 on Tuesday. And FSUIPC5 will be a new product, not an upgrade. It's been too much work to have it as just an upgrade.

    The user weather stuff is stripped out, and some other facilities do not yet work (mouse macros, menu diversion, frictions just to name three). They are dependent on further P3D development.

    Pete

     

    You are one of the most wanted person in the community right now and this statement will be wide-spread very quickly.

    Thank you so much for the works you have contributed and moving forward.
    Hoang Le

  2. 9 hours ago, Pete Dowson said:

    On my system, with no complex aircraft but a large amount of AI Traffic and very busy airports like Heathrow, FSX-SE is a clearly better performer. But probably not the original FSX-ACC -- I found FSX-SE far better than FSX and switched pretty quickly.

    However, P3D is better looking and CAN be smoother if set correctly. I've recently made some substantial changes to my system and will be doing the comparisons again. with the 200 degree FOV screen I now have (by NatVis), the superiority of the P3D visuals is very desirable.

    Pete

     

    That is what so mystery about the simulator, it varies with different system. At Uk2000 Heathrow with FSX:SE, limit 10 AI, using PMDG 777 I can get barely 20FPS in the VC, most of the time ~15 but stutter here and there. With P3D + higher graphic settings, 30AI, I still can get at least 25FPS if I view straight to the dense area in the airport. If not it will always stay around 30FPS and more. No stutter whatsoever, I was amazed. Maybe I did not tweak/config my FSX:SE good enough.

    Just to update, I have been flying since yesterday without any issue so far besides ntdll.dll crash which I am troubleshooting. Found out there are many unnecessary and duplicate C++ in my window.

    Safe flight,
    Hoang Le

  3. 3 hours ago, Thomas Richter said:

    Hi,

    you need to set the SimConnectStallTime= value to your needs of course because it will stay as it was saved last, max 20.

    Thomas

    Thank you, I have changed it back to 1 and it seems to stay there now. Still don't know why it goes up to 20 but could be I was using the older version of FSUIPC. So far, it works!

    2 hours ago, Pete Dowson said:

    I understand the reasons for an autosave. I was thevfirst to implement such a facility a long long time ago. But I don't think it is a good idea for some of these aircraft which do freeze simulation in order to take copies of all the information to create the files. The larger number of files also is a factor, especially if you don't use fast SSDs or have a crowded disk.

    I hate having to do that too. I maintain both FSX-SE and P3D systems with many addons, and I dread ever having to do a complete re-install. Worse still is having to reinstall all of Windows. I bought a new PC last November and it took me well over a week just to get it fully set up the way I liked things with my utilities and support and diagnostic programs, even before starting on FSX-SE and P3D. This is why I put off upgrading machines for years after they are well superseded by better and faster tech -- and unfortunately I demand more and more performance!

    Pete

     

     

    Hi Pete,

    I used the autosave function in your software for a very long time until I change to using Pro-ATC/X. Very handy.

    Earlier today after digging, I install the newest FSUIPC version and change SimConnectStallTime from 20 to 1 as suggested. I found out that this problem also happen to my FSX setup. So it must be something outside the simulator. What I did after was very traditional, restart my window. To my surprise, the problem suddenly disappear. No more Simconnect errors, no more long pause during saving flight. I can load PMDG 777 normally now.

    Been going back and forth P3D and FSX today I clearly see how poor the performance FSX is compare to P3D in my system.

    Thank you so much for all your help, Pete and Thomas, I was so desperate that I almost getting ready to reinstall my Window.

    Just one more challenge, reinstall or FSDT products to see if they conflict with PMDG again or not.


    Cheers,
    Hoang Le

     

  4. On 3/5/2017 at 2:16 PM, ironcondor said:

    Interesting. I did purchase the PMDG 737 for the first time for P3D. I has it for my old FSX existing years ago. That is the only  thing that had changed. I am now wondering if any of the changes requested by the PMDG 737 installer changed anything for the PMDG 777. I am doing another flight from KJFK-LSZH right now. I will report back any findings. Thank you for your prompt responses!

     

    Abe

    Hello, I am having quite a similar issue and wondering if you have found out the issue?

    Thank you,
    Hoang Le

  5. 1 minute ago, Pete Dowson said:

    No, it cannot. If there's no such line FSUIPC sets 1.  20 is the maximum I think. If you didn't change it then somethnig else you have run did.

    With a stall time of 20 then FSUIPC won't reconnect to SimConnect until it has received no updates for 20 seconds. That's a mighty long time!

    Okay. That sounds better. So it must be something else, maybe something ProATC/X is doing? I've never used its AutoSave. There's no point in my case because I fly a cockpit with loads of other drivers, and you just can't start a flight in the air. I almost always start from cold and dark. The nearest to flight I can start with is on the runway ready for takoff, but it's so complicated to get that set that it simply isn't worth it. Anyway, a lot of the fun is in the pre from cold and dark, taxiing and so on. Especially at the sort of busy airports I like.

    I use ProSim for my cockpit and, like you ProATC for ATC. No complex aircraft cockpit with its own systems though, of course.

    Sorry, but I really can't help much further. The SimConnect restarting WILL be adding to the time you are seeing, but it means it has already been 20 seconds with the sim frozen. I can't really do much about that -- my software isn't involved.

    Pete

     

    Hi,

    I use the auto save in case my system crash or suddenly get VAS leak that I can not continue the flight. Most of the time I don't need it. But now saving manually under P3D menu, my simulator also freeze for a very long time, which is not related to Pro-ATC/X. Pro-ATC, along with PMDG 777, is just being affected by whatever causing this problem.

    I will dig deeper, or else I have to do a full reinstall of P3D, which took me almost a week to install things I needed.

    Thank you so much for your help, I really appreciated it, as I said I believed it does not relates to your software but FSUIPC.log is one of the only source that tell me what is happening to my P3D.
    Have a nice day,
    Hoang Le

  6. Actually, I have just installed PMDG 777 yesterday and it would not load into the simulator. I open a ticket over at PMDG and they say it relates to Simconnect problem (which P3D keep running "777X_debug_log.txt" in "Prepar3D v3\PMDG\PMDG 777X" and P3D can not start. So it could be my Simconnect somehow broke and fail before I purchase and install PMDG.

    My original topic over at PMDG https://www.avsim.com/forums/topic/508261-p3d-pmdg-777-cannot-load/

     

  7. 2 minutes ago, Pete Dowson said:

    FSUIPC is timing out the connection to SimConnect because the AutoSave is taking so long. When using sophisticated aircraft like PMDG and FSX, whenever a flight is saved they effectively freeze the sim whilst they collect and save the state of every system and gauge. Even if SimConnect didn't time-out, there would certainly be a very noticeable pause. Most folks advice against using an AutoSave of any sort when using these aircraft.

    the fact that SimConnect connections timeout will certainly make the pauses longer, because FSUIPC then has to completely reinitialise. You can make FSUIPC more tolerant by increasing the SimConnectStallTime parameter in the FSUIPC4.INI file. The default of 1 second is normally much more thasn adequate because it should be receiving updates every single FS frame!

    Now you say about autosave that "it has been working flawlessly". So what have you changed? Have you only just started using these aircraft?

    The files are what the A320 and PrtoATC/X are using/saving/loading, whatever. FSUIPC isn't involved. Maybe your disk is becoming full or needs a thorough defragmentation. That would certainly slow file read/writes down.

    Pete

     

    Hi,

    I just look over my FSUIPC.ini and SimConnectStallTime is set to 20, which default is 1, I never touch or edit it. Is there a reason why it automatically goes up to 20?

    I have been using FSlabs A320x for a while and if I manually save the flight in P3D menu or Pro-ATC/X menu, there will be slight pause. But Pro-ATC/X automatically saving pause is barely recognizable. Now it hangs up for 1 minute when saving manually or automatically which is very unusual.

    For the past few days there have been enormous changes to my simulator setup. I uninstall almost every addon in my FSX:SE (which now I am hoping it does not relate to this problem), and adding many airports into P3D + PMDG 777. However all of these are done after the problem occur in my P3D.

    IIRC, 2 days ago I had a flight from Flightbeam San Francisco KSFO to PACSIM Salt Lake in FSLabs A320x (using Pro-ATC/X with automatic saving function). The flight went smoothly until reaching TOD where I had to pause and go out. When I get back, I unpause and decend to the destination airport where it started to hang up very often. I did not know why back then but now I can certainly confirm it is the pause from Pro-ATC/X automatic saving. And it has been happening until now.

    I am using a  SSD 480GB for my FSX:SE and P3D and it has around 100GB free.

    Thank you for your help so far,
    Hoang Le

  8. Hi,

    I am having a big issue with my simulator, everytime I save a flight in P3D menu or Pro-ATC/X, it freezes around 30 seconds to 1 minute which is very unusual. I found in FSUIPC.log there are 2 lines that I think can do something with it:

    "**** No SimConnect events or states being received! Re-connecting now ... ****"

    " **** SimConnect Data Stalled! Re-connecting now ... ****"

     

    My Pro-ATC/X is set to autosave every 5 minutes and it has been working flawlessly without issue, now every 5 minutes I get hang up for 1 minute.

    I open ProcessMonitor and see P3D keeps loading these 2 when I save the flight, usually it does it very fast, now it keeps continuously for around a minute

    "D:\Game\Lockheed Martin\Prepar3D v3\FSLabs\A320\PanelState\LastProATCX.fxml.sav"

    "C:\Users\******\Documents\Prepar3D v3 Files\KLAXKSLC_20170410-0901_RTE-EnRoute_142.fxml"

    It happens to PMDG aircrafts too so I believed it does not relate to FSLabs.


    I have reinstall the Simconnect in P3D/redist and also the P3D SDK but does not fix the problem. I don't know if this relates anything to FSUIPC but FSUIPC might point out something wrong in my simulator.
    Thank you,
    Hoang Le

    EDIT: Is this the correct version of Simconnect?  "Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.22.19868 (SimConnect: 3.4.0.0)"

    Found out in FSUIPC.ini "SimConnectStallTime=20" which default should be =1? I never edit this line.

  9. 32 minutes ago, AKC130FltEng said:

    Yes you can do it that way.  Make sure you follow the steps precisely and make sure you have the latest one. 1.3 or something.  

    I honestly stopped using my Saitek throttle quads earlier today.  And I stopped using the reverser buttons on them years ago as I found them just to sloppy and always triggering just from taxiing.  So what I did was setup one button on my joystick to enable that plugin and then ran the throttles up.  If you wish todo it that way it is not described in the readme but its easy todo.  Select the button you want to use in the Button assignment table.  Select for FS Action.  Scroll down to LuaToggle ThrottleManager.  Make sure you select the Toggle one.  There are like 9-10 options.  Set it to parameter 1 click okay and exit FlightSim.  Open up FSUIPC.ini and find the entry that looks like this.
    54=PA,8,CL3:T,1     -{LuaToggle ThrottleManager}-                            the ,1 at the end is the parameter.

    Copy paste that line 2 more times and change the parameter to 2 and then 3.  The parameter assigns the engine.  Should look something like this when your done.

    54=PA,8,CL3:T,1     -{LuaToggle ThrottleManager}-
    55=PA,8,CL3:T,2     -{LuaToggle ThrottleManager}-
    56=PA,8,CL3:T,3     -{LuaToggle ThrottleManager}-

     

    Open fs.  Press that button you should hear a ding.  If you don't something isn't setup right.  All done.  I have it setup on my 777, ifly 747, pmdg 747, md-11 and works fine on all of them and more convienent than a seperate axis for the reverser.  Now you should be able to setup a spoiler axis and a flap axis on your quadrants. since you freed up 3 axis assignments.

    Hi,
    Thank you so much for your help. I think I will use this setting and use the other axis for spoiler and flaps(if it is worth it since it is free-moving levers).

    Cheers
    Hoang Le

  10. Just now, AKC130FltEng said:

    Give it a shot like that see what happens.  I still suggest trying the Throttle Manager Lua though.  It will allow you to just turn your throttle axis into the reverser axis by a press of a button.

    Hello,
    I had a look over that topic and if I understand correctly, move the throttle levers down to press the button under it, then move it up for reverser, so actually we still use the axis for reverser so it is the same as I use the 2nd throttle quadrant for reverse. I will try it later to see how it works.
    Thank you for your help so far.
    Hoang Le

  11. 33 minutes ago, AKC130FltEng said:

    Change the calibration also.  You want a deadzone from the max and minimum setting to get away from those jitters also.  The manual describes how to calibrate everything.  The most I can tell you is move the throttle axis just a bit out of the detent Set the minimum.  Advance it all the way then pull the throttle back just a bit and set the maximum.  Now you will reach the minimum and maximum throttle setting before you get to the stops and should take care of the rest.

     

    the MD-11 does have a something inbuilt to prevent you from going full reverse to soon after touchdown.  So that might be something also yes.  The nose wheel on the MD-11 is supposed to be on the ground before applying reverse thrust.

    Hi,
    This is what I did earlier today (settings in Joystick Calibration).

    "Reverser1=-15000,15000/8
    Reverser2=-15000,15000/8
    Reverser3=-15000,15000/8"

    "Throttle1=-13000,-512,512,15000/40
    Throttle2=-13000,-512,512,15000/40
    Throttle3=-13000,-512,512,15000/40"

    Default all of them were -16380 and 16380.

     

  12. 29 minutes ago, AKC130FltEng said:

    After you did my suggestion whats your calibration and delta look like?  You can look into the Throttle Manager plugin.  I tried it out a few days ago and its awesome minus its incompatibility with the new PMDG 747.

    Hi,

    I just went into FSUIPC.ini and change Delta for 3 reverser axis to 420. Everything else I remain the same. Did I do it right?

    I try to use key/button function for the MD-11 reverser and found out if I press once, it is going to go into reverser idle (I think so because it always stay at that spot), press again then it moves further without stutter. This could be why it stutter when trying to use the axis because it got stuck at the idle spot.

    My workaround for now is move the reverser axis little bit until I here a click sound (which probably reverser at idle) then move it further.

  13. 2 hours ago, AKC130FltEng said:

     

    I'm not going to claim to be an expert.  But I have the Saitek setup and its constantly jittery like that.  Increase the Delta size on the Axis Assignment page.  I used 420 seems to mellow out the jittery inputs ALOT.  Also make sure you have a decent dead zone for the rerverser.  No need for it to be hyper sensitive to go into reverse so even a knob width of a dead zone will make sure Rev is triggered while your taxing around.
    Todo the delta its easier to do it in the ini file to get an exact number or Scan the axis you want then press the Delta button move the axis very slightly then press delta again.  Keep doing that until you get the result you want.  

    Hello,
    Thank you for your help. I have tried your method but the issue is still there. I found out that if the reverser is still functioning(even tiny bit of it), the throttle going to stutter. When there are no reverser deployed, the throttle works normally. So I will just let it to fully in up position (clicky sounds) until start using the throttle. One problem solved.
    I try to assign button press for reverser and it still stutter. Because PMDG does not support FSX:SE, I am unsure this is problem with my settings, or because I am using FSX:SE.
    Thank you,
    Hoang Le

  14. Hi,
    I am using PMDG MD-11 with FSX:SE and FSUIPC registered version(4.962) for throttle and reverser. With other aircrafts both settings in FSUIPC work fine(PMDG 737,747,777, FSLabs A320X) but this particular plane keep spiking as shown in the video.

    I use 2 Saitek Throttle Quadrant, one for 3 reverser and other one for 3 throttles. Tried to search google and forum but couldn't find the answer.

    DBxRIij.jpg

     

    vilaVX1.jpg

     

    cuf1Y5h.jpg

     

    AUtWAwd.jpg

    There is a topic from avsim that I believed he had the same issue but he uses the button under the levels for reverse: http://www.avsim.com/forums/topic/363151-reverser-fsuipc-little-problem

    Any idea why this could happen?

    Thank you,
    Hoang Le

  15. 2 minutes ago, Pete Dowson said:

    The simulator yoke is a graphic trying to imitate the real aircraft, where most yokes turn at least, and sometimes beyond, 90 degrees. It is the Saitek which has a limited angle.

    Pete

     

    Hi,
    Thank you for your suggestions. I will dig deeper into it later today when I get home.

    Will try to turn the Saitek yoke more slowly to see if it is sensitive or it is because I am used to the real aircraft yoke that I might over control the Saitek one.
    Cheers.
    Hoang Le

  16. 6 minutes ago, Pete Dowson said:

    Well, I completely disagree with you there. The flight controls should always allow you the full range of deflection provided for in the engineering of the aircraft. Why else would they construct it that way otherwise?  And you never know when you might need it.

    If you simply want more central range, pushing the more extreme angles to a small outer portion of the controls, then use one of the slopes available in the FSUIPC calibration tab to achieve this.

    If you really want to (UNREALISTICALLY) limit the effect of your controls there are two ways of doing it:

    1. Edit the AIRCRAFT.CFG file of whatever aircraft you use to reduce the aileron effectiveness. 
    2. Edit the calibration values in FSUIPC4.INI to make the minimum and maximum figures recorded there a multiple of the ones now set (eg 2X to reduce effectiveness by 50%)

    Pete

     

    Hi, thanks for the fast reply.

    How do the Saitek yoke and simulator yoke work together?  Saitek one only 45*,in-game is 90*. So if I turn my Saitek yoke 10*, in-game it will turn 20*? Or it is the same until the last moments where it will go up more when I am close to reaching 45*?

    Because I find my yoke too sensitive and I don't know how to set it up correctly to make it as realistic as it can be. Or less sensitive.
    Cheers.
    Hoang Le

×
×
  • 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.