The_Nephilim

well not in Win 10, Win 11 is a little better at it but I stil had issues in win 11 with the DCS assigning ecores to pcores tasks.. This way I know for sure what core is doing what..

Well I was thinking TDR at the last post. Glad you found a fix either way.. your Welcome..

Well I am guessing with Process Lasso running and my PC Parts OC like they are I am getting all I am going to get out of my system. I had also reduced the amount of Processes running on Windows, I think I am down to like 85 from 135.. Other then trying to tweak DCS a bit more I am balls out with my gear.. I had bought some faster ram and probally gonna try to OC that a bit more then the XMP PRofile as the RAM I have now is not a good OC Potential.. Maybe when the 5xxx series and intel 15th gen I may upgrade next year but proball not..

Yes saved games can get corrupt or just some mods acting wierd after DCS Updates.. I hope that is all it was.. What PC Parts you planning on getting? EDIT: I just noticed this any reason these cores are disabled? 2024-09-06 01:37:45.449 WARNING EDCORE (Main): logical core 16 is not available for this process 2024-09-06 01:37:45.449 WARNING EDCORE (Main): logical core 17 is not available for this process 2024-09-06 01:37:45.449 WARNING EDCORE (Main): logical core 18 is not available for this process 2024-09-06 01:37:45.449 WARNING EDCORE (Main): logical core 19 is not available for this process

Well that could be a good idea to reinstall and if they are SSD or M.2 drives use secure erase or nvme erase, some BIOS's have them in BIOS so go in there and if you decide to reinstall that is the best way to wipe the drive clean to make sure nothing nefarius is lurking about.. Those errors with nomex glove I see in everybodys log files I think it is an error with DCS code or similar and I dont think we can fix those.. they popped up recently too if I remeber correctly.. I hope a total wipe will help you out.. I mean if you already did the repairs. I would try and run the game one more time with all mods wiped out and clean and repair the game.. I also saw your Pagefile is pretty small 4096.. Maybe try and increase that proveded you have the free space on your drive you are going to put it on too like 65536.. put the same number in start and end..

The PSU specs should be on the website of the company that made it. Yes the blackscreen could be either a TDR or just Crashed. Have you tried looking at the logs in Windows?

Hi, If your able please post your DCS log file.. also a TRK file could be helpfull..

How old is the PSU??? it should have enough power how many 12v rails does it have?? is the GPU New? Maybe a Possible TDR issue with the GPU but you did have lots of Graphics errors. Did you use DDU to uninstall the nVidia drivers when you installed the GPU? Does this Black screen happen only when rain hits you?? If so have you tried a Clean Slow repair. also do you use any other mods official or unoffical?

Thank you that worked.. they look awesome will be looking forward too your thought on how they work ingame and all.. I had ordered a TEDAC as well..

Hey Apperently the video for me at least is blank, I tried to DL it and it said I needed to buy a HEVC Codec

well I have only 2 questions for you what is your PSU and what Hz rate do you use for the G2.. oh and your trk file there is no mission or whatnot it just goes straight back out to mission brief??? Your TRK file is not working? also this: 2024-09-02 18:32:28.836 WARNING EDCORE (Main): logical core 16 is not available for this process 2024-09-02 18:32:28.836 WARNING EDCORE (Main): logical core 17 is not available for this process 2024-09-02 18:32:28.836 WARNING EDCORE (Main): logical core 18 is not available for this process 2024-09-02 18:32:28.836 WARNING EDCORE (Main): logical core 19 is not available for this process 2024-09-02 18:32:28.836 WARNING EDCORE (Main): logical core 20 is not available for this process 2024-09-02 18:32:28.836 WARNING EDCORE (Main): logical core 21 is not available for this process 2024-09-02 18:32:28.836 WARNING EDCORE (Main): logical core 22 is not available for this process 2024-09-02 18:32:28.836 WARNING EDCORE (Main): logical core 23 is not available for this process so did you omit those 8 cores from DCS in Process lasso or similar? are they ecores?

no you can play with 8gb of ram and it does work but when it gets real busy not so good.. but it will run with just 8gb.. mindy like I said maybe not as well as with 32gb..

OK but when I went to run the trk file it said I needed those 2 packs. as for the warning backend there were multiples of those that was just one I highlited not just pointing that one particular ship out.. it could be a conflict with an older pack or similar?

The Only thing I can think of is that the standby memory is full and when you goto press F10 it just tanks the memory. I know you said you were only using half the memory but the standby memory could be full causing a crash.. there is this in the logs repeated many times: 2024-09-01 22:39:54.327 WARNING BACKENDCOMMON (16240): Need to reprocess [DDS] image '/textures/USS Samuel Chase _N_3.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format maybe an issue with your drivers? EDIT: I just tried to run your trk file and it says I need the mods WWII Weapons pack and Technics?? Do you use mods running that mission, it could be those maybe check and see if there is an updated mods pack for those 2..

Well I was using the OXRTK they also have one in the OpenXR Tools. I am unsure why they say they are not accurate but they are pretty close.. Yes I am not worried about the numbers as once I am set like this it just works for me and I like monitoring the spikes.. but setting it like this has given me hours upon kours or near lag free gaming even in the Pretense campaign.. you can also divide 1000/FPS to get Frametime.. I rarely get spikes just some wierd one from the game itself like if I press a certain button press sometimes can cause a spike but it is almost instantly.. F10 crashes could be a memory issue. if you made a thread and posted the log I can have a look dont want to clog this thread with that so if you can PM me your log.. I dont use VD as I guess I can not haha!! but I heard good things about it.. what kind of crashes do you get a black screen in the headset then game ctd's??

