glider1

Members
  • Content Count

    354
  • Joined

  • Last visited

Everything posted by glider1

  1. glider1

    RTX 2080 ti P3D benchmarks?

    Does VR behave the same way as flat panel when it comes to performance in sli though? We need someone who actually uses VR to do tests in VR P3D.
  2. glider1

    OTT and FlyInside

    Yes blueshark is right. Don't use OOT supersampling flyinside has it built in. You will only overload the GPU.
  3. If the Quest is wireless out of the box when connected to a PC, I could be in if it has slightly better image quality but I doubt it. The Vive Pro would have to drop to half price before I'd be interested for flightsim. Not worth it compared to Rift CV1. Pimax 5k+ is a big possibility if the price of a 2080ti comes down to something resembling sanity. I have a feeling the 5k+ 2080ti combination are going to be very well suited. I might even pay top dollar for the 5k+ 2080ti combination even if it embarrasses me to admit I'm a sucker. Pimax is the solution for flight sim with reasonable screens and fov but prices are too inflated to make it worth it compared to being on Rift CV1 which is still good enough. People who have trouble with image quality play around with shader presets and autostarx for night I agree the banding at night is bad but it is still a great experience at night some of the most memorable flights of my life have been at night in the Rift. Make sure you turn off HDR at night otherwise you will get greyed out effect. Also I think the banding is not just the headset but a weakness of the sim itself. EDIT: The biggest concern I have for Pimax 5K+ is not the price but support and warranty servicing.
  4. glider1

    My Weekend VR Experience

    The rift has to be supersampled to make the visual quality acceptable this has been known since the first gen headsets were released. The performance on a 7700k 1080 with 1.5 supersampling is very good and graphic quality is acceptable for everything but large cockpit aircraft. This has been known since LM released P3D 4.3. Performance is good because LM in 4.3 have made VR very usable out of the box on current hardware and even though you have to tune settings down relative to a monitor, it simply doesn't matter because the lower resolution of the 1st gen headsets don't get benefit of higher visuals anyway. I appreciate the personal perspective of the OP but it is not to be taken as a review grade piece of writing. VR is already a massive improvement for most types of aviation except the tubeliners.
  5. Yes many some have used it in v4 so have I. Takes a bit of work to understand how to use it but it works great. It can control the brightness of stars and adds a huge database of stars in accurate locations without any performance hit. I could walk you through it but am not at my flightsim computer. The readme is a good start. Basically it just mods the stars.dat file which is the exact same format in P3D as it was in FSX. You could also try Stargazer which is payware but should do a simiilar job. In VR the night sky is very good now. Even saw a a couple of shooting stars which look spectacular in VR truly I mean that.
  6. Yes you are right but you can fix it with autostarx freeware. It takes a bit to learn but it works in P3D I use it to fix the night sky in VR.
  7. Depends how much money you have got. If you are rich, you can buy now and upgrade later. If you are tight, Rift/Vive resolution is good enough with a 1080 even when the 8k shows up because the price of first gen VR should continue to drop. "Good enough" means you can read most things with supersampling in GA aircraft perhaps not in the really big tubeliners. Ideally Vive pro/samsung galaxy resolutions are preferred because they will do everything in flightsim with reasonable clarity.
  8. The other thing is that the Vive Pro will be going wireless.
  9. glider1

    Carenado G1000 and Navigraph Expansion

    I have the Phenom 100 navigraph expansion. I enjoy it but there are bugs and omissions enough that it makes me look around for a better implementation. It is good enough to get you started into the big wide world of G1000 but the more you dig in the more issues you start to find. Also keep in mind that you cannot load a flightplan into the G1000 nor can you save one. You have to manually enter it every flight which can be a pain if there are reasons why you need to save a scenario with the G1000 state remembered for a later session. At one time the Phenom 100 framerate was considered pretty bad but now in P3D it seems to be one of the lighter business jets on fps with glass cockpit from what I read. Possibly because some of the details are not implemented both in the G1000 and flight dynamics of the aircraft which actually help with performance.
  10. glider1

    Flight1 Mustang is available

    Thanks for the info on VR. I disagree on fps for single pass you don't need 45FPS unless you are running ASW. If you set the display settings to vsync on unlimited and ASW off, P3D syncs VR in multiples of 90. So if it can't get 90/2=45 it will drop to 90/3=30 and if can't get that it will drop to 90/4=22.5. For me in busy airports the phenom 100 will drop FPS to 90/4 or 22.5fps but it still is smooth. Agree, the spiking in FPS would be a problem.
  11. glider1

    Announcing the Zenith 701 for P3D V4!

    A proper STOL GA aircraft with accurate flight model is badly needed for P3D.
  12. glider1

    Is VR blurry?

    I've finally finished with Flyinside and think native P3D performance is better if you do it right. Steps: P3D settings to vsync on and unlimited Put all settings on minimum including HDR off shadows off and check performance FPS will lock to either 90fps, 45fps, 30fps or 22.5 fps because these are vsync multiples of 90 (native refresh) Don't fight the fps, let it lock to one of those combinations. It depends on scenery load. It happens because of vsync. Add settings one by one and recheck performance each change. FPS may not change until it suddenly reverts from one of the FPS multiples. OTT setting at least 1.5 Get eyes checked if still blurry. Do that and you can have a very happy time on Rift but you need decent hardware CPU>4GHz and at least a 1070. Expect performance similar to that if you were running a 4K monitor but visual details are not set as high because they don't need to be.
  13. glider1

    Accu-Feel v.2 Air, Land & Sea (P3Dv4) Released

    Hi Neil I am also in VR. Accufeel is the only way to go for you if you are still with Flyinside because camera movement isn't supported but airframe shake does. In native VR however everything works like normal. Chaseplane can be used to shake your view and works in VR for everything except static view and custom HDR adjustments (only the P3D standard HDR works). I use a combination of a slight headshake in VR with chaseplane it doesn't make me nauseous if I keep the settings conservative definitely adds to immersion if you don't have a motion platform.
  14. It is actually a feature of VR. You get the equivalent of the old FSX 1/2 Vsync fullscreen tweak because it is actually running in the VR equivalent of fullscreen mode not having to worry about windowed borderless execution. Because it hardware locks to 45fps, 30fps or 22.5fps you can adjust the settings to match what lock multiple you are aiming for. I don't know why people think VR performance is bad. The drop in visual quality of the headset means you don't have to run as high visual settings and so your performance is still good with the benefits of 3D and 1:1 scale.
  15. I gave the free trial of dxtory a go in native VR again brett. Problem is that it can't hold a software vsync firmly enough so if you set dxtory to 30fps for example but the unlimited fps are really wanting to gravitate to the real hardware vsync of 45fps (90/2), there is an underlying fight going on between dxtory wanting to keep it at 30fps but the sim wanting it at 45fps which reduces smoothness. I'm finding in native VR that using vsync with tripple buffer unlimited works well enough. The internal vsync keeps frames locked at ratios of 90 so depending on hardware in rural areas it locks to ~45fps (90/2), in regional city it will lock at ~30fps (90/3) and in big cities it locks to ~22.5fps (90/4). The only downside is when the internal vsync can't decide what multiple to lock to which can reduce smoothness. For example if you are in a 45 degree bank in a rural area it will lock to ~45fps for a period through the turn. When orbx scenery comes into view it suddenly locks to ~30fps then back to ~45fps really quickly which reduces some smoothness but it is good enough. In native VR I tend not to use internal FPS lock because it is too expensive on FPS (it worked better in flyinside) but locking it to vsync/unlimited in native VR with appropriate settings works really well Lockheed Martin really made good improvements to VR performance improvements in 4.3.
  16. In native VR everything behaves as you would expect. I don't use flyinside anymore because LM nailed VR in 4.3 the performance is at least as good possibly better in my experience. VR rift vsync is in multiples of 90/45/30 instead of the usual monitor refresh multiples of 60/30/20. External limiters work but not nvidia inspector unless I was using an old version. I have used dxtory as the external limiter in VR because it's free, you can adjust it on the fly and I thought it did a slightly better job than NI inspector at holding the software vsync steady anyway.
  17. glider1

    oculus rift

    You need controllers or can you manipulate windows in native with a mouse?
  18. Hi Dave Infinite loop with ATC handing me off to approach from center in an endless loop Sequence of events I was flying a GA IFR into Nelson NZNS in New Zealand from Stratford NZSD. I created a flightplan in P2A and hit Autoplan. P2A added an approach for the flight. I took off from Stratford which is uncontrolled. No frequencies available on the ground so I take off on Multicom freq. Climbing out I contact centre and ask for IFR clearance which they give me I get instructions everything is fine including handoffs etc At around 16:00 On TOD center wants me to contact Nelson approach in an unstoppable infinite loop. I had to disconnect and reconnect to stop the controller repeating the same message over and over. then manually ask for a visual into the airport from approach which they give me but they don't hand me off to the tower as I arrive on final Please find attached logs and flightplan. Note that the infinite loop happens at around 16:00. Link to logs: Logs_p2A_glider1_24062018.zip Thanks for your help. Glider1
  19. Thanks Dave. What about airports where there isn't even UNICOM? How do I find a center frequency that works either on the ground or in the air? Australia is full of long dirt airstrips that have no services at all with vast distances between them. Normally I'd look it up on a chart but in P2A I can't be sure the frequency is live unless it is in the frequency list. Thanks, Harry
  20. Hi Dave sorry to be a pain but this problem is back again for me on 2.5.0.4.x64.R3. Here is a link to the log: https://www.dropbox.com/s/7qg6ie1kc67sk8h/P2A_2018_Trace_File1.log?dl=0 It could be because I flew out of Norfolk Island NSW Australia which is uncontrolled after filing an IFR plan. I was hoping to contact center once in the air. Your software doesn't list center frequencies (I wish it would!) so I was flying blind for frequencies until approach turned up in the list for NWWE. No center frequencies worked not even official frequencies and not even the ones displayed in the taxi monitor. In order to find out if center is live I pretty much always start up by giving them my callsign and my altitude and wait for them to acknowledge. I also listen for background chatter which is a good indicator that the frequency is live. So I gave up on center and contacted NWWE approach but forgot to get IFR clearance from them. Approach didn't seem to care and immediately started giving me IFR directions which I found very strange (there is a bug like that in PF3 as well). But then they handed me off to another approach and that is when the infinite loop started..... At 16:42 in the log you start to see dozens of Trigger:ReachedArrivalSetup. I eventually had to disconnect, reconnect and refile my plan. Thankfully, I could contact approach and they carried on vectoring me in which allowed me to complete the flight successfully. But having to reconnect is a pain in the a... especially with a VR headset on. Could you take a look at the log please dave especially from 16:42 onwards? Sorry for the long post I realise you are very busy. Cheers, Glider
  21. glider1

    Using AiTrackerX for flying as a passenger

    Hi Oliver It is a complicated problem to pin down. Today no CTD for reasons I don't understand but I can induce one pretty easily. A couple of observations: I think center ATC think that the plane is being followed by another and will issue a traffic alert for aircraft less than 1nm 🙄 ATC stopped directing the plane during the flight. I had to end the session after 3 hours because the plane was way off course never going to make the dispatched destination. Probably a P3D ATC issue for AI planes. At least I learnt the aircraft systems it wasn't a waste. AI doesn't seem to react to weather engine effects like turbulence etc? What is really good about it is that you can learn the systems of the aircraft while they are all live enroute. The fuel levels update, the map updates, the gauges, FMS, lights etc. Much better than learning it on the ground while the plane is stationary. Not sure if fuel consumption figures are accurate probably not considering it is an AI flying. Boy they are rough pilots. No subtlety at all 🙂
  22. glider1

    Using AiTrackerX for flying as a passenger

    Ok thanks Oliver. I'll try to chase it down. Not sure what has changed in my system going from 4.2 -> 4.3. It is a caranedo phenom 100 with navigraph extension. This mode of flying is actually very useful for learning systems. You can do a flight as a copilot and physically interact with the glass cockpit and learn FMC etc while your pilot flies you somewhere..... at least you could in 4.2 in the same scenario.
  23. glider1

    Using AiTrackerX for flying as a passenger

    Hi Lorby sorry about that P3D 4.3 CTD. Thanks ok I get the concept now. Nevertheless the param changes in pilot view are causing the P3D CTD not every time just most of the time. Appreciate that you are busy.
  24. glider1

    Using AiTrackerX for flying as a passenger

    Hi Oliver - I had this working quite reliably in 4.2 using your procedure above but now in P3D 4.3 it crashes when changing parameters. The weird part is that cockpit view looks correct but when you look out the window at the wings, there are two wings superimposed vertically like a biplane. If you try to correct that with parameters it doesn't superimpose exactly and can crash to desktop. Could you in your spare time just do a check of this in P3D 4.3 just to be sure it is working and not a problem my end? Maybe I need to reinstall AITrackerX or something? Thanks
  25. glider1

    WhereAreMyAircraft - WAMA updated to 1.12

    Hi Oliver - All's good. I must have gotten AITrackerX into a strange mode first trial. This time I did it per your instructions above and didn't use the observer pod but was in the actual aircraft I intended to be a passenger in before commencing following. I used the shortcut keys to change my position in the seat in VR. No clipping absolutely perfect as if I were flying the plane. I could actually interact with the G-1000!? Pilot didn't seem to care 😉 Interesting way to learn ATC procedures too for beginners. Excellent thought that people with disabilities are going to love this feature in VR! Good on you for thinking of them. I don't have CameraX installed. Cheers