Jump to content

mpo910

Members
 View Profile  See their activity

  • Content Count

    2,403

  • Donations

    $15.00 

  • Joined

  • Last visited

Posts posted by mpo910

  1. Posted

    5 hours ago, peloto said:

    Is it going to be compatible with VR since launch?, if not, null interest of me in it till then.

     

    And if it has VR build in, I hope OpenXRToolkit will be too, or all functions integrated (which I doubt). Because only since using OpenXRToolkit, my VR looks stunning sharp. Things like Foveated Rendering are not implemented in MSFS yet, and this is needed for all users using High End Headsets....wihtout Foveated Rendering, Performance will drop signifcantly.

      

    • Upvote 1

  2. Posted

    11 minutes ago, Nemo said:

    Experience tells me not to give too much on Mathijs Koks opinion ...

    Mathijs Koks Signature text is interesting:

    Have fun. Be respectful. Criticize Ideas, never people.

    I would never use the approach to  "Criticize Ideas". Every Idea is a free motivation from a "Customer or potential Customer" to share something. Why Criticzing on that?

    It is Off-Topic.......I know.

    It´s just something that I don´t like to read from a Manager.....   

  6. Posted

    3 minutes ago, RockOla said:

    I did 2 tests flights yesterday (ESSA-ENBR / KMCO-MKJS) with IAE engines. Did not encounter VNAV issue, but had one AP disconnection mid flight. Cannot blame the FNX though, might be my joystick and/or xbox pads. Never had any disconnection with B1 though, I'll do further tests tonight.

    Maybe check the dead zone settings if they are high enough? And, also with MSFS I had heavy weather upload changing altitude and wind dramatically causing my AP to disconnect as well.

    Just some thoughts, although this must not be applicable to your situation. 

     

  7. Posted

    8 minutes ago, caneman said:

    Need some help. What I'm thinking/doing wrong?

    Just ran a test.

    At KLAX with traffic, sitting at gate (A300)

    With automated version 4.0, on the ground TLOD is running at 200.  This gives me a pretty choppy experience.

    With manual version 3.7, I have TLOD set to AGL / 50.  Increases to 200 as I hit 1000 AGL.  Much smoother views as I pan and steadier FPS overall.

    Why would the automated version have a high (200) TLOD on the ground?  Isn't that the opposite of the desired effect?   

    (Running PC store version)

    The AutoLod is only increasing and maintaining TLOD if your set target fps is achieved.

    If this is the case, tlod could be high BUT if the sim is not well optimized then you still will suffer from stutters 

  9. Posted · Edited by mpo910

    6 minutes ago, Reset XPDR said:

    MSFS settings like you used to, and the app will take it from there

    I do understand this very good.

    This will lead to the case, that when you start a flight, all is fine because the app will choose your "in MSFS" TLOD to start with.

    The downside is, that when decending, you get very high TLOD (when your Target FPS is not set to high and your machine is capable of), then when hitting the ground, the app will "fix" the last TLOD value, which was present "at" the moment you hit the ground, this is a high value, in the most cases, to high for smooth taxiing. Yesterday I got, till landing TLOD values >200,  and after I touched down it reduced quick to 105. So 105 would be the right value to maintain my "target FPS, which was 45 set by me in the app). 

    With the newsest version this "105" will be around "200". That will cause stuttering.

    That´s why I asked about the "fix TLOD GRound Value" set by the user.

  10. Posted · Edited by mpo910

    30 minutes ago, abennett said:

    Yeah this is why I think it would be better if that app could always change the TLOD. I started the flight at 50 TLOD which is too low for my system but hey, I'd rather have it super smooth. It gradually increased to 400 on the way up with zero stutters and the sim looking great. I had set FPS target to 60. In descent and approach it just stayed at 400 the whole way as I was above 60 fps, but once I had landed, taxied over to the gate, etc., I was stuttering a fair bit, but because the TLOD can't change on the ground it was just stuck at 400, which was a bit too much for my system in the Fenix and a 3rd party airport to keep 60 fps at 400 TLOD.

    @Reset XPDR

    For AutoFPS

    It would be nice to have the possibility to set a ground TLOD value in the app (0=x, like  0=125). The value x can be set by the user and the "0" is fix.

    When loading into the flight that x value is chosen, when climbing the fps target is leading, when decending also, when touching down after  decending (=ground) the set ground value is set once by the app. Ground value works the same as in dynamic lod reset app. 

  11. Posted

    11 minutes ago, VFRHawk said:

    Sorry to divert slightly, but how does one remove any of these programs?  I recently updated my PC and would like to see how it performs without this.  I actually have the original version by Fragtality still installed, though may well update if I still find a need on the new system once the pace of development slows down a little..

    Is it as simple as deleting the folder?  It doesn't seem to appear in the list of programs in windows so I can't uninstall it that way.  As it launches automatically I assume it must have updated a file in MSFS?

    Just run the installer again and choose the remove or uninstall option in the app. Then all is gone

  12. Posted

    Just now, Reset XPDR said:

    I put it down to a DX12 issue, which I have seen well before this app existed. I have no idea why it would happen as LOD changes in the distance should have nothing to do with what's right in front of your nose. Even OLOD stays exactly the same so it's not that with this new app.

    Could it be the way "you" access the memory?

    Why I ask? Because when I turn Resizable BAR on (via NVInspector) this happens also every single time I use MSFS, If I deactivate ResizableBAR again, issue is in 90% of my usage gone. 

    So I assume, this has to do with memory.

  13. Posted

    2 minutes ago, roi1862 said:

    True. But its more on the rare side. With the software altering TLOD dynamic its worse and happens instantly 

    That´s indeed a interesting finding. I further am testing AutoFPS (and DynLod too) and just a view minutes ago, I saw those textures disappearing in DX12 with AutoFPS. I turned AutoFPS of, exited VR, zoomed out with the Drone Camera, so the textures reappear again, got in the cockpit view again then activated VR again and tested the in and outside view a view times to see if the issues stays "gone". All stayed fine! No issue with textures.

    But, then I started AutoFPS again and immidiately (within a splitsecond, means  <1second) )the textures disappeared again. I did this whole process 3 times in a row to rules AutoFPS out, but indeed, I could reproduce it every single time.

    Airports where this happend:

    EDDF and EIDW

    Planes used

    FenixA320 and SimHorizon 789

    I am aware of the DX12 Airport texture disappearing issue and Bing Maps textures bleeding trhough then. But in my case, since SU14 and also Beta Su15 this didn´t happen anymore so often, only in very very rare cases (with excessive low FPS for example, means <32FPS, but even then not always).

    Now I am aware, that probably autoFPS has an influence on this, I will test it with DynLOD_Reset again. I also thought, at my end, that DynLOD Reset has less influence compared to AutoFPS

    @Reset XPDR: Just to inform you. IF there is something you are keen or aware of, why this COULD happen (I don´t have any evidence, just an assumption) then please let us know. I know that the real cause of the texture issue is probably DX12 and caching issues within MSFS.

    Regards

    Marcus

    • Like 2

  15. Posted · Edited by mpo910

    2 minutes ago, Reset XPDR said:

    unless you go into MSFS settings and change it yourself.

    During my flight I did went into the MSFS Settings and changed my OLOD to 150, the AutoFPS was not showing the new set value. 

    I did not test if it was maybe still detecting it and handling it as well (so just not showing).

    Do I need to restart the app to take advantage of the new set value? I tested it in VR  mode active.

     

  16. Posted · Edited by mpo910

    3 hours ago, Reset XPDR said:

    If anyone would like to help me out by trialing my new MSFS2020_AutoFPS concept demo, which you can find here, and providing feedback, I would much appreciate it. A detailed description of the functionality developed so far is provided at this link.

     

     

    @Reset XPDR

    First of all: I would AGAIN like to thank you for this new Tool, AutoFPS!

    I have tested it extensively this morning and it works like a charm. My FPS was so stable and I could follow the "changes in TLOD" so smooth and so "self explained"

    I have tested this with the new MSFS BETA and in ocmbination with my 7900X3d RTX 4090 and with, as well without, VR (Varjo Aero) in a scenario, where I knew my FPS will hover "around" the target FPS, in my case 45, to keep VR smooth (1/2 of 90Hz HMD refreshrate)

    Here in EDDF Scenery I have photogrammity as well procedural Buildings/Objects and so I could really good see how this impacts the "drawing" lines (TLOD Distances)

    Its another MUST have addon and also my prefered one above the DynLod Reset Tool you have developped.

    I have ONE further wish:

    I would like to set my own FIX OLOD value. The tool fixes it on 125. Is that right? Regardless of my OLOD PC or VR OLOD settings, right?

    In my case, and maybe the VFR flyers too, I would prefer to change that value, as a fix value, to a distance (OLOD) what my maschine is capable to handle as OLOD objects (also the details on Streets that are drawn are OLOD) look better when flying over them at 5000 feet for instance with 150 or 175 instead of 125. 

    Are you planning and willing to change that? That would be awsome!

    THANKS a lot and now I will fly with your new Tool! AutoFPS! So great!

    Cheers, Marcus (from EDDF) 

    • Like 2

  17. Posted

    1 minute ago, GeoSkyman said:

    Hello any advise, SU15 Beta, smooth like silk, performance great, BUT cockpit camera pan, screen tearing. Any advise please?

    Also smooth. I pan every time due the use of VR headset (Varjo with ppd set to 37) no stutters, even with TLOD set to much greater then 200 (tested up to 300 and even 400). FPS goes down a bit, logical and very acceptable at my end, but stays smooth. Same is applicable for 2d screen, tested that as well. 

    Overall the whole sim is smooth as never before incl taxi und ground and large airports, even at klax with 50+ AI traffic around and LOD to 150 I get 37 fps in my headset (+5k pixels!). At 2d I get 60 fps in that scenario , and butter smooth. 

    • Like 3

  19. Posted · Edited by mpo910

    5 minutes ago, iFlySimX said:

    I wonder if DX 12 has improved...or if any changes were made to it. 

    Smooth as Butter at my End (7900X3D and 4090). Really more smooth even if I crank up the Settings. TLOD 300 and great stability, FPS and Smoothnes even on ground while taxiing. 

    NOTE: This is in VR with Varjo Aero and PPD set to 37 (which is really a lots of pixels)

    • Like 1

  22. Posted

    23 minutes ago, Reset XPDR said:

    Quick update on today's progress on 0.3.7 development.

    @Reset XPDR

    Your work, your communication and your product-outcome is just incredible remarkable! I would like to THANK YOU for all this. I enjoy using this tool and for me it is, combinded with the openXR-Toolkit, the ABSOLUTE NUMBER 1 MUST HAVE PRODUCT!

    😉

    I would like to wish you a great day!

    Regards

    Marcus

    • Like 8
    • Upvote 2
×
×
  • Create New...