

Adam
Members-
Posts
226 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Adam
-
So just to clarify - FA18's have the disadvantage of not being able to use ECM - but the advantage of ECM not affecting them either? ... asking for a friend. :smilewink:
-
And to me that's the beauty of it.... giving "choice". We could always have the alternative - no early release and no choice. (or have the experience I've had with EA games - full release with bugs that never get fixed as they release their next game for another cash grab). I understand the frustrations, I would love to hear some news as well but I'm glad we at least have choice in this matter. ED have been transparent and given us a choice and I'm grateful for that.
-
And once released everyone will be wanting to know if the physics support this. :lol: That is epic! Thanks for posting!!!
-
Repeat function would be fantastic - but even as a work around as you've mentioned - have all coms go onto a kneeboard page that we can view previous coms like a log would be fantastic too. (Why not both). :smilewink:
-
I'm not sure if I misunderstand the question - but I can play back a track file, and see exactly what I saw when I was flying. Plus - if I choose, I can use the function keys to change the views from inside / outside the cockpit, flyby's, and so forth during that playback. The main thing I've learned is to save a copy of the original track file first. Playing back the track file is not read-only and any changes made are written to the track file. Speeding up the time in the track file can also corrupt it - so when I have a Trackfile i want kept - a copy goes into a vault that I never play directly from - I only load copies of that trackfile into DCS. (By Trackfile I'm assuming you mean DCS's track file, and not a tacview file - which are two very different things)?
-
I should add to this... SmoothTrack TrackIR alternative that allows you to use your smartphone's camera for OpenTrack. I haven't used it ingame yet (I already have TrackIR) but a mate of mine who hasn't got TrackIR just came across it and is going to give it a try.
-
A thread/place to list all the extra's you've got for DCS that have improved your experience (that may not be that well known about or would be handy for Newby's to come across to see all the extra handy tools available to them). Here's a list of things I've come across so far - and I'm keen to see others that I'm not aware of yet: PointCTRL - https://forums.eagle.ru/showthread.php?t=218861 VR Pointing utility. (I haven't had the pleasure of using this... yet). DCS Updater Utility https://forums.eagle.ru/showthread.php?t=160053 Utility to control multiple configurations (and builds) of DCS. TacView Handy tool for reviewing / after flight debriefing for seeing where mistakes were made and improvements can be done... https://www.tacview.net VoiceAttack Allows you to bind keystrokes to voice commands. (Worth mentioning here is the VoiceAttack profile by Bailey https://www.digitalcombatsimulator.com/en/files/3302954/ - many pre-set things that allow a huge variety of functions using Voice attack). (I use this in conjunction with a button on my HOTAS to activate it so it's not listening the whole time) ScratchPad A little 'notebook' like app that can be displayed/hidden that allows you to type in notes / coordinates, etc. Very handy in VR when you can't use real pen and paper for making notes - or for non-VR players who want to save the rainforest. :smilewink: SRS for DCS Integrates within the DCS game to allow transmission over the radio frequency you have installed. (Used on many servers) Overlord Bot Allows AWACS responses to radio communications. Things such as verbally saying "Colt 1 1 - Set Threat Radius to 50 miles", and then overlord will warn you when threats come within there. It can also understand more basic commands such as "Colt 1 1 - Request Bogey Dope", etc. Probably not so much for newby's to setup - I think it's quite involved - but I've experienced servers with this on, and it just ads to the immersion of the gameplay! (I believe it's used in conjunction with SRS). Just wondering what others have come across that I can add to my collection. :)
-
Oh - maybe that's it. No - I'm running the stable branch of all.
-
Thanks for the help. I appear to have something different. I have (icons from left to right) - Menu - Desktop - fps VR - Library - Home - Shopping - Reset standing Position - Speaker, and - Settings Going into settings gives me the same settings/menu option that I see if I right-click on SteamVR's icon in the system tray and choose settings. Going into Menu gives me Steam, Exist SteamVR and Exit VR. There's no icons there for Windows Mixed reality. :cry:
-
A couple to add to the list that I just found in the last few weeks and wish I had have known about earlier! ScratchPad (Ability to bring up a scratchpad and type down notes - kinda like a virtual interactive notebook). Especially handy in VR when the 'pen and paper' hack is more cumberson. VoiceAttack Ability to bind keystrokes to voicecommands. To be able to program things such as "Smoke On/Off", "Ground Crew" "Remove Wheel Chocks", (and many others). FPS VR Steam app that brings up a panel in VR that allows user to see performance information. Memory usage / GPU and CPU performance as well as the real / local time. (Handy to know when I'm playing too late!) ;-)
-
Sweet. Thanks for the link! I've set "motionReprojectionMode" : "auto", And will see how we go. Thanks!
-
Aaah - I wonder what's the bet that I've mapped the brightness nob to a POT on my HOTAS accidently and it was turned down and bumped slightly at that moment! Thanks so much - I'll check this out if it happens again!
-
Thanks. Unfortunately I have no idea how to find the WMR settings in the SteamVR dashboard. I've gone into the 'SteamVR room', and clicked on various buttons on the controller which have brought up various 'dashboards' and have been groping around using controllers to try and find WMR settings - but none have a mention to WMR. I have WMR for SteamVR installed in steam (or whatever it's called) - but don't know how to access it. Cheers! I've managed to find a file which references motionreprojection in Steam\Steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings The file contains: // Comment out or remove this line to use the SteamVR settings for controlling motion reprojection "motionReprojectionMode" : "disabled",Is it just a matter of commenting this out to switch it "On" to see improvements? ie - make it // Comment out or remove this line to use the SteamVR settings for controlling motion reprojection [b]//[/b] "motionReprojectionMode" : "disabled",
-
Is Motion reprojection the same thing as motion smoothing? I was unable to find anything regarding 'reprojection' in the steam settings. :-( To the O.P. I believe I've had a similar issue. My FPS's were showing 25 but it was stuttering when viewing fast objects at right angles wiz by from the cockpit. I ended up messing with a lot of settings to reduce the load on the GPU which fixed this. (I've got Pixel Density (which is found in DCS VR settings) running at 1.0, and Steam SuperSampling set to 100% now. I've got a 2080 with 64GB RAM and I am only getting 45fps when near the ground. I wonder if it's possible for the GPU or DCS to overwork while the GPU is still calculating higher FPS but the results are still stuttering?
-
Hi, The other night I had a couple of times where I had the left DDI in the EW page practising some BCM with a friend where the screen just went black. The DDI was still on 'day' - but it was as though the screen was turned off. I was just wondering if over-stressing the aircraft causes the left DDI to fail, and if this is a feature - or if there's something else dumb that I'm doing. (As the two times it occurred I had sudden aircraft movements at high speed that may have been overstressing)? (This is on the latest stable release). If it happens again I'll look at saving a track file (I didn't do it that night) but just wanted to check if it is something I'm doing wrong or a feature I'm not aware of?
-
Just wondering what the difference is, and what people have experienced? Improvement. Performance hits? Etc...
-
I have no idea - I've tried it and couldn't tell if it was a placebo effect or if there really was a difference. I'd love some clarification as well, but figure it'd get a greater chance of being answered in a dedicated thread. So... https://forums.eagle.ru/showthread.php?p=4475670#post4475670 ;)
-
Thanks speed! I've got a bit more tweaking to do to get a full understanding of what I can have - but strewth - what a difference! So glad there's people like you saying that you're achieving good results at 100% that kept me digging to find out why I was different! :thumbup:
-
Just thought I better add what I've just discovered in incase it's helpful elsewhere. I've been boosting PD / SS to try and bring more clarity - especially to the cockpit. I've recently been playing around with settings outside of DCS (in particular in WMR) and choosing quality over performance in some areas. (The main things I changed that I recall were changing performance to quality and 60hz to 90hz). To the point where things are much clearer now for me at 1.0PD / 100% SteamVR SS in the cockpit than they were with PD at 1.2!!!! I've got a lot more learning to do and a bit more verification - last minute success late at night when tired - but it seems that my problems with clarity were external to DCS, and that supersampling was a heavy handed approach to correct which was not required. It may be that increasing PD increases clarity even more - but at present the improvement I'm seeing is so much better than what I was experiencing that I'd be willing to say no supersampling is quite playable and very readable - if the other settings are done correctly! (I'm just wondering how much more improvement I can get by tweaking the other settings now). When I have time I'll try and relist my specs and settings compared to what I've posted above to give an indication.
-
Major Breakthrough - and confirmation of speed-of-heat's result! I originally replied with... That is now no longer applicable! I've been playing around with some settings outside of DCS. In particular in WMR I recall changing from performance to quality, and at the same time from 60hz to 90hz. I don't know what I've done exactly completely - and which setting I needed and which I don't (I need to go back and relook) - but the important thing is I can now read things so much clearer in DCS!!!! Not only that - I can read it clear at PD 1.0 / 100% SS!!!! :cheer3nc: I'm guessing I was doing something wrong (dumb!) that was causing bad quality/readability of the text on the DDI's and labels in the cockpit outside of DCS and some how supersampling was combating that a little. As per speed-of-heat.. it 'kinda worked'. This gave me the wrong impression that SS was the answer to my problems. The improvement I've seen makes all the numbers clearly readable to me now at 1.0PD / 100% SS! I've still got more work to do with the tweaking - but just wanted to post here that my previous reference to super-sampling being required for the HP Reverb may be very misleading. :doh:
-
For me, after making a few changes and reducing the PD/SS - I've got GPU mostly green, and yellow on occasion. Seems that my processor is doing fine though - it hasn't been maxed out at all from what I can tell (except when initially loading) I'm just starting to work through what all the settings mean (I'm a noob with all this stuff, and the phrase 'all the gear and no idea' is highly applicable - I'm on a steep learning curve). The main question was just if there was a difference between PD and SS which there obviously isn't - so I'll use steam. (Gives more control over it in the end - finer adjustments). From what I can tell there's a significant difference between 100% and 140% - but after that, the improvements are difficult to see while the performance hit continues to take it's toll... Now that I've figured out that, I'll move onto trying to understand the next lot of settings. I'm also wondering if I might be expecting too much from DCS and VR at this time. (As mentioned, zero previous experience with VR and straight into this) - I was probably thinking that pictures would be a little sharper than what they are. I guess I should have tried a rift or something with less resolution first to appreciate what I've got. (Either that, or I'm doing something very dumb and a single setting somewhere I need to change which is probably a good possibility too). Specs as requested: 2080 Super i7-10700K @3.80Ghz 64GB RAM 2 x 2TB PCIe SSD HP Reverb Pro At this stage I'm managing to get 60fps for most of the time, and it can get as low as 30fps at some times (using Steam FPS VR). When it gets low, it's the GPU that's in the orange, not the CPU. I've managed to get rid of the stepping / ghosting and most of the playing I've done doesn't seem to get me any clearer cockpit but seems to chop into my FPS's a lot. This is currently with the following settings NVidia Control Panel: Image Sharpening - Off Anisotropic Filtering:16x Antialasing FXAA - Use Global Setting (Off) Antialasing Gamma Correction - Use Global Setting (Off) Antialasing Mode - Use Global Setting (App Controlled) Antialasing Setting - Use Global Setting (App Controlled) CUDA - GPU's - Use Global Setting (All) Low Latency Mode - Use Global Setting (Off) Max Frame Rate - Use Global Setting (Off) MFAA - Use Global Setting (Off) OpenGL Rendering GPU - Use Global Setting (Auto-Select) Power Management - Perfer Max Performance Shader Cache - Use Global Setting (On) Texture Filtering - Anisotropic Sampling Optimization - On Texture Filtering - Negative LOD Bias - Clamp Texture Filtering - Quality - (I've played with both high performance and High Quality) Texture Filtering - Trilinear Optimization - Use Global Setting (On) Threaded Optimisation - Use Global Setting (Auto) Tripple Buffering - Use Global Setting (Off) Vertical Sync - - Use Global Setting (Use 3D Application Setting) Virtual Reality Pre-Rendered Frames - Use global setting (1) Virtual Reality - Variable Rate Super Sampling - Adaptive Mixed Reality Portal Experience Option - Optimize for Performance Resolution - Automatic Upscaling (best performance) Frame Rate - 60Hz SteamVR Render Resolution - Custom Resolution Per Eye - 2564x2512 (136%) Advanced Supersampling Filtering - Off Overlay Render Quality - Low Motion Smoothing - Enabled for DCS Use Legacy Projection Mode - Off DCS Textures - High Terrain Textures - High Civ. Traffic - Off Water - Medium Visib Range - High Heat Blur - Off Shaddows - Off Resolution - 1280x768 (lowest it will go) Aspect Ratio - 1.66666 Monitors - 1 Res of Cockpit Display: 1024 MSAA - Off Dept of Field - Off Lens Effect - None Motion Blur - OFF SSAA - OFF SSLR - OFF Clutter/Grass - 750 Trees Visibilty - 90% Preload Radius - 100,000 Chimney Smoke Density - 0 Gamma - 2.2 Anisotropic Filtering - 16x Terrian Object Shaddows - Default Cockpit Global Illumination - OFF Messages font scale - 1 Scale GUI - 1 Rain - Off VSync - Off Full Screen - Checked VR Pixel Density - 1.0 Bloom Effect - Off MSAA Mask Size - 0.53 There is probably stuff there that could be turned on that would make nicer images with little performance cost - I'm still working my way through what it all means and what is and isn't good change for little performance hit. PD / SS was my first thing to get my head around on what appears to be a long journey. Thanks to all who have replied and helped!
-
Thanks. I actually had anisotropic filtering turned off in an attempt to reduce load on the GPU. I'll try going back and resetting what I've done and try again. Thanks for the suggestion. (Texture filtering was set to performance instead of quality) :thumbup:
-
Hopefully you don't mind me chiming in here. I'm having the opposite to you and would love some insight. With PD at 1.0 and SS at 100% with my reverb - the display in my cockpit (and definitely my DDI's) are not readable. I struggle to read anything until I up the SS or PD. PD of 1.2 is acceptable with reading clarity (although still not great). PD of 1.0 makes it impossible to read numbers such as Lat/Long (especially 8 and 0's). Even the number pad on the center console - the numbers are blurry like I'm wearing someone's glasses - I can make out what they are - but only because I know what they should be. I know you say that SS should make things smoother - but in my instance it makes things clearer (but at the cost of being jerkier, not smoother) Running HP Reverb on a 2080S with cockpit texture set to 1080p, and MSAA off, SSAA off. Not sure why my mileage is varying so much compared to yours.
-
64GB Ram, 2080 Super, i7 10700K @ 3.8GHz. I haven't overclocked anything yet but I was expecting to be able to read what was on the screen without having to stretch forward and squint at the blur. That's why I was wondering if I'm doing something wrong with my settings, whether there's difference between SS and PD (which there isn't apparently) - or whether it's just to be expected. I'm a complete VR noob - have no idea on expectations, what's reasonable, etc - so it's not a complaint - just looking for clarification. So far - I'm guessing what I have is to be expected, and I need to put up with the fuzzy cockpit and DDI screen to have a smooth experience.
-
Aah - I see. So no benefit at all using one over the other - just be aware of the different in measurements to not mistakenly counter one for the other. Thanks!