Jump to content

glider1

Members
 View Profile  See their activity

  • Content Count

    678

  • Donations

    $10.00 

  • Joined

  • Last visited

Posts posted by glider1

  4. Posted

    3 minutes ago, Andrew Urbanczyk said:

    Thanks, I managed to get it working.

    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.

  5. Posted · Edited by glider1

    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.

    • Like 1

  8. Posted

    I had a theory that in VR your eyes would get lazy because the focal length never changes for objects near or far away. At least on flat panel you can look away from the monitor to exercise your eyes but in VR you can't. I spend probably 3-4 hours a day in VR so I went into my favorite non-flight simulation software - first person tennis to test a theory.

    I put the racket right up to my face then looked all the way to the far end of the court. My eye muscles still had to work not to create a double vision when I look at the racket really close.

    Weirdly, I then clicked on the Oculus home button where I can put the virtual hand controller right up to my eyes. But then I didn't need to work to keep it from going double, only in first person tennis.

    So I guess I'm confused. I think VR might be the same problem as it is for astronauts in weightlessness, because they can't escape zero gravity their muscles atrophy - but I'm really not sure.

  11. Posted

    Definitely need to wait. Problems are:

    • The Ryzen 3950x is 300$ more than the i9900k in my country
    • Only two cores of the 3950x hit 4.7GHz otherwise all cores 4.3GHz
    • What will simulators go for? Will they stick to doing the hard computation on the two fast cores leaving the slower cores for rendering?
    • Will the simulators prefer higher all core clocks?
    • Will the simulators prefer more than eight cores?

    My guess is that more work should fall on the GPU in the future so eight CPU cores should be enough for simulation going forward.

    If the clock/heat ceiling has been hit with 5GHz then the best buy would be an overclocked i9 9700k (i9900k HT is not necessary) saving the money on CPU for the next gen GPU which would be the 3080TI which rumours say will be more price competitive than the 2080TI.

  12. Posted

    I think at times like this you should fall back to flat screen and check the sim operation for expected performance using default aircraft. I recently had a situation where a freeware aircraft would show a 2D panel on the monitor correctly but in VR the panel was a black square frozen in the middle of the view. Other payware aircraft panels would work normally in VR.

  17. Posted

    I had this problem as well in VR but not so far in V4.5. I used to get it in V4.3 and V4.4.

    Best of luck with it because it is a difficult problem to sort out. I never found out the reason why it fixed itself in my case. Could have been an update of the oculus software for my headset but really not sure. Might have been a change in the affinity mask I was using. It can be a baffling problem. It could also be a defective video card. It could be a power supply issue. There are so many possibilities with this particular error it is not funny. It could also be non-standard scenery I was told that could trigger it too.

    You could try "prefer maximum performance" for P3D which is the only setting I change now in the nvidia drivers. Everything else is default. I adjust P3D settings for GPU usage on average around 50-60%.

  18. Posted

    On 10/6/2019 at 6:19 PM, Lorby_SI said:

    Hi,

    The SimObjects are added to the simulator with the addon package "\Documents\Prepar3D v4 Add-ons\Lorby-SI Content". Make sure that "Lorby-SI Content" is active on the Options->Add-ons dialog in Prepar3D.

    When they are there, then on the first page of the CDX Settings activate "Show 3D crops" and "Show marker poles".

    When in doubt, please send me an email, address is on the last page of the manual.

    Best regards

     

    Thanks Lorby for the excellent support sorting this problem out for me really quick via email.

    The fields now contour with the Orbx terrain with the "disable surface checks" option. It is working now with Orbx scenery in NZ south and I'm looking forward to having some fun with this great app.

    Pity that Orbx didn't adhere to the P3D standard for terrain creation which is what caused this problem in the first place.

    Cheers and thanks again

  19. Posted

    6 hours ago, jozeff said:

    Thanks a lot!

     

    Because of your advice I'm not planning on buying the reverb.

    You convinced me I need a 2080ti and that is really not in my budget.

    As I mentioned above I'm looking for the following to accompany my Rift S. Would that work?

    i7 9700 k

    MSI Z390-A PRO motherboard

    Msi 2070 super

    32gb 3200 Kingston memory

    Thanks for your useful advice!!

     

    A VR flight experience is for fun, a few hours a week. My wife gets hickups when she sees the 2080ti prices 😄😄

     

    Jozeff

     

     

     

     

     

    I think you will do very well what you have there should be a well matched Rift-S system for simulation. The 9700k is perfect (try to set up a system where you can overclock it) and you haven't wasted your money on a 9900k because hyperthreading is unnecessary on 8 cores.

    You will need to supersample the Rift-S to 1.5 as joepoway says and that should be very doable with the 2070super because I could even dial in 1.5 on a 1080. The 2080TI is simply a rip off no question so avoid that.

    The 8GB VRAM is good enough for the quality of the Rift-S display since you will still be restricting the scenery settings to suit the limitations of the Rift-S display (which will still be very very enjoyable experience) and so won't hit the memory wall.

    The problem with the HP Reverb is that since it is just 110FOV with good clarity, you are very quickly going to get frustrated to compensate the sameness of the 110FOV experience so will start cranking up the scenery settings to appreciate the clarity of the screen and then you will quickly hit the wall again on only having 8GB VRAM and minimum spec GPU.

  20. Posted · Edited by glider1

    Hi Lorby

    I just bought CropdusterX and installed it into P3D 4.5 HF2.

    I loaded a flight out of NZGC in ORBX new zealand south island which does cropdusting in real world.

    I connected etc etc.

    When I fly over the random dry field there (within 100 feet as indicated in the Cropduster app) there are no pole markers, no green overlay no plants nothing there.

    The app registers my position etc

    I tried settings like "disable surface checks", "show green overlay"

    There is nothing in the P3D addon menu for CropdusterX

    There are also no simobjects in the addon folder.

    In the addon folder all I see is:

    C:\Users\Harry\Documents\Prepar3D v4 Add-ons\Lorby-SI CropDusterX_P3D_V4
    Doc (folder)
    Sound (folder)
    CropdusterX.....exe
    led_counter....ttf
    Lockheed......Simconnect.dll
    Uninstall_cropdusterx.exe

    When I tried to define a custom field by slewing, the app froze and so did P3D.

    So I guess first step is to ask, where are the simobjects located? The database in the app thinks they exist.

    Help would be appreciated.

    Cheers

    (PS, there was no log file in C:\Users\Harry\Documents\Prepar3D v4 Add-ons\Lorby-SI CropDusterX_P3D_V4\doc

  21. Posted

    2 hours ago, joby33y said:

    Hi, Can you say more about what you mean here ?  I get the fact that a lot of people dont see value (bang/buck) in the 2070's generally,  but would like to understand more about what refer to above.    

    I'm on CV1 right now and will upgrade soon, and Reverb is the leader.  My card is 1080Ti.  

     

    cheers, 

    JB

    I'm going off intuition not facts.

    To me a HP Reverb + RTX 2070 feels wrong for flight sim but it would be fine for other purposes. Instead of getting the best GPU you can afford, you are putting your money into just another 110FOV headset from an inexperienced VR company and it is not even OLED like the vive pro.

    To me an Oculus Rift-S or Oculus Quest with PC-link (not yet available) teamed with an RTX 2080 makes more sense. For the same money you are getting the best GPU you can afford with a cheaper headset that is still 110FOV and has acceptable resolution from a company that really knows VR. The quest will even be OLED and it will support hand tracking.

    Personally I'm waiting to see what the Pimax 8K+ reviews are like. That to me is a genuine upgrade from a CV1. I am still happily on the CV1 supersampling the old headset with a beefy GPU bringing the clarity up to acceptable levels.

     

  22. Posted

    Don't make the same mistake you made years ago. The GTX 970 was never powerful enough for the original rift to run sufficient supersampling to get rid of the shimmering and blockiness. Make sure you pair the next headset with the graphics card perfectly. I doubt a HP Reverb and a 2070 card are a good team. Also, make sure you get a i7 9700k eight core processor nothing less.

  24. Posted

    35 minutes ago, joepoway said:

    I could be wrong but I think the headset at least my Rift and now Rift S clips itself at multiples of the headset frequency Rift was 90Hz and Rift S is 80Hz.

    So I would get 90 > 45 > 30  and so on and now 80 > 40 etc. with P3D set to unlimited with Vsync and Tripple buffering OFF.    Also use Single Pass Rendering in P3D !

    Additionally I use the Oculus Debug tool to Disable ASW and set Pixel Density to 1.6. 

    I've never tried to limit frames in P3D and I'm not sure my Rift would even acknowledge that if I did??

    Joe

    Thanks for that. Do you find P3D now trying to lock your simulator to 20fps in dense scenery situations? On the old Rift it would try to lock to 22-23 because that is 1/4 of 90.

  25. Posted

    15 hours ago, Iceman2 said:

    Hi Glider, I’m currently using “wide” which is 200 FOV. Unfortunately this can cause clipping depending on which aircraft you sit in. For example sitting in the PMDG B747 I get a slight clipping which requires a move of the eye position (head down a bit) to avoid this, whereas sitting in the Maddog its fine and the 200 FOV is simply awesome. 

    There is definitely a performance hit by selecting wide mode over normal mode but with the 2080ti it handles the torture very well.

    IM

    Thanks!

×
×
  • Create New...