mrivers

I am unable to reproduce this locally. It would be great if an in-progress-save of a scenario that triggered this problem could be provided along with viewing location.

Please try setting the font/app scaling to 100% and relaunch SB. Open Window's Display Settings (rt click desktop) Set the "Change the size of text, apps and other items" to 100%

I think you can rule out memory. If you consider a CPU, it should have higher single thread performance (more cores won't help the frame rate, though they will help during map loading). A 1070, in theory, should be quicker. It has (afaict) more memory bandwidth which will be useful for high res displays. However, I couldn't tell you how much quicker, it may only be a few fps.

The tree textures are loaded before the scenario starts. The cache I mentioned above that is updated during the course of the scenario is used to optimize determining which trees to render, and their physical location. Nothing is loaded from disk, but it could be a bit cpu intensive to generate this cache. (imagine panning a few thousand trees into view and data needs to be generated for those trees)

I don't know if a 1070 will improve your situation, because it may be a CPU/memory bandwidth problem and not a GPU problem (or something unrelated even). I do use an 8GB 1070FE card and it performs quite well with SB. Regarding sounds, the sound files are not loaded on-the-fly. If you suspect sound related issues, perhaps check for driver updates. Also, the mention of throttling is interesting. It would be good to verify your CPU/GPU temps are good. I've suffered from throttling problems after I bumped the CPU cooler and broke the bond with the heat sink.

I looked at the debug log, but don't see any reason for stutters. However, your last description of the problem could indicate the tree cache being populated as the culprit. While panning, trees that come into view are added to a cache. It could be that there are so many trees that it takes longer to update the cache and that results in a delayed frame. Could you upload a scenario that causes these stutters?

For the debug log, please start the exe with the command line parameter -loglevel trace. This can be done by selecting Start Menu->eSim Games->Toubleshooting, and then launching SB with the (debug) shortcut. Please enter the scenario, and go to the Leo TIM view (or any view that experiences trouble) and exit. Please attach DebugLog.txt (not one of the numbered ones, as they are from previous sessions). Regarding the Pagefile line. The values are indicate the total page file that is available to SB, and how much of it is consumed by the the system, other applications and SB (so, everything).

I examined the debug data provided, unfortunately I cannot provide a concrete solution. SB uses Window's "default audio device". I have seen this problem on occasion due to the audio device being missing or being changed once SB is running(unplugged USB headset for example). As mentioned, HDMI connections could also pose a problem as the available audio devices can change if the cable is un/plugged or if the monitor is turned on/off/stby. Please ensure your default audio device is set correctly before starting SB. If you're using HDMI to feed video and audio to your monitor, make sure the monitor is on before booting the system.

Interesting, I had been running Avast up until about a month ago myself, perhaps had I kept it a little longer I too would have experienced that problem.

Thank you for the feedback, it'll be something to keep in mind if others report similar problems.

Please let us know if any of the solutions have worked or not. It could aid us in assisting others. Thank you.

The dump files indicate you have RivaTuner/MSI Afterburner installed. Disable, uninstall or update RivaTuner to v7.0.0.0b19.

While it can't be ruled out due to significant changes in 4.019, I believe this is unlikely to be related to the video card. Is the scenario available for download? Which position and vehicle were you in? Was anyone else sharing the vehicle?

Can you upload a scenario you used when this crash occurred. Thanks.

If possible, could you provide a scenario that causes the crash? I've tried to replicate this crash several times with no success. It's possible that my scenario's are just too simple.

This is actually no longer the case, it is 2300(default value from UI) and 2400 only. Unfortunately, the change did not get documented.

The host must have 2300 UDP and 2400 UDP open/forwarded.

Was just able to reproduce this and it doesn't appear to be directly related to MP. Anyhow, will forward the info I have to correct coder.

When you were booted, was there a message state the connection was lost, or did it fall back to the menu screen, or crash?