Jump to content

glider1

Members
  • Content Count

    586
  • Donations

    $10.00 
  • Joined

  • Last visited

Community Reputation

60 Good

About glider1

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

1,784 profile views
  1. The whole issue is statistical and so difficult to prove. I'm in VR too. I go a different route. I internally lock to 45fps (1/2 90) and allow the sim to build frames in the background this way which keeps it smoother for me for the types of flying I do. With DFFTF there is a reduction in long frames I feel, but it is not a bullet proof solution.
  2. yeah I also had an issue with A2A windshield rain effects that were causing a device hung randomly in v5 not v4. Definitely have to wipe the shaders and let them rebuild every time there is a CTD of this kind. Old corrupted shaders will give a "device hung" too.
  3. true it depends on the flying. Internally limited is there for a reason. It pregenerates frames ahead of time so that they are ready to go. This is expensive CPU wise but gives highest chance of not getting dropped frames with modest settings especially during rapid scenery transition processing. FFTF should decrease the chance of dropped frames even more because you can slow down CPU scenery loading processing and keep the benefits of internal frame limit which "should" give more headroom for other types of processing that are needed in fast scenery transitions.
  4. Hi Bruce "smoothness" might not be an issue in your scenario. If you are flying in a straight line or sitting on the tarmac the scenery beneath is transitioning gradually so there is already a good balance between processing and scenery loading and no need for a dynamic FFTF. Put the plane into a tight bank now look at the scenery rotating with the bank then test smoothness. I "used" FFTF in v4 precisely because I needed smoothness in a steeply banked aircraft over ORBX scenery. That is where the low FFTF number like 0.1 or 0.01 helped because all CPU was dedicated to processing and not being diverted into scenery loading jobs as well. Then once the plane is flying in a straight line more FFTF (eg 0.33) can be dedicated to scene loading because in a straight line the CPU doesn't have to process scene as much. It seems from reports that this is still the same in V5.
  5. Thanks bruce nice to have numbers. FFTF is about controlling smoothness not just frames ie) allocating time slice as in how much time is spent on rendering - so it might not be zero sum.
  6. Thanks for this Harry. This sound bug in windows has been really annoying. I found that your manual fix works but I couldn't get your bat file version to work. The bat file version does do the switch in the dialog box but it doesn't change the sound. Seems like it needs an actual mouse click to trigger it. Never-the-less the manual method works so thanks.
  7. Here you go, a product written by a developer who is regularly on this forum: https://aitrackerx.weebly.com/
  8. There is so much you can do in P3D because of the huge numbers of addons it is simply incredible. MS2020 is not going to able to compete with that for a long time. At the end of the day it will have somewhat better graphics and somewhat better weather but at the expense of functionality. If P3Dv5 breaks backward compatibility it will take a lot to shift me from P3D 4.5...4.6 though.
  9. Not really, it is a poor substitute. CumulusX models many more things like thermal lean. Not sure about RealTurb working with Active Sky though.
  10. Control Panel->Sound->Communications tab->do nothing option Doesn't work for me but might for you. Has to do with Win10 automatic handling of sound volumes for mic comms.
  11. One of the most beautiful things I have seen here on Avsim. Not the plane...the cooperation between you guys to mod this awesome little plane.
  12. Great news. WinchX works in a similar way. It complains that there is no FSX but it doesn't matter. The CumulusX clouds look a bit dated but they blend in pretty well with active sky or sky force clouds and you can fiddle with the post processing to make them look better. If you have a low end system turn off simobject and cloud shadows. You can also have CumulusX run on its own core to help keep simulation smooth if you want. If you like it you might want to get the registered version.
  13. If you don't have the old FSX installed the installation is pretty straight forward. To get CumulusX! working with P3D v4, I ran the CumulusX! installer and then entered the path of my Prepar3D v4 folder. Then you run the CumulusX!.exe file when you are in the simulator. It will be in the modules folder. Try a fair weather scenario with medium cumulus clouds. If you see CumulusX! clouds and CumulusX says it is connected you are good. It won't do any damage at all everything it does is light touch to your installation and when it complains at various points about not finding FSX etc just ignore it with cancel button it doesn't need it. CumulusX can't even find where the P3D ini files are since it doesn't know it exists so it is incapable of stuffing with them. It merely puts some assets into the P3D modules folder and then connects via simconnect and complains about not finding FSX but it doesn't matter. If you get it going you should try to disable P3D internal thermals and also any weather engine thermals since CumulusX does all types of gliding lift better than any sim and rivals condor. If you have FSX installed, that confuses things a little because CumulusX will update the FSX ini files even when it is pointed to P3D. If you are nervous about it, install CumulusX to an empty folder and manually drag the installation into P3D yourself. That method works fine. PS) You don't need use the DLL file version the CumulusX app works perfectly with the EXE file.
  14. With the current builds of windows 10 it still happens with the windows audio control setting I can confirm that. I've had no luck tracking down the cause. It probably does have something to do with multiple apps wanting to use the mic.
  15. Moisturizer on your face after every VR session cures the problem of having a permanent impression of your headset lined into the skin around your eyes. I woke up a while back one morning shocked that after 10 hours of sleep I still had the headset line around my eyes from the previous night.
×
×
  • Create New...