dukman83

Dear ED team, At the risk of bringing up an unpopular/well-flogged topic to light, I am hoping to re-life (probably every pilot's wish) of re-living that awesome last mission they flew. I realise that the track file system is horribly broken and left for dead because it would require a significant code re-write to make it functional. BUT if it were recreated as an add-on, purchasable module, I would be willing to bet that most pilots, would be happy to pay for it. Another really good complementary feature would be the ability to replay previous missions with a greater level of control for the purpose of creating that amazing cinematic. Having something similar to what Tacview offers that incorporates an improved fast-forward, rewind, track, event-based navigation etc. would be a brilliant addition and revamp of the replay model. I think that this would have incredible potential not only for content creators, but also for post-game analysts, and would better advertise the awesomeness of DCS. Many thanks for reading and considering!

Dear ED team, I would love to add to the wish list a fully working Westland's Sea King Mk. 50A and/or B model that was used by the Royal Australian Navy. Having worked on this aircraft for a majority of my career, and having flown it in a simulator as well as IRL, I would love to have this amazing utility helicopter added to the DCS toolset. Warm regards, and many thanks in advance.

Dude... 7 months into the module release and this is still an issue. Can you please fix it? I get that you may not be able to replicate it, but please just give us the benefit of the doubt and implement the IHADSS height adjustment feature. It's pretty frustrating to be asked "are you wearing your headset correctly" over and over. The problem exists only with the Apache module. It is real, albeit not for everyone. Please don't assume we're idiots and help us out.

Hi BIGNEWY, Thank you for looking further into this. Unfortunately I am not familiar with the crosseye tool, but I am pretty confident that my IPD is set to 63. Will have to confirm when I am home in a couple of days, but I am reasonably sure that it is set to that because I measured my IPD a while back. Thanks and kind regards

Dear BIGNEWY and ED team, I would like to revive the topic listed here regarding the IHADSS sitting too high in VR with the AH-64D. While the linked topic is specific to George AI's position on the screen, the issue that I am finding extant is the height of the IHADSS display relative to the centreline of the eye. Kayos has illustrated this well with his screenshot. I took a few photos from inside my VR headset in my naturally seated position (seated position reset in Steam VR) to further demonstrate this. I apologise for the poor image quality, it was almost impossible to take the photos, but I believe that it paints the narrative. As it can be seen, the centreline of the eye is directly inline with the turn and slip indicator/field of regard box, the crosshair sits along the canopy crossbeam, the heading tape is somewhere in another galaxy, and George AI is in the back of my eye socket. Slight exaggeration aside, I find it problematic. I have a single monitor, use HP Reverb 2, and am not exporting to any other display, so I don't see the multi-monitor patch helping in my case. Adjusting the angle by significantly tilting the headset uncomfortably (and unsustainably) downwards with both hands so far that the headset has to sit away from my face for it to be able to sit correctly in the screen seems to adjust the IHADSS to the centre. Additionally, I question if tilting the headset downwards is a solution, as I am not sure how this affects the aspect/perspective and picture accuracy with respect to the game and boresight. My head and face are regulation size, if that helps This now begs the question... is the IHADSS too high or is the picture at an incorrect angle? I would be very grateful if there is no fix to this at this point (and looking around various forums there doesn't seem to be) that some sort of personal adjustment (height or angle?) via the menu be added to the backlog for implementation. Many thanks, in advance.

Wow, I am loving this conversation, thanks guys, there's a lot of valuable information there! I think that as advised, it's best that I do start at the lowest settings with a closely comparable hardware setup to mine (which there seem to be a few of in this thread) to get a good baseline... Same settings, same map/mission and compare our results before making a determination on the best way forward. Thanks again to all of you for engaging in this discussion!

Hi stuartaston, I definitely haven't installed Skype on this recent installation of Windows 10 (certainly not manually anyways). Looking through my Task Manager I did not see it running as a process either.

Thanks guys! I will reduce everything to pretty much barebones as suggested to see if I can get the 90/45 FPS and sub-11ms frametime. I will kill as many resource hogging tasks as possible make the changes a couple at a time. I will also re-enable hyper threading as suggested. @Gunnars Driver I agree with the shaders mod, it's a lot of work for minimal gain which needs to be redone with each update. I had a bit of a run with the game last night (I spent all this time lowering settings and chasing FPS and frametiems without actually checking what the game looks like when I put on the goggles) and the results were pretty disappointing, I have to say... There was a lot of flickering in the picture, text looked like it was tearing as I was looking at it and moving my head even slowly and I noticed that if I tilt my head (not turn but tilt to either side) the clouds would deform/change shape?? Thank you for offering your time to help via Discord or Skype, that's amazing! I am free this weekend and if you'd be happy to, we can arrange a time to discuss? Thanks again!

Thanks @Gunnars Driver! I reverted to 2.5.5 a few posts ago, I believe it has made significant improvement to my FPS and frametime in doing just that alone. For info, this is what I have done so far: Implement shdwp’s recommendations: •Reduce visibility range to Medium - (post #2) •Set shadows to Mid - (post #2) •Set Terrain object shadows - (post #2) Implement stuartaston’s recommendations: •Copy stuartson’s personal settings - (post #4) •Disable hyper threading in BIOS - (post #4) •Revert to 2.5.5 - (post #4) •Set processor affinity to physical cores (6 and 7 as per SkateZilla’s post #1 using the URL stuartaston provided in abovementioned post) - (post #4) Implement Gunnars Driver’s recommendations: •Reduce both global and DCS specific VRSS to 100% (post #9) •Run VRmark (using URL Gunnars Driver’s provided) – (post #17) •Reverted CPU affinity to all cores Still to do: Implement Gunnars Driver’s recommendations: •Benchmark CPU/GPU/RAM – looking for a good free benchmarking tool (post #9) •Reduce settings until reaching a playable game (post #9) •Max out pre-load radius? (post #9) •Reducing the tree visibility, clutter grass to a quite low value, terrain textures to low, lower visibility range to lower than ultra, shadows to ”flat”, smoke and chimney to lowest and anisotropic filtering to off or 2x. – (post #17) A few more questions: Would you recommend playing with affinity mask via the game's lua file seeing as Project Lasso had no measurable impact? Are you suggesting that I should be reaching something close to 90fps during gameplay? How do you enable reprojection - is it automatic? I haven't been able to enable it using Thud's VR4DCS.

Thanks jalfrezi, that seems to be consistent with the results I got... Does this mean that this setup is as much I can get out of my system?

Thanks for the advice guys. I used Project Lasso to set the core affinity to 1, 3, 5, and 7 and found no noticeable difference between affinity set to all cores. Out of curiosity I then changed it to 0,2,4,6 and found the same... Should there have been at least some difference one way or the other??

Hi mate, thanks for the info! Out of curiosity, what is the third core required for by DCS? I understand by previous posts that one core is for the game and the other for the sound. Also, I did a bit of googling and couldn't find exactly which cores are physical and which are logical for my specific CPU. If it is safe to assume that generally all multi-core CPUs structured from core 0->n where the first core is physical and the next is logical, would you recommend DCS to be set to cores 3, 5 and 7 in order to utilise three physical cores?

Thanks guys! @stuartaston, thanks for clarifying! @Gunnars Driver, did you want the specific screenshot of Task Manager with the game running as well as the Project Lasso I provided earlier? Until this latest tweak I have not messed with PL in any way. In fact, no changes have been made between my last post and this response. The most recent tweak (done just before this post) was the change of priority of DCS.exe to “Realtime”. I noticed that there was some improvement following that change. Please see the attached screenshot of the results. The next thing I tried was to set the CPU affinity to CPU 6 and 7 as per stuartaston’s recommendation in post #4. This did not appear to be helpful – in fact, somewhat worse? I reverted to Priority "Realtime" and affinity to all CPUs. Please see the attached second screenshot appropriately titled. Another thing to note is (I probably haven’t mentioned this earlier) that this is a fresh install of DCS. As part of my original troubleshooting I totally uninstalled it and re-downloaded it. Any further thoughts/recommendations? In the meantime, I will keep going down the list of TO-DOs unless you have any further advice?

Hi guys, Thank you all very for your input, I really appreciate each and every one of your advice! Here’s a quick summary of things done so far under your collective guidance: Implement shdwp’s recommendations: •Reduce visibility range to Medium - (post #2) •Set shadows to Mid - (post #2) •Set Terrain object shadows - (post #2) Implement stuartaston’s recommendations: •Copy stuartson’s personal settings - (post #4) •Disable hyper threading in BIOS - (post #4) •Revert to 2.5.5 - (post #4) Implement Gunnars Driver’s recommendations: •Reduce both global and DCS specific VRSS to 100% (post #9) Still to do: Implement stuartaston's recommendations: •Set processor affinity to physical cores (6 and 7 as per SkateZilla’s post #1 using the URL stuartaston provided in abovementioned post) - (post #4) Implement Gunnars Driver’s recommendations: •Benchmark CPU/GPU/RAM – looking for a good free benchmarking tool (post #9) •Reduce settings until reaching a playable game (post #9) •Max out pre-load radius? (post #9) •Run VRmark (using URL Gunnars Driver’s provided) – (post #17) •Reducing the tree visibility, clutter grass to a quite low value, terrain textures to low, lower visibility range to lower than ultra, shadows to ”flat”, smoke and chimney to lowest and anisotropic filtering to off or 2x. – (post #17) @stuartaston, I do use more than one m.2 drive. I use one for my System and DCS is installed on another one. Does the pagefile still come into effect? Thanks for the info on “Static1”, good to know! Please see the attached fpsVR following revert to 2.5.5 and Task Manager showing startup and services whilst DCS is running as well as a few other things which could be of interest including VRmark results as per Gunnar’s Driver’s recommendation. Looking at the results, it looks as though there is a significant improvement following the most recent changes which were the reduction of Global VRSS to 100% and reverting to DCS 2.5.5. What is the collective opinion on these results? It is significantly better, but is it where it could be as far as my rig setup in comparison to other PC setups? I will continue to work my way down the list of things remaining to do as per your suggestions and will report as soon as possible! Thank you all again for your help!

Hi stuartson and The_Nephilim stuartson, Thanks very much for getting back to me so quickly and for the detailed explanation! I am running a Samsung 970 EVO Plus 1TB M.2 NVMe SSD. I am not familiar with page file swapping, I'm sorry... What is that? Please see the attached screenshot following disabling hyper threading and the task manager in-game with running processes. It looks worse to me...? I also noticed a comment "Static1" on the top middle of my screen after matching your settings the first time - does that mean anything to you? I will also have a detailed read on the CPU affinity link you sent first thing tomorrow morning. The_Nephilim, there is no Asus AURA rgb lightning service running in task manager. Thanks again guys!