Jump to content

Hoover

Members
  • Posts

    114
  • Joined

  • Last visited

Posts posted by Hoover

  1. On 8/21/2019 at 6:45 AM, Maj.Hans said:

     

    A vehicle with a system "Removed" will behave exactly as if the system is "Damaged", but the player won't have the blinking damage warning up on the screen for the entire mission...

    👍😎

  2. On 8/6/2019 at 4:54 AM, inexus said:

    After having reading people's results and I've tested a large number of different scenarios it seems unlikely that a descent framerate can be achieved even on the fastest overclocked CPUs and GPUs today unless the missions are fairly small in terms of landscape complexity and units. I've given up the idea of upgrading to a 9900K@5Ghz as I only think it would provide a few more fps.

    It's really hard to poinpoint what is causing the slowdown. I had a scenario where changing ground cover from 44 to 45 would make the fps drop 10 frames from 40 to 30. If i reverted the value to 44 it would go back up to 40... 

    Hi inexus,

    did a little bit benchmarking today. Here are the results.

    Cheers Hoover

     

    [REPORT]
    In Benchmark 1 I had the GPU maxed out between 82% and 99%. As I could not believe it, I repeated the test 3-times. It always came down to the same result. If you look at the FPS only, all seems to be OK. The GPU usage tells another story. Before drawing a conclusion, others should confirm that result. Very interessting would be a benchmark result with a quicker GPU like the GeForce RTX 2080 Ti.

    [TEST]
     I used MSI Afterburner for testing. Load Afterburner after you entered the station you like to test. Avoid switching to the map. Always take you position first then start Afterburner.

    [REMARKS]
    From minute 02:00 the weather gets worse and the visibility gets lower, felt proportinal goes the GPU load down from 99% to about 57%.

     

    [UPDATE]

    In my results the GPU was maxedout to 99%. But this finding seems to be an edge case and happens only when you look in direction of the wood in daysight and in a short distance to the wood. I could reproduce this behaviour (GPU maxedout 99% ) in another scenario. But the FPS stayed in these cases within the (for me) playable (> 30 FPS) range. When I pan away from the wood the GPU loadout drops dramatically.

     

    [temp. Conclusion]

    In my case with my hardware the GPU seems to be NOT the limiting factor.

     

     

    benchmark-results.jpg

    Deep Forrest (1)_0014_dayview.jpg

    Deep Forrest(1)_0024_thermalview.jpg

    Deep Forrest(1)_0250_dayview.jpg

    Deep Forrest(1)_0259_thermalview.jpg

  3. 56 minutes ago, Captain_Colossus said:

    this weekend i'll get my first opportunity to spend time with steel beasts for than just a few minutes; already i see how much the terrain has improved. some of the map locations i have been looking at to mess around in look like places i want to go on hikes or go on vacation- serene meadows, tropical islands, the improvement over all previous versions is comparable to the improvement of steel beasts version 2.00 over steel beasts gold version 1 if not more so.

    Hi Captain,

    have a lot of fun with 4.1! Please enjoy the beautiful screenshots from @norrin with a grain of salt🧂. I think these are not pur Steelbeasts shots but colored by an external graphics shader. Anyway they look impressive, more real than default. It‘s the magic of light 💡  that totally changes the impression and the mood of a scene.

    Cheers

    Hoover

  4. 28 minutes ago, Ssnake said:

    Obscuration needs to be identical irrespective of graphics detail settings.

    Yes in multiplayer, less in single player. As far as I know in multiplayer mode the hosts enforces certain rules. The amount of dust could be one of them. The single player could set the dust according to his hardware.

  5. Just now, Gibsonm said:

    ou don't want a global setting that says regardless of the terrain you'll see "some" dust (leaving aside the subjective measure of "some").

     

    As I understood the case, the scenario designer sets the parameter which influences the amount of dust created. If for example a shell explodes or a vehicle drives by. Now we have a situation where (for performance reasons) only dust of vehicles 🚗 🌪 is visible, not from exploding shells. Because I sometimes write before I think, I read my own post again but sorry,  I could not find the section where I demanded dust „...regardless of the terrain...“

  6.  

    1 hour ago, Dr.Thodt said:

    @Hoover What about he bug where the unbuttoned commander could not be steered with the joystick? That bug was in V 4.157. 

    5 minutes ago, Toastman said:

    Yes , the 4.157 bug was related to the TC unbuttoned view in the Leo2 ,you could not look around using j/stick control . 

     

     

    Sorry guys, my CPU took a while to recognized the problem. Now I understand it and of course, it still exists.

  7. 2 minutes ago, Dr.Thodt said:

    @Hoover What about he bug where the unbuttoned commander could not be steered with the joystick? That bug was in V 4.157.

    Hi Doc,

    I hope I understand your question "...steered with the joystick?" because this problem is unknown to me (maybe I missed a bug 😎).  I steer all things crawling, running or rolling with a 4-way switch on the throttle. I use the joystick for looking around, slewing TIS, GPS, GAS, Peri... Please take a look at the screenshot below.

     

    SteerUnits.thumb.jpg.3fe04d06ba1d9aeddfbb6f7220101317.jpg

     

  8. Joystick: Warthog Joystick / Throttle Combo

    Tank: Leopard 2

    Behaviour before installing patch 4.1.5.9 (all versions of SB as I remember)

    • TC slews TIM/EMES with joystick: OK
    • TC slews Periscope with joystick: OK
    • TC Cmd ZU with joystick button (H1 > H1U - Trim Switch DX Hat 1 upward) OK
    • TC Cmd Face gun with Joystick button (H1D - Trim Switch DX Hat 1 downward) OK
    • TC Toggle TIM/EMES with joystick button H2 > H2U TMS Up DX 7 OK

    Behaviour after patch 4.1.5.9 (first version of SB IMHO)

    • TC slews TIM/EMES with joystick: does not work
    • TC slews Periscope with joystick: does not work
    • TC Cmd ZU with joystick button (H1 > H1U - Trim Switch DX Hat 1 upward) does not work
    • TC Cmd Face gun with Joystick button (H1D - Trim Switch DX Hat 1 downward) does not work
    • TC Toggle TIM/EMES with joystick button H2 > H2U TMS Up DX 7 does not work

     

    Update: I know, I should not do it, never ever... anyway (😈) I did it and patched the new (4.1.5.9) patch with the old one (4.1.5.7). All things not working since 4.1.5.9 (see above) work again 🤸‍♂️. Waiting for the sim to crash now 🧨...

     

     

    brokenMovementKeys.jpg

  9. On 8/5/2019 at 5:22 AM, Rotareneg said:

     

    You guys play always(?) with enemy icons not shown on the 🗺 map. It‘s easy to loose the orientation, at least for me. Where does this shot come from?👀

×
×
  • Create New...