

Gryzor
Members-
Posts
1221 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Gryzor
-
Thanks Yaga. That is exactly what happens between true and false shader parser option. As you said, many time has been posted this in other posts. But no solution from ED since one year appart of closing posts.
-
Many of us post many pics about not rendering issue in one eye, not many days ago I sent you a private message about some pics for this issue from other posts. As many times I said, this bug appears one year ago since 2.5.6 and it seems nobody at ed take care of it. In fact, I saw many post closed without any solution appart the message from you to putting shader parset on false. It seems to me that ED dont want to hear about this issue, closing posts without reason or solucion. COME ON FIX THIS ISSUE!!!!! (Please BN speak seriosly with ED... this is unacceptable from VR user, specially with older versions not affected by this bug). ED don´t have any VR device to test it? It is a rendering problem at some distances, very noticeable and disturbing (at least to me...).Thanks.
-
First thread - squeezing out fps in VR - 3060Ti
Gryzor replied to plasma1945's topic in Virtual Reality
Please can you attach your modified scenevr.lua file? thanks- 9 replies
-
- 1
-
-
- performance
- 3060ti
-
(and 1 more)
Tagged with:
-
I prefer that they remove replay completely, just for freeing resources (more fps)
-
Thanks for your quick answer. My system is perfectly stable with other modules, other games, other benches (OCCT or prime95 many hours....), fumark... etc and I can have any crashes. Maybe it could be a bug from DCS software itself? It surprise to me that my crash file it´s exactly the same as crash#2. Even the same codes! so it seems to me a software bug, due code similarities 0x0000000000439F70 (nvwgf2umx): NVDEV_Thunk + 0xBC8B0 0x00000000010B5D4F (nvwgf2umx): cask::ShaderList<cask::SoftmaxShader,cask::SoftmaxOperation>::availableShaders + 0x7916F 0x00000000010B5CCA (nvwgf2umx): cask::ShaderList<cask::SoftmaxShader,cask::SoftmaxOperation>::availableShaders + 0x790EA 0x00000000010AAEED (nvwgf2umx): cask::ShaderList<cask::SoftmaxShader,cask::SoftmaxOperation>::availableShaders + 0x6E30D 0x0000000000681B4A (nvwgf2umx): cask::SafeEnum<cask::GemmChip_ENUMCLASS_SCOPEWRAPPER>::SafeEnum<cask::GemmChip_ENUMCLASS_SCOPEWRAPPER> + 0x165CA 0x000000000163776C (nvwgf2umx): OpenAdapter12 + 0x3A88FC 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14 0x000000000004D241 (ntdll): RtlUserThreadStart + 0x21 In addition, searching on DCS forums, results with "SoftMaxShader" issue are only showed since 27th january. No more results before that date, in other years, so I suspect it is a software bug (or maybe a wrong Nvidia driver / W10 update).
-
I have another crash with F-14 module. The last 2 months, all of my crashes happens with this module. I think its not related with pagefile or mem, or system overclocking, maybe it could be a issue with that module?. It happened exactly when opening wheel comms with F-14, just after taking off from carrier. Attached logs dcs.log-20210221-184053.zip
-
It could be possible to have some words from DEVs? I think that having this bug since 2.5.6 appears (with 2.5.5 was nonexistant), one year ago,... is not acceptable. Maybe it will be solved for 2.7? I hope ED don´t forget that the most entusiastic customers are in VR, in this sim.
-
Thanks BN. I suppose you´ve tested 2.7 version. Please can you tell me if the not rendering some parts in one eye bug would be fixed in 2.7? We are with this issue since 2.5.6, nearly one year ago
-
Simply... due the detail I seen with new clouds I cannot believe it. Maybe 2.7 will be multithreared?
-
Bumb. Any word from devs? maybe in 2.7 this will be solved?
-
Done. Many thanks. How do you know that the cause was deleting temp folder? some hint into the logs? thanks
-
Hi Lefuneste, I noticed that with 8.2 version I have more fps hit than with previous one 7.4 - maybe due new shaders added? I tested those two in the last DCS beta Please could you update a alternative version from 7.4, but without new features added, just for not hurting fps much more? Great mod. I hope some day ED implement at least sharpening feature. Thanks.
-
I attach log files. Any help please? # -------------- 20210129-201849 -------------- DCS/2.5.6.60720 (x86_64; Windows NT 10.0.19042) C:\WINDOWS\system32\d3d11.dll # C0000005 ACCESS_VIOLATION at BF4F89C1 00:00000000 SymInit: Symbol-SearchPath: '.;C:\RS\DCS World;C:\RS\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Gryzor' OS-Version: 10.0.19042 () 0x300-0x1 0x00000000001289C1 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0xF431 0x000000000008CC2D (d3d11): CBTProc + 0x1EA7D 0x00000000000176BD (dx11backend): RenderAPI::DX11Renderer::setShaderResources + 0xCD 0x0000000000062ADD (dx11backend): createRenderer + 0x4AB8D 0x000000000006237D (dx11backend): createRenderer + 0x4A42D 0x000000000005FB59 (dx11backend): createRenderer + 0x47C09 0x0000000000011E84 (dx11backend): RenderAPI::DX11Renderer::draw + 0x364 0x0000000000026F1F (NGModel): model::load_json_mat + 0x56FF 0x000000000002A09E (NGModel): model::DeckMaterial::draw + 0x314E 0x000000000002A397 (NGModel): model::ModelMaterial::draw + 0x2D7 0x0000000000043FDB (NGModel): model::NGModelLods::reload + 0x21B 0x0000000000121497 (Visualizer): RenderParserImpl::DrawZWrited + 0xA7 0x000000000012613E (Visualizer): RenderParserImpl::isEmpty + 0x420E 0x0000000000125B12 (Visualizer): RenderParserImpl::isEmpty + 0x3BE2 0x000000000015B35F (Visualizer): smSceneManager::CreateSceneManager + 0x6CFF 0x00000000007AC487 (DCS): CoreUtils::TempFilesManager::operator= + 0x3BE8D7 0x00000000007BFC53 (DCS): CoreUtils::TempFilesManager::operator= + 0x3D20A3 0x0000000000790A04 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A2E54 0x0000000000790DC9 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A3219 0x00000000018F4F56 (DCS): AmdPowerXpressRequestHighPerformance + 0xC86F52 0x000000000098580E (DCS): CoreUtils::TempFilesManager::operator= + 0x597C5E 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14 0x000000000004D0D1 (ntdll): RtlUserThreadStart + 0x21 dcs.log-20210129-201849 F-14 CRASH.zip
-
It crashed when approaching supercarrier. I attach logs files & mission. Anyone have had this sort of crashes? Some solutions please? Thanks Crash log: # -------------- 20210129-201849 -------------- DCS/2.5.6.60720 (x86_64; Windows NT 10.0.19042) C:\WINDOWS\system32\d3d11.dll # C0000005 ACCESS_VIOLATION at BF4F89C1 00:00000000 SymInit: Symbol-SearchPath: '.;C:\RS\DCS World;C:\RS\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Gryzor' OS-Version: 10.0.19042 () 0x300-0x1 0x00000000001289C1 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0xF431 0x000000000008CC2D (d3d11): CBTProc + 0x1EA7D 0x00000000000176BD (dx11backend): RenderAPI::DX11Renderer::setShaderResources + 0xCD 0x0000000000062ADD (dx11backend): createRenderer + 0x4AB8D 0x000000000006237D (dx11backend): createRenderer + 0x4A42D 0x000000000005FB59 (dx11backend): createRenderer + 0x47C09 0x0000000000011E84 (dx11backend): RenderAPI::DX11Renderer::draw + 0x364 0x0000000000026F1F (NGModel): model::load_json_mat + 0x56FF 0x000000000002A09E (NGModel): model::DeckMaterial::draw + 0x314E 0x000000000002A397 (NGModel): model::ModelMaterial::draw + 0x2D7 0x0000000000043FDB (NGModel): model::NGModelLods::reload + 0x21B 0x0000000000121497 (Visualizer): RenderParserImpl::DrawZWrited + 0xA7 0x000000000012613E (Visualizer): RenderParserImpl::isEmpty + 0x420E 0x0000000000125B12 (Visualizer): RenderParserImpl::isEmpty + 0x3BE2 0x000000000015B35F (Visualizer): smSceneManager::CreateSceneManager + 0x6CFF 0x00000000007AC487 (DCS): CoreUtils::TempFilesManager::operator= + 0x3BE8D7 0x00000000007BFC53 (DCS): CoreUtils::TempFilesManager::operator= + 0x3D20A3 0x0000000000790A04 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A2E54 0x0000000000790DC9 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A3219 0x00000000018F4F56 (DCS): AmdPowerXpressRequestHighPerformance + 0xC86F52 0x000000000098580E (DCS): CoreUtils::TempFilesManager::operator= + 0x597C5E 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14 0x000000000004D0D1 (ntdll): RtlUserThreadStart + 0x21 dcs.log-20210129-201849 F-14 CRASH.zip
-
Any feedback from devs? maybe in 2.7 we will see this fixed?
-
I hope so!! I pray to not having much lower fps performance with the new clouds.
-
Issue is still present for almost any objects used in editor. There are some distances where some details are missing in the L eye. This bug came when 2.5.6 went into scene (near one year ago, with 2.5.5 it was perfect), and no one in ED same aware of this.
-
It seems that this issue is completely abandoned by ED. We´re with it this since 2.5.6 - february 2020 -. Even ED closed / removed other bug post regarding this issue. Disappearings clouds, disappearing wires on carrier, disappearing some details of AC or ground targets...
-
Please ED, can you give a update about this? Discussed many times also in other threads. This bujg came with us since beginning of 2.5.6. In 2.5.5 was inexistant. Thanks.
-
Maybe ED give us a gift for chrismasts updating to the new clouds for 12/23 patch... any chance? Specially looking how many months we´re stuck with the same branch 2.5.6... at least I hope some eternal 2.5.6 bugs for VR will be fixed (for example some objects at some distances not rendered in left eye)
-
With index With index is a bit strange: the more closer the lenses, the more greater the sweetspot is in my experience (about 80% of the total area). I always have the lenses closest to my eyes in Index, maybe if you have your eyes at longer distance, so you don´t notice such huge difference in comparison with G2. The fact is that with G2 I need to move my head just to read cockpit text or instruments, with some sort of "tunnel vision". In close dogfights with Index were easier to lock to a bandit, just because that. With Index, only moving my eye... easily can read cockpit instruments.
-
For me, index sweetspot --> about 75% 80% of total area. G2 --> 20-30%. Not much more. That´s huge.
-
I had Odyssey 1,5 years ago (not the plus) and the sweetspot were not as big as Index, but greater than with the G2. In fact, I´m very disappointed with G2 I don´t understand the fact that Valve helps in lens design..., so how resulted in so much less in clarity appart of 20% central area??? - and yes, I put OK my HMD on my head -. Compare Index with G2 is night and day in FOV and clarity edge-to-edge. In addition, G2 is a lot less brighter that Index, about 60 o 70% of Index levels (130% brighness setting). The only plus of G2 above index is the incredible clarity and resolution, but only in the sweet-spot small area, the 70% is blurry (with Index, I can look down to cockpit instrumen, reading radar contacts, without movin my nect. With G2 I have to move my head looking down the cockpit. Very unnatural feeling to me).
-
Personally finally I will sell my G2, I cannot live with only a small sweetspot zone. Will continue with valve index, appart to have less resolution, I has A LOT of clarity from edge to edge, and FOV is quite larger. In G2 I feel like I wear scrubber mask.
-
Reverb G2 strobe flickering while loading in Mixed Reality
Gryzor replied to Gryzor's topic in Virtual Reality
I have 1,5 years ago a Samsung Odyssey and I don´t remember such flickering during load, I think it´s some sor of recent bug from drivers / WMR or steamVR