Jump to content

mrivers

Members
  • Posts

    33
  • Joined

  • Last visited

About mrivers

  • Birthday 09/14/1973

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mrivers's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In Rare

Recent Badges

11

Reputation

  1. I'm sorry, this feature was intended for internal use and severely limited in function. It is completely disabled.
  2. mrivers

    Crash to desktop

    Thank you for providing the scenario and dump files. Unfortunately, after numerous attempts, I have not be able to reproduce and the dump file did not provide enough context to determine the cause of the problem. Please let us know If you encounter the crash again.
  3. mrivers

    Crash to desktop

    Thank you. Looking into it.
  4. mrivers

    Crash to desktop

    If possible, could you upload the scenario and dmp file? (%userprofile%\AppData\Local\CrashDumps) Thank you.
  5. A description of how things work at this time. The terrain dustiness is a result of combining the tile's dustiness value (from the map editor) and the ground saturation. saturationDustFactor = (1 - saturation / 4%) or 1, which ever is lower. finalDustiness = saturationDustFactor * tileMapDustiness. at 0% saturation, finalDustiness = 100% of the tile's dustiness. at 1% saturation, finalDustiness = 75% of the tile's dustiness. at 2% saturation, finalDustiness = 50% of the tile's dustiness. at 3% saturation, finalDustiness = 25% of the tile's dustiness. and at 4% saturation, finalDustiness is 0%. The finalDustiness must be greater than or equal to 25% in order for it to be kicked up be vehicles. Once the finalDustiness is found, it is then modulated against the vehicle speed to determine the scale and transparency of the dust. I'll discuss this with the other developers to see if we can create a better solution.
  6. Please start SB fullscreen again. When it becomes non-responsive, right click the task in Task Manager and then "Create dump file.". This should create a dump of the state of SB and hopefully will point us to the problem. Thank you.
  7. Thank you for the scenario Rotareneg. It illustrated the problem perfectly and is now fixed.
  8. For those with issues, please list any overlays, graphics injectors, etc being used. (for example, MSI-Afterburner, Reshade)
  9. Thank you. It turned out I had a rather ancient version of the Map Transfer tool :O Installed new version and found it.
  10. I'll need a link for the map used by the AAR.
  11. Thank you. We're able to replicate the problem and we're looking into it.
  12. 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.
  13. 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%
  14. 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.
×
×
  • Create New...