FragBum

I get it I lost 1 activation when I elected to just reformat my HDD due to hardware issue, didn't have much choice but seriously loosing activation's because of bios changes when trouble shooting hardware issues is nonsense.

All the maps have slightly different CPU/GPU usage so results will vary between maps and the modules you use and situation. :)

There is a trap when adjusting gamma and that is to make sure you do not look through a canopy just clear air other wise you will be compensating the any glare or other visual effect of the canopy.

It is so difficult to try and actually explain what VR is like you kinda just have to take the plunge. :thumbup: I'm sure we could jump on a server and I could take you for a for a spin in the Gazelle. :D

True that. :thumbup:

Huh!

Turtles all the way down,.. :D Still and all it's lens distortion clearly, I mean I get it on my 8 to 12mm FF all the time. :thumbup:

As an observation MP seems to impact more on CPU then GPU although MP will use more GPU VRAM and more system RAM. As for PD vs MSAA, it seems MSAA is post PD, that is for a given amount of MSAA the PD amount delta ramps up GPU and CPU usage hugely. Just have a look at taskmanager as you change the PD value. Personally I prefer MSAA processing with a small amount of PD but that is very much a personal preference and very dependent on hardware, if I can I also add a bit of AF even *2 or * 4 even better but you can work that out. Lower clutter and visible range and textures. TBH your choice is pretty much made, Rift doubly so if your on standalone DCS version. Also follow Harlikwin 's guide, it's a matter of what eye candy you can accept for FPS/smoothness. I'm not sure but maybe the last patch changed frame rate aka processing overhead but I had some other hardware issue to work sort out at the same time though. Bah Humbug. :cry: YMMV :)

Go away it's lens distortion. :P :D

Both the 8600K and 9600K are the same price here, given that wouldn't the 9600K be a better buy?

Whilst ED have been tweaking DCS World memory usage over the last year or so I have seen memory usage drop from mid 20GB down to about 6GB for a simple mission, I regularly see 16GB usage on MP servers. Despite having 64GB installed (some of that will come out for another build) DCS will get away with 16GB take that to 32GB if you regularly do big MP missions or indeed develop missions. At no time have I seen my virtual memory being used or recently DCS using much more than 16GB. VRAM usually around 6 to 7GB on SP mission but will go up to just over 10GB usage on server, again if your GPU has only 8GB I don't know what the effect would be, would you really notice I don't know. I'm in the give your system 32GB camp mainly because when I do other stuff like editing RAWs or video or audio, Windows just works better not saying it wont work with say 16GB. One thing is DCS (I guess most other software too) will benefit form faster RAM and higher CPU clock. Whilst SSD is great I really don't see any disk activity when running DCS, that may be different with 16GB and a GPU with 8GB or less VRAM, but once your mission is loaded AFAIK it's the holy trinity of CPU Clock, RAM speed and GPU horse power especially for VR. YMMV. :D

Or is it something to do with having static FA 18 on the tarmac, I have heard others say there is some FPS weirdness associated with static objects. Perhaps try creating a simple mission and see if you have the same issue.

And in that vain I have managed to fall through an aircraft carrier, through the ocean, through the blackness and into space all that whilst trying to land inside an open portal on an aircraft carrier in a Gazelle. :D

Long story short I upgraded my GPU to a shinny new 2080Ti apart from the somewhat smaller form factor compared to my 1080Ti I didn't give it much thought all this whilst going through some really odd image issues in VR and that's another story from the 2.5.4.x changes. One thing I noticed from the time I installed the 2080Ti is that the back plane got very hot whilst running DCS 60+ C. Running old school settings netted me slightly more eye candy but still same ole same ole FPS, alright so I did some tweaking and experimenting with settings and found my rig could mostly do 90FPS in Rift NTTR and Caucasus even PG and Normandy but not as consistent with some interesting observations more latter. So what I observe happening is for example on the Caucasus map CPU would sit at about 17% GPU about 50% 45FPS then the CPU would ramp up to 25% and GPU to 80% and voila 90FPS. This meant GPU back plane temps rose a few more degrees as my previous 1080Ti GPU ported some of the heat out the back the new 2080Ti does not (all the 3 fan designs look much the muchness here) and increases the temperature inside the case. Anyone else think not porting at least some of the heat out the back is a bad idea? The crashing was consistent and brutal, BSOD and a restart after a few of these and with a fairly hot day yesterday the system crashed but this time when I fired up taskmanager I had 8GB of RAM missing I'm not sure how many starforce points I racked up because of "Total System Memory" changes. :cry: Platform is X99 so 4 memory slots either side of the CPU all close to the GPU backplane and getting hotter than before. Front RAM set about 50C rear RAM set about 55C. The temporary fix, drop RAM speed from 2400 to 2200 so far stable but long term I need to revise the system cooling especially the GPU and RAM. So if you upgraded recently and I can't say if the same applies to other 20 series GPUs it might be worth checking temps etc if your getting seemingly random crashes. As a side note dropping the RAM speed noticeably affected performance,... such is life. :) HTH. :thumbup:

Nor have I been able to, although for simple free flight testing you should be able to get mostly 90FPS on NTTR maybe on Caucasus and less so on PG and on Normandy, if a Swallow* fart$ in the Forrest,.. 45FPS. :) From here it's CPU clock and memory speed and VR improvements. :cry: *European Swallow.

Pipped to the post. :thumbup:

Here you go Damcopter from Flight Model Again V2 thread

Interesting thanks for sharing. :) The reason I went down the simpit route was to get away from wrist killer table top joysticks and attempt to make it "more real" in VR, however I think I'd miss the "feel" of hands on controls. Mmmm, just when did they say the holodeck is coming out? :D

Indeed exciting times. Just a heads up I remember when I first got Rift I took the Huey out and OMG, well then I took the Gazelle out and after about 10 minutes I had to put it down and have a break or it wasn't gonna end pretty. Good news a few more sessions perfect :thumbup: But then you probably haven't seen how I miss the ground, well mostly. :D

Are you referring to Damcopter?? patiently waiting to see updates. :thumbup: :D

Wait until you have your first crash in VR Bahahaha :music_whistling::D

Settings Here and PD=1.2 With PD 1.3 PG and Normandy wont do 90FPS at least not with my testing. It's a slight compromise but not so bad as I thought it would be, don't get me wrong we need much improved VR support and since 2.5.4 my graphics have been very odd. I've been mainly tinkering with settings just to see what can be done. DCS is very much CPU bound ATM, I can use the FPS indicator kinda like a compass even on the other side of a mountain range when I point the heli at Las vegas 45FPS point any where else 90FPS I visually can't see las Vegas it's behind virtual rock. In the other maps, PG for example this effect is more pronounced and sometimes there doesn't seem to be an obvious reason for the FPS drop but might explain "apparently random" FPS drops. Anyway I see we have another update I best check whats broken and whats fixed on this one and how many times it's gona crash. :cry:

Yeah they all grow on you as you learn.

Actually 90FPS is doable with Rift at least, mostly, and yes I think it has something to do with rendering objects way to far out or simply not in view e.g. blocked out by mountains etc.

I think it's more a case that DCS IPD should be called maybe "World Scale" at least changing the DCS IPD value changes the DCS world scale so your perceived view port is either closer or further away from "DCS World" view port. Kinda like stepping back from a window or moving closer to a window. I would assume simply enabling it and keying in the IPD measured in your HMD setup would be a 1:1 same as disabling it should also default to 1:1 HTH.