Jump to content

Recommended Posts

Posted (edited)

I went back on it today because I found a multiplayer server and I really enjoyed myself and I found the map beautiful and super pleasant.

 

just a shame about the low fps when flying at low altitude

 

I have 100 fps at 5000 feet, and if I go down to 200 feet I have 25 fps, as soon as I go above 2000 I have 100 fps, why?

there's too much detail in the trees or on the ground, it's a shame to have done this for planes the fps drop is brutal, 95 fps, I go down = 25, we feel huge jolts

it's only on this map that I have it

 

image.png

image.png

image.png

 

4060ti 32giga ram

Edited by mobile83
  • Thanks 1
  • mobile83 changed the title to good map but too bad fps drops at low altitude
Posted

Why? You have the topic about it:

 

 

  • Like 1

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted

Hi, here's a video that explains the problem, only encountered on this map, at first everything's fine, I can fly at low altitude and fps are stable, then 5 min later it does this to me... I have to quit the game and reopen it, knowing that I have a lod at 1, a 4060 TI and 32 giga ram.

I hope the developers will see this problem, on all the other maps I don't have this, even Syria remains stable at low altitude.
 The fxo and metashader folders were emptied before testing.

 

  • Like 2
  • 7 months later...
Posted (edited)

Tried the map again today (latest patch) this same problem exists with all my aircraft installed. Is this issue acknowledged by the developers?

Edited by westr

harrier landing GIFRYZEN 7 3700X Running at 4.35 GHz

NVIDIA GeForce GTX 1080Ti

32gb DDR4 RAM @3200 MHz

Oculus CV1 NvME 970 EVO

TM Warthog Stick & Throttle plus 11" extension. VKB T-Rudder MKIV

Posted
On 9/10/2024 at 2:12 PM, PLUTON said:

yes 

Thanks

harrier landing GIFRYZEN 7 3700X Running at 4.35 GHz

NVIDIA GeForce GTX 1080Ti

32gb DDR4 RAM @3200 MHz

Oculus CV1 NvME 970 EVO

TM Warthog Stick & Throttle plus 11" extension. VKB T-Rudder MKIV

  • 1 month later...
Posted

Is this issue being worked on?
I mean, it's of course good to have the acknoledgement about the existence of an issue, but you know ... just asking :lookaround:
This map is so wonderful, but so unplayable when flying low.

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1

 

Posted

I really hope the upcoming update can address this.  There's a small subset of us that really struggle with the framerate being mauled under 900ft.

Posted

Just conducted another test.

Still the same, though I did find some interesting things:

  • For me, FPS seems to go to pants at around 800-900 feet altitude
  • Doesn't seem to matter if you're over land or water.  Even on an open sea with no land for miles, it still does it
  • From looking in Task Manager:
    • It's NOT a GPU issue.  My GPU load dropped down to 30-40%
    • It does appear to be very related to the primary thread.  That core was for me at 100%

So it would appear to be some calculations being conducted below a certain altitude within the primary thread.  No idea if that helps, but hopefully.

As this is only true on the SA map, is it possible that the map has a configuration setting where the sea level is different to other maps and maybe the primary thread believes that our aircraft are below sea level and is trying to decide if we've crashed or not?

  • Like 5

7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat 

Posted
On 11/9/2024 at 12:41 AM, Mr_sukebe said:

As this is only true on the SA map, is it possible that the map has a configuration setting where the sea level is different to other maps and maybe the primary thread believes that our aircraft are below sea level and is trying to decide if we've crashed or not?

Wouldn't subprise me if something like that is the error. 😉

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...