dorianR666

Oh, yeah thats even below minimum requirements. My bad. That being said I run with 32GB and i get less FPS than him LMAO.

Where? I think youre confusing RAM and VRAM. (I cant read) Yep, it is suspect.

Mark it 10. I believe thats just the nature of low FPS in a game with fast jets. If you look forward and your view is static, only small portion of your screen's content moves and it moves relatively slowly. If you look perpendicular to your flight direction, the content will move faster across your screen from side to side, making low FPS more noticable.

Consider that for example only 12% of steam's userbase has more memory than 16GB, which already wasnt really enough for missions in more performant Syria. And thats gamers. That comment was based on reports in this thread and on reddit. In this forum thread alone, I count 9 people (including myself) reporting approximately half the performance of Syria or PG. Really the issue is that the LOD/render-range sliders do almost nothing on this map, for some reason. If you look at pierrewind's post here, notice that in the second screenshot almost nothing is being rendered, pretty much only ground mesh - yet FPS remains almost the same as when everything is rendered at high quality (16 FPS vs 14 FPS). I understand that many and detailed objects require powerful HW but if you render almost nothing and frame time is still the same (poor), something is wrong. What is the time being spent on in that second screenshot? Oh I'm happy for those for whom it run well, dont misunderstand me. Its a very nice map. Maybe after this global GPU shortage is over, I may be able to join them Edit: added second&third paragraph

There needs to be some balance with that. Even people with powerful and expensive high-end gaming rigs report insufficient performance here on the forum and on reddit. With Syria it was already an issue for large portion of the userbase and now we have a map with roughly half the performance of Syria. If only, say, 15% of your playerbase can comfortably use it, then thats a problem. Lets hope its merely a software bug or incomplete optimization.

It doesnt explain that. Im saying the lua percentage says nothing about the nature of the problem, besides more time being spent per frame which is already known. Hopefully. Looks like ideal map for carrier ops. Would be shame if most of us couldnt use it. Well, it got new graphics engine since then (2.5 in 2018).

it shows higher lua use percentage on caucasus because the rest of the frame computation takes less time than on marianas. thats to be expected.

LOL, in the first screenshot, there is practically nothing rendered and you still get 16 FPS. This gotta be a bug.

Same. I get 30 FPS in Syria but 10-15 FPS in Marianas. At first i thought its because of the trees, so i set tree sliders all to minimum - 2 FPS change. Then i though it must be the shadows, set them to flat - maybe like 3 FPS change. Maybe the terrain mesh? Tried ground radars, no observable slowdown (unlike Syria, interestingly). So it seems to me that buildings are missing LODs or something like that perhaps. Edit: not VR

You mean the official manual? Each module has a manual. Its a PDF file in <DCS program files folder>\Mods\aircraft\<module name>\Doc

+1 related thread by me, some time ago:

hi, in the first mission, this line is printed twice.

It doesnt seem to be so. The wind logic in airfields is broken.

this is now marked correct-as-is without ED replying (seems happening a lot lately). you might wanna PM bignewy on your own.

....why is this marked correct-as-is??? its extremely confusing, there is no indication that youre dead, the only practically noticable difference is that you cant flip switches. all other modules will switch you to external camera and you cant go back into cockpit. this is a bug.

Syria is not supported

+1 pilot can die but camera will stay in cockpit. you cant control any switches, not with clicking or keybinds. cyclic and collective dont respond. you cant switch seats.

i think i remember the guy from deka saying that some manpad unit doesnt properly set launch time for the missile, so they had to work around it in their module to fix it (jf-17 has mws).

Igla is hopeless. Its like it doesnt even guide.

If youre referring to the mig-21 module's behaviour, that was mismodelled.

better even, make a custom snap view

+1 seems like bug to me.

its always been quite broken.

same, it seems to me the gyros only stabilize against random shaking noise of the heli right now.

9nm is a lot. Petro looks at the point you designate and will give you the list of targets once you get close enough.