T would be nice to hear from someone on the product side on any plans to fix this or not. But is that really acceptable behavior for the product to exhibit? I don’t think it is and I am not the only one with this issue. Yes, I have seen the frame rates on AviTab and this does happen when the frame rate is anything other than 30 or 45 (even 22 seems to be ok). For you to say, “Lower your settings to get a better experience…” well, I can probably do that in 11.41 if I lower things down to the point where my fairly powerful system renders a sim that looks a mess. Note that I am not complaining here about anything – just wondering if this type of things is planned to be addressed. One of the enhancements that was to come out of the move to Vulkan was better management of textures and help eliminating stutters on a reasonable system with reasonable settings – which I believe I have. That should give me a smooth 30 fps (or at least 22 FPS) in VR. I am getting around 60 fps sitting on the ramp in non-VR mode. My GPU isn’t the issue here since the textures never full occupy the VRAM. Sliders are set to objects on high, HDR, 2x AA and textures max. I should get descent results with that system and reasonable settings. I could probably lower my settings to all the way left on the GPU and CPU sliders, but wouldn’t that defeat the purpose of some of the benefits of moving to the Vulkan architecture? I have a i7700 1080ti with 11GB vram. And maybe to see if one of the developers could comment on plans to address it. Just a finding I wanted to share in the developer blog comments to see if others testing the beta have experienced anything like it. So I guess my questions is – are there plans in the 11.50 development/beta/release roadmap to address this kind of micro-stutter?Īgain, I have filed defects using the bug reporter, so I don’t expect this to be an official defect report. When you move your head, it’s like the numbers get double-visioned and shake/micro-stutter. Like looking at the MCP and the digital numbers for speed/altitude. Like an exact copy of an image 1mm or so away from the first. I guess I should have not used the term ‘blurry’ to describe my issue. My question is around the micro-stuttering and if it was on the radar to be fixed. I read the phases of development and priority for releasing beta builds. And if not, are there plans to address additional smoothnes/stuttering/blurriness/FPS in future beta releases that we can test?Īn, thanks I read that post when it came out and commented on it actually. (not that this has ever happened to me I saw it in a movie….)Īnyway, just wondering if this beta addressed any underlying VR smoothness issues. Almost like if you had too much to drink and move your head too fast… the world stutters a bit and gets blurry. But if I start to turn my head, they stutter and get blurred a bit until my head stops moving. For example: take the digital numbers on the 737 MCP – if I look directly at them and don’t move my head, they look clear and crisp. When I disable these tools completely and test with the beta versions, I get the micro-stutters again. I try not to use plug-ins during the beta, but it seems if I use a tool that ‘locks in’ the frame rate, the stuttering goes away a bit, but then I’m locked to a specific framerate. I have filed a couple of bugs related to this, should I keep filing them? I noticed there were some bugs fixed related to VR, but not sure if there was any under-the-hood work done to help VR performance especially around the smoothness. I am still getting the micro-stutters in VR. You may need to show hidden folders to access it. The name will include the date & time of the crash and will end in. This can be found under your username /Libraries/Logs/DiagnosticReports. Mac users do not have the ability to auto report, so they should fill out the bug report form, and include the Apple crash report as well as the log.txt. If you send an auto report, please do not also send a bug report form email. You can include your email if you want us to be able to find your specific crash, but we do not need the message field–the log and back trace will have pretty much all the info we need. The best way to help us handle crashes on Windows and Linux is still to submit the auto report form. We are trying to cut through the noise and provide better information in logs and in the remaining crash reports to fix issues faster, and let our support team (primarily me) get the inbox under control. We’ve been seeing a huge uptick in volume of bug reports and auto reported crashes since the initial 11.50 public beta release. This update was focused on crash fixes and better triaging. (Steam users: it’s on the servers and we’ll hit go in a few hours if we don’t hear reports of massive crashing and pain again.) X-Plane 11.50b4 is now available if you update via the Laminar Research installer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |