Jump to content

dorianR666

Members
  • Posts

    1625
  • Joined

  • Last visited

Everything posted by dorianR666

  1. its kind of a big deal actually. it makes some campaign missions unplayable.
  2. hi, thanks for info. this will be useful for me in future mission making. the indices are fine, i tested it in editor. must have been a user error on my part, with making markpoints unprecisely at 9k.
  3. hm, i checked the mission triggers and it checks for two cockpit button presses for the markpoint creation, while being in a zone. i made the markpoint at higher altitude to avoid ground fire, and so i may have been unprecise. i guess that explains it. still weird about the screenshot though.
  4. the thing happens with like 30 minute delay. i got this after i flew all the way (100+ nm) home and landed. bug?
  5. could it be because my wingman keeps crashing into terrain every time? is he supposed to say something? i now found out i can still RTB and get 52 result, but there is absolutely nothing telling me to RTB and no message after landing (that may be intended). its like the mission abruptly ends after killing the manpads, nothing is heard or shown afterwards.
  6. I dont get it. I report detail on the crash site. Vehicle moves into the compound. Im told to create markpoint on the crashsite. While doing that, I get shot at by the manpads and get told to destroy it. I destroy the manpads. Cool, I can now do the markpoint. I do the markpoint. Nothing happens after that. Im not getting any radio messages. Im circling above and nothing happens. According to youtube videos, there are supposed to be reinforcements coming and im expected to choose between attack or RTB. This never happens to me. Very frustrating. What am I doing wrong? Whats the trigger im missing? BD, for future campaigns, consider adding an F10 command "Current task?" that will give me a simple text message describing what I'm supposed to do at given moment, for people like me :). With these trigger complicated missions it gets confusing. Or maybe Im just dumb.
  7. fixed, thanks
  8. same, this is reported i think. TOO is all around broken right now.
  9. yes, i was answering the question in the post. not the question in thread title.
  10. as far as i know - no. you have to support the missile until pitbull or it will fly straight (instead of extrapolation of targets movement).
  11. Oh, yeah thats even below minimum requirements. My bad. That being said I run with 32GB and i get less FPS than him LMAO.
  12. Where? I think youre confusing RAM and VRAM. (I cant read) Yep, it is suspect.
  13. 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.
  14. 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
  15. 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.
  16. 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).
  17. 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.
  18. LOL, in the first screenshot, there is practically nothing rendered and you still get 16 FPS. This gotta be a bug.
  19. 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
  20. You mean the official manual? Each module has a manual. Its a PDF file in <DCS program files folder>\Mods\aircraft\<module name>\Doc
  21. +1 related thread by me, some time ago:
  22. hi, in the first mission, this line is printed twice.
  23. It doesnt seem to be so. The wind logic in airfields is broken.
  24. this is now marked correct-as-is without ED replying (seems happening a lot lately). you might wanna PM bignewy on your own.
×
×
  • Create New...