Well a basic understanding and this goes for any headset. is that in VR to keep it looking smooth and silky you need to maintain the Frametime and under for your desired HZ rate. this is what they are: 1. 60hz = 16.6ms 2. 72hz = 14.4ms 3. 90hz = 11.1ms Frametime, is basically how long it takes to process the Frame by the GPU. so if you go over the frametime the affect is stutter. So basically if you follow that guideline on any headset and your PC can maintain that Frametime or less and less is better to have some overhead the rest is all just tweaking the options in DCS to what you can and can not be able to do according to the frametime. And as you see the higher the HZ rate the less time it takes so @ 90Hz you need massive FPS to achieve good frametime.. I have been following this guideline and DCS is as smoth as it is going to get within the confines of my system. now I could share my settings but rather pointless as your PC is going to be different to some degree.. So if you have a potato PC and are trying to run 120hz good luck with that. I bet the highest end PC's might struggle with maintaining 120+ FPS in DCS in VR.. so you just have to experiment there is no magic setting.. If you set it all high and when you hit a busy scene your Frametimes will tank and then you will get stutter I see it all the time. best bet is too find a happy medium like 4-6 points under your desired Frametime. that way if the scene gets a bit busy you have some overhead.. If you play in VR you have to compromise or suffer with stutters.. Now that is not withstanding current issue with the last 2 patches. it has been known for along time alot of objects especially moving ones cause stutters.. another thing could still be happening is when you do get stutters check your memory and standby memory I am gonna say it might be pretty well spiked at it's limit especially if you have terrain on HIGH.. the simple thing at the top is to me the biggest thing people need to understand about VR.. I am not refering to the ones who do know so don't take that personal..

can you please post the DCS.logs nd sys specs and maybe a trk file?

post your logs if you please..

Hey LucShep, I had ran into a teething issue with the new PC and it turned out the OC needed more Voltage, I bumped it up to 1.330v it was then pretty solid stable. but that was just a bump in the road, the real issue is I did assign all the Procceses other then the ones that did not convert over it seems some processes can only stay on ALL cores, all the other Processes got assigned to the E-Cores and it seems to be working really well. I am going to need to do further testing but I had a jump off tangent and ran into a voltage issue I had to resolve. so now that I think I am stable again I can continue testing to see if keeping all the Processes on the E-Cores will be viable.. but so far so good. I am currently running DCS in VR mode and monitoring the Process Lasso Program and what the e cores are doing.. So far they seem to be doing very little which is great.. I just need to get into a 2-3 hour session in DCS and see what happens.. EDIT:: another thing I noticed is that the HyperThread core #3 seems to be more busy then the rest of the Cores, I wonder why? shouldn't the main core be set at more % usage then a hyper thread?

you can supply a Log File Please and then wait until you get back in the cockpit the % will probally spool back up as it is not as demanding in the Splash screen..

Well I am testing Win 10 Pro and it seems a tiny bit better in the MP so far. I was getting about 11.4-11.6ms in win 11 and now I am getting 10.4-10.6ms in MP. but now when running Process Lasso it does not specify P- and E-Cores, they are just labeled as cores.. Now it did seem about .2ms better when letting Windows handle the affinity. I am going to try it again without affinity running and just letting windows do its thing. I was expecting a little better and I guess this is about as good as it is going to get.. I had did a fresh install totally nuking both drives on my PC. So far not sure but I guess win 11 was ok just that win 10 is a bit smoother and lower Frametimes but not by much.. but I guess enough to make it 90FPS @ 90Hz with 80% Rez. Now I am sure if I lower the HZ rate it will be fine but at 60Hz it seems ok just feels funny..I am going to do some benchmarks now and see where they stand.. Will do more testing but it is getting late right now. will do a few more tests and then shut down.. Benchmarksran but only 2 and it looksto be real close with Winn 11 edging Win 10 but another test I ran was the win for Win 10 so you could fudge numbers but in this case for my quick and dirty test I would say Tie.. but Win 1 is PITN and I like win 10 GUI!!.. I will have to run some more tests with DCS.. here are 2 screenshots 1st one is win 10 w/12700K sys in specs just different OS. 2nd pic is win 10:

Yes I tried this it did not work.. I am in the Process of going back to Win 10 Pro.. lets keey fingers crossed Win 11 has been a disaster so far.. Hey In ProcessLasso window you may need to scroll right there is a column named "Application Named Claimed" in there you will see if it is a Windoes OS Process like so:

Well I had tried a MP Mission and ran into some high frametimes that were 20ms way to high for smooth gameplay in VR. I am unsure if it was the 1st PCore running at max percentage or just that it was a bit too busy ingame. I think I am going to try and put all the windows processes back on the E cores it seemed to have ran smoother then.. I will 1st try a Rez reduction back to 80% which will still be higher then the 60-70% I had gotten before.. I am unsure if it was the server but I think it was me and the resolution was too high.. Going to test @ 80% Rez and the windows OS Proc. on all cores..

Yes I have it all set where the windows operating system processes have access to all cores. makes perfect sense and it seemed I was able to get my Reverb G2 to 100% @ 60Hz which before I did this was at 70% rez.. So it was a good improvement over the stock way..