JimmyWA

I guess I should have added that I’m running solely in VR, which adds another level of complexity, but my main point is that I was surprised that DCS uses the pagefile even when there is physical memory available. It’s also interesting to see that even with 32 gb of RAM, it still uses the pagefile.

I've discovered that your RAM can be one of the main reasons DCS can have performance issues. I've been running 2.5 using VR for a while now, and have tried everything possible to boost performance. I found that overclocking my CPU to 4 ghz helped, and overclocking my memory from the base 2200 to 3200 finally stopped the annoying flashes I was getting. But, with the textures and viewing distance set on high, I would still get stutters. My CPU usage doesn't get above approximately 35% and my graphics card stays at around 50% when flying around the Caucuses with everything set on high, in a heavy mission. My total memory usage with DCS running in the same mission was shown as being only 12 Gb of my 16Gb. I decided to install an extra 16 Gb of the exact same memory to see if having more actual physical memory would help, and I also reduced my pagefile to 4 Gb in the hope that maybe it had got fragmented, and by resizing it, might help it performance wise. Unfortunately I couldn't overclock the 32 Gb no matter what I tried, and my performance went back to being below average with the flashing taking place. I then removed the extra 16 Gb, loaded up DCS, went to fly in a mission, and DCS crashed out to the desktop. I tried a number of times, before I remembered I'd reduced the size of the pagefile to 4 Gb. But, Task Manager told me I was only using 12 GB of physical memory, so with 4 Gb of physical memory still available, why was DCS also using the pagefile? It appears that DCS is using the pagefile as soon as I start flying in a mission! You would think my physical memory would be maxed out before this. I set the pagefile back to system managed, and I could fly in DCS once more. Luckily my windows pagefile sits on an SD drive - but it is still a performance hit. So the lesson I would like to share, is that if you just have 16 Gb of ram, there is a good chance that as soon as you start flying, your system is using your pagefile. If this isn't on an SD drive, then your performance is going to suffer. This is different from having DCS installed on a separate SDD. If you don't have fast memory, your performance is going to suffer - even if you have a great graphics card and a fast CPU. If you have a good CPU, good graphics card and 32 Gb of fast RAM - DDR4 running above 3200 mhz, then you should have good performance. It would appear that fast memory is much more important than multi threading in providing better performance.

I've just discovered that since the latest update, doing a cold autostart now sets the radar to LTWS by default. I'm sure this is going to cause a lot of problems with other unsuspecting simmers who aren't aware of this change - and I've seen other posts about it now. I follow the change logs closely, and watch the tutorial videos but this change was not mentioned. It also negates all the existing tutorials on the F-18 radar pre LTWS. I also asked on Teamspeak while in MP if other flyers were having trouble unlocking a target when in LTWS and a large number said they were - and yes I've pressed reset and tried everything else when it happens.

Here is the track file. Interestingly, the SA page shows the enemy MIG as a friendly (which it didn't when online - it showed up as a diamond not the square shown here) and after I shoot it, the replay then sets it to hostile. When I turn the radar off in the replay the tanker radar lock unlocks - but that isn't what happened online. It stayed locked. And it seems the track file is too large too upload.

Unable to Unlock Hi, I've only been flying Multiplayer the last week, but been flying the Hornet since it's release. I've never had this issue of being unable to unlock a target in single player, flying against multiple A2A targets. In Multiplayer, I've found a number of times I've been unable to unlock my target! This is Through the Inferno MP (OCG Australia). I'm always up to date with patches. What happens is I take AIM9x on my wing tips, AIM120s x 6, and 2 AGM66s. I've turned my datalink and IFF on. I'm selecting the target by setting the radar MDI as the main screen, then putting the cursor over the target, and doing sensor depress to lock them up. The first time I lock up an enemy or friendly, I can unlock. Then I fire a couple of AIM120s at the enemy, then move onto another target. Then (it can seem to be quite random) when I lock up, I can't unlock. This seems to happen after I've been in the server for over 30 minutes or so, or it is because I've fired off a couple of AIM120s - I'm not sure. I have tried uncaging, turning off my radar, switching master arm to off, and deselecting A2A, but I still remain locked on the target. The only way to unlock I've found is to turn 180 degrees to break the lock.

I can easily reproduce this error. I have created a mission with two tankers and my F-18 flying behind at approx 7 miles. When I start the mission the two tankers immediately appear on my radar. I then eject, respawn the same aircraft, but even though I can see the tankers in front of me, they don’t appear on the radar.

I agree. At the start of a mission my radar is working. Then, when I go to refuel later on, even after turning the radar on and off, resetting, and with the tanker in front of me, the radar shows nothing. This has been consistent for the last two weeks (I’m flying 2.5.2) in every mission I fly.

I’ve had a game crash in 2.5.4 when my Huey clipped a fence in Nevada and the Huey crashed. Have also tried to fly the second F-18 campaign mission, but both times the game crashed. The first time it crashed after 15 minutes, the second time after 3 minutes. I’m flying in VR, and all three times I got the message DCS has crashed, and it allowed me to collect and send the dump files automatically.

Ahh - but we aren’t all the same. VR simming is the main reason I built this PC. It is very important to me. Upgrading and wiping the C drive had resolved all my stability issues and improved performance. My point was that you don’t need more than 16gb. Please don’t judge everyone else by your own standards.

I’ve just rebuilt my high end system, and after discovering I couldn’t overclock >16gb, I removed the other 16gb to get the performance back. Because I upgraded to Windows 10 and Then wiped my C drive, removing legacy apps, memory usage in dcs VR has gone down to 12gb.

Unable to connect Multiplayer Apologies if this has been raised before, but after installing SRS I'm unable to connect to multiplayer servers. Once I installed SRS - using the automatic installer, when I tried to connect to both AEF 161 sqn servers, using VR, it sits on the aircraft selection screen for a minute or so, then all the options disappear and all that is left is the hangar with the SU aircraft. I have tried three times to connect to the two servers, rebooting after each attempt. I then removed SRS, rebooted PC, and connected to multiplayer server. Any thoughts?

Two times I've flown the Harrier in VR, single player in my own simple mission to practice firing AGMs, for around 2 - 3 hours, and both times the game has crashed. I was using the on board camera both times, so whether that is a factor? I've included the crash log. No I haven't - it seems the zip file exceeds 9.7mb so it won't upload :(

A Fix of Some Sorts I connected to a multiplayer server. When in the select an aircraft screen, VR seems to freeze. After a few minutes I was kicked back to the DCS main menu screen. I clicked back on multiplayer, connected to the same server, and this time it works. I was able to happily fly around for over an hour. So it seems you have to connect twice to login multiplayer.

Same here - single player is fine (relatively speaking - still have DCS restarting after I shut it down, then have to restart PC to be able to start DCS again) - but when I go to Multiplayer it hangs on the aircraft selection screen. I'm updating DCS almost as soon as the updates come out, and have the latest - 1st August 2018 installed. I have an i7-6800k @ 3.40ghz, 16 GB RAM and a Gigabyte 1080 with 8G GB RAM

Still Restarting I ended up upgrading to Windows 10, then wiping my C; Drive and resetting completely and reinstalling DCS. Still have the same problem. I shut down DCS, and up pops the login screen again. If I close it, then it tells me I'm continuing without logging in, and starts up DCS. If I close it with Ctrl Alt Del, then the next time I start it, the login screen has lost all me details. This is happening with the latest patch as of 1st August 2018. What's frustrating is that after shutting DCS down this way, the only way to restart it is by having rebooted my PC. If I don' reboot my PC, then DCS will start up, but freezes at the screen just after the splash screen, showing half the aircraft in the hanger, but no options at all. You have to ctl alt del to close this, then restart the PC.

I've been experimenting with VR resolutions, and have found that when changing the VR Slider on the VR graphics page, the game restarts, but on restarting DCS, it finishes loading - as shown by the horizontal loading line down the bottom, but instead of showing the normal opening screen with the options to start a fast mission, modules, configurations etc., it is as if the VR has frozen on the view of half of the background aircraft that you normally see in the hangar. The only way to close DCS is to go to task manager and end the program. If you try and start DCS again, you get the same problem. Only way to startup DCS again is to restart PC.

I'm running DCS 2.5 using VIVE VR, and when I close the program - I leave the Steam VR running - the program shuts down, then restarts. This has happened randomly in the past, but now it has become more consistent (I have just updated 20th July 18 - so whether it is because of this?). It brings up the login screen, and whereas normally I have it set to autologin, on restart, it has my username and password filled in and the save password checkbox checked, but the autologin is unchecked. Previously, after re-login and shutdown, that would be it, it would close. Now, it shuts down and then starts again. The only way to shut it down currently is to goto task manager and close it there.

I've found that when I load a mission I've created - in this case using the Persian Gulf Map - it takes a while to finish loading all the textures. Because I've flown this mission a lot and did not need to edit it, I loaded it, decided not to wait the three minutes or so for the textures to load, and clicked on fly. The game crashed out to windows. If I then try to run DCS, it hangs at the menu window - just showing the hangar, and a bit of the aircraft. Nothing else. The only resolution is to restart computer to be able to load DCS again. Running in VR Windows 7 sp 1 64 bit i7-6800k 3.4 ghz 16 GB RAM

Thanks for all the info! The problem - as I just discovered - is that because my pilot was set to vunerable, I died! That was why my pilot reset and I lost all my hours. Maybe when you die a message should come up to say your pilot log has been reset? Or even something in the log page - when you select 'Vunerable', to have a warning message come up which tells you that your stats will be lost and country reset back to US if you die?

It was a rookie (in mission editor) mistake! I'd set the initial speed at 27 knots, without realising the end point had the speed set at 10 knots. Unfortunately, when I added the Tarawa at a later date, I must have put both points at 27 knots - which was why it was outrunning the other ships. I've set all the point to 27 knots and its all working as should be. Thanks.

Hi, I've used the missions editor to have the Stennis moving at 27 knots. I then added the Tarawa and put it to 27 knots as well. But, Tarawa seems to be travelling almost twice as fast, and within 10 minutes is way out front. I've double checked that they are both at 27 knots, and they are both on the initial way point which goes on for miles.

Hi, After flying around for a few hours in 2.5 Beta, I went to the pilot log and reset my country to Australia - losing all my hours up to that time. A few days later I checked the log, and noticed that my country had reset back to the U.S. Because I'll lose all my hours again, I really don't want to reset back to Australia until I know it will stay that way. Can you please advise?

I did a perfect landing onto the carrier, taxied (slipped - deck was rolling) along the deck, managed to successfully launch and fly away. I kept wondering why there was a warning tone. Then I realised I'd forgotten to unfold my wings before launching to take off! Should the F-18 be able to fly with wings folded? Because I did.

Further to my previous thread were the only way to stop DCS crashing was to do a reboot of PC, I've discovered that when I was using VR and created missions, after switching VR off, running DCS and being able to load those missions, switching VR back on, I'm unable to load those missions - DCS crashes just as it almost finishes loading before flight. However, I can load and run instant action missions OK. I've created new missions in VR (now that I've enabled it again, and these ones work OK. The only difference might be that previously in VR I had the screen resolution set quite high, and now I'm running it at the default 1980 x 720 (or whatever the default is).

Hi, I've found that when in VR, sometimes the simulation will crash, and it seems to leave something in memory, because the only way to fix it is to reboot the PC. Then I decided to use my physical MFDs because the VR MFDs resolution is terrible for ground attack. I unchecked VR. The game crashed on loading. A reboot allowed me to get it working again. I then decided to go back to VR - you just can't beat the immersive VR! And it crashed. It wouldn't start up in VR again. The only fix was to delete the config file under C:\Users\My Name\Saved Games\DCS.openbeta\config and start up again, select VR, close the program, then reboot.