RuskyV

If you late activate units in the mission editor they should then spawn with hot engines. The sooner an option gets added to the editor to warm engines the better. With path finding being so broken and ground units generally causing big FPS issues (especially in multiplayer) moving units around becomes less viable. Which ironically sort of nullifies the point in having a fancy FLIR model.

Why not add an audio click for every 0.5g steps? it doesn’t have to be anything obnoxious just some sort of audio feedback that can determine how long it was pressed.

I don’t have a track file as it was huge but I’ve seen something similar last night when I was on our server, I had created a mark point using the HMD and then slewing over the target to refine. I tried to MSEL on the mark point to make it active, having had no luck getting it to work I selected mk point 26 under STER button. (Probably user error). However when trying to get the TGP to look at the mark point I noticed that it was off by a few hundred meters or so, I CZed the pod to remove any slew errors but it continued to point further west than the mark point. It’s worth noting that I had done a stored heading alignment not a full alignment (Persian Gulf), I’m aware it’s not directly related to the error you see but it could be linked to an INS related issue..

Try this. DCS PD to 0.5 (you will get the headset to re render this using the OTT) Cap DCS at 45FPS using the autoexec (don’t use any Nvida frame capping) Oculus (software) render resolution to default (I see you have it set to x1.3, don’t set the SuperSampling here) Oculus tray tool Super Sampling to 1.4 or higher, (I use 1.6 anything above this can introduce stuttering with the oculus software) Oculus tray tool ASW mode 30hz ( oddly I found if you set higher it can actually cap the FPS lower in DCS when 45FPS is forced in the autoexec) Additionally try. Terrain Texture resolution to Medium (this affects 3d objects only) Water quality to medium or low (personally I set to low as I don’t fly any of the navy stuff that much) DCS AA to x4 (the default setting) Shadows to medium. (this affects the shadow resolution in cockpit) Cockpit display resolution to either 1024 or 512, just don’t use every frame Disable motion blur. Disable v-sync in the Nvidia control panel, and make sure you have power set to performance mode if you are not using game by game profiles. hope this helps you

This is how it feels to me but I’m not qualified to say it’s right or wrong so I’m treading a little carefully, I’ve also noticed the same tendency in extreme cases of +g, maybe you see the same? I can see how this would be more prominent on take off as you have full fuel onboard, but when landing shouldn’t the behaviour be slightly less based on a lighter fuel load? I know the tank cross feed is controlled automatically balancing out fuel, however under a certain weight is there any manual intervention needed? I can’t remember where I read it but somewhere in a manual it said there might be times where this might need to be adjusted manually. just looking to expand my understanding.

The first observation I have noticed a short but strong pull up will create a small oscillation where by the jet seems to then look to stabilise (understanding it looks to maintain 1g) this drags the FPM back down ever so slightly after the initial increase in AOA from pitching up. The second observation Is regarding pitch during take off and landing phase’s where you pull to hold a set pitch attitude, it seem in both take off and landing cases I often find I’m holding quite a bit of back pressure to initially rotate or aero brake. The behaviour gives the impression the jet is sucking to the ground and makes balancing the jet in these transition phases of flight a bit of a "work out". I have built up a fair bit of time in the viper module so I’m coming at this from a more seasoned prospective, however willing to still learn.

Brilliant thanks for clarifying Frederf

Do you TMS down after locking and bore sighting the mavericks? It’s this step in the process that I’m not sure about. Seems odd to have both maverick’s looked and then just taxi off.

I did have a cross wind it was 180/09 and was heading 290 but it was +3 deg when switching to GS which doesn’t make sense. I'll double check to be sure first

As the title says when switching between these two modes a few times shows around a 2-3 deg heading change. possibly a small bug?

Thanks, I’ll give it a shot

Can anyone tell me if there is a way i can turn off the VR background and just have it black?

Hi jurinko, I think it’s more about working to a solution rather than a fix, looks like it’s a known issue now so hopefully we will see some improvements in coming updates.

My pleasure, glad it’s getting looked at

This a big part of the issue, textures are taking up so much memory now even a high end system costing thousands is still no better off. No matter how much memory you have it gets eaten up. You can’t keep adding textures and triangles and not have a way to clear down memory, It’s a diminishing return on performance. What’s the official line on this, Bug? Bad code? No standardised textures sizes for modules?

When starting DCS and going straight to the encyclopaedia, flicking left to right using the arrow keys while looking through the 3D models starts to eat up memory pretty quickly. -Most noticeable is the Tomcat by Heatblur, flicking left to right on both the A and B models while loading in their liveries, just eats the memory up to the point all of my 32gb of memory hits 100%. Its the same with the Viggen. Other 3D models especially the aircraft have the biggest impact. The really odd thing is once its hit 100% memory DCS doesn't release the memory and it will sit at that percentage when exiting the encyclopaedia. This brings the simulation nearly to a crawl so loading the editor or trying to fly a mission gives horrendous performance. Its easy to repeat by opening the Task Manager and setting it to "always on top" then start flicking through the 3D models, once the memory tops out the only way to lower it is to quit DCS, which will then sit in the task manager until it finally quits about a minute later. Could the similar issue be causing part of the stuttering people see in multiplayer when people are connecting and changing liveries? dose this force all clients to use up memory when ever a livery is selected and comes into the players view? What could be happening here?? dcs.log

It gets worse, try narrowing the azimuth without any DBS modes and pan the cursor. You can literally drag the image all over radar screen.

In theory by focusing all the radar energy into a smaller scan volume you should be able to detect a target a little further out. The radar is updating a very small area so should brute force the radar into picking up contacts bypassing filters built into the radar that would normally disregard a contact. Others can fill in the details.

ED’s statement is correct, chuck’s guide has it flipped. When using IFF it will tell you what mode is being used in the bottom left of the FCR, as for LOS also scanning entire radar volume I’d have to check as i nearly never use it.

Your better off removing all the DL contacts from the radar using the filler and TMS right to IFF scan. Cross reference radar contacts under the ghost cursor in the HSD, any DL contact that is then picked up by your own radar will go solid colour. People often get confused with the DL overlay thinking that the radar is automatically classifying contacts and everything shown is lockable. Remove the ambiguity

See my reply in this post, it’s more than likely due to temperature.

Check your GPU temperature make sure it’s not hitting 85’c what tends to happen after is the GPU will start to under clock. This happens to help cool the card, for what ever reason this happens before the fans ever ramp. Use a program like nvtune and manually override the fan and set it to 90% or even 100%. It will be a lot more noisy but the fan will take care of the heat far better than the under clocking. From memory I have never seen the fan ramp more than 45% in nvtune even after hitting above 85’c might also be worth ramping the CPU fan if you can, similar behaviour is also used for intel CPUs now lithography and TDP are so much smaller, temperatures become an even bigger factor.

Ideas don’t go un noticed but you need to provide evidence, facts and figures build accurate simulations not guess work and approximation. Grab the evidence and track files from DCS and show where you think the performance needs adjusting.

Nope, you don’t have to have it running in the background you can close it if you are not running any profiles.

This hasn’t been fixed with the latest patch 2.7.16.28157. Also noticing when using any of the narrower azimuth settings, when panning the cursor left to right the image under cursor gets dragged around the screen until it refreshes. This is easy to produce, enter GM set azimuth and pan the cursor…