Jump to content

droopy114

Members
  • Posts

    495
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by droopy114

  1. Terrible news...RIP Gospadin...
  2. LOL Tsync why not...Rise of Flight, Elite Dangerous, are perfect when Vsync'ed at 144hz, and FPS fluctuate...but honestly i'm done with this, i just enjoy DCS 2.5 now :D
  3. Give this a try: set your "resolution of cockpit displays" to 512 or 1024 every frame https://forums.eagle.ru/showthread.php?t=202541 https://forums.eagle.ru/showthread.php?t=199880 Maybe an issue with frame timing, wich can cause heavy stuttering, that did the trick for some of my friends having the same issue...
  4. This is another issue, but i was not aware about the Harrier having the same bug. I though this was a Viggen issue, so maybe not, i tested with the KA50 and it's fine, with or without this option set to every frame. What Goa suffer is this: https://forums.eagle.ru/showthread.php?t=176131 And guess what? still the same issue. Same as you, Goa. I have a 27''144Hz curved screen. After some extensive research, i found the following: Vync@144Hz, in high altitude or somewhere in Nevada to have a steady 144FPS: TIR is perfect Vsync@144Hz, but 1/2 the refresh rate (so 72FPS): feel like in the Youtube video (???) So to go deeper, i lowered the refresh rate of my monitor to 120Hz, then: Vsync@120Hz, looking for a steady 120FPS: perfect Vsync@120Hz, 1/2 the refresh rate (60FPS): perfect So >below 144FPS>look like Youtube's videos >below120FPS (from 119 to 61)>same You need a perfect 120 or 60FPS to have a smooth TIR, and the strange thing is with mouse or keyboard, view panning is perfect, no matter the FPS. Still trying to figure if this is a DCS or a TIR issue... So for now, i keep my refresh rate at 120Hz and use adaptive Vsync at 1/2 the refresh rate. Unfortunately my 144Hz screen is useless...
  5. here are my results: -launch DCS -resolution of cockpit display was already set at 512 every frame -launch the default "airborne intercept" mission >steady 60FPS, perfect frame time, at about 16.66ms, as expected -leave mission -choose 512 only, without leaving DCS -launch "airborne intercept" >steady 60FPS, perfect frame time, at about 16.66ms, as not expected :huh: -leave DCS -launch again DCS -resolution of cockpit display:512 only -launch "airborne intercept" >erratic frame time but steady 60FPS, as expected :D Here is a video, default mission "cold start": Maybe not easy to see, but this is particuliary noticeable when you look up or down in the cockpit, not in front of you :wassat: Log attached. Thank you! Logs.rar
  6. Will try this too, thanks for looking into it.
  7. Textures, exterior or cockpit, are for me the best looking in DCS, no complain about this. But i agree with the shadows, going from flat to low, it take a massive hit.
  8. Just to say, bug still here in the latest 2.5 version, but not exactly as it was before. Frame time is erratic this time, sometime correct, or totally crazy, depend where you are looking, and it still cost about 15FPS hit. I will post a video later.
  9. Finally, someone else with this issue! Does this sound like this: https://forums.eagle.ru/showthread.php?t=199880 The only solution: set you cockpit resolution display to 512 or 1024 EVERY FRAMES, strange issue but that's the only solution i've found.
  10. In signature, but: I5 4690K @4,5Ghz, 16 GB RAM GSkill 2133Mhz, Nvidia GTX 1070, MB MSI Z97, Samsung Evo, Windows10.
  11. :thumbup: BTW, except this problem (and the AA/AF filtering with DS On, but it's another thread), great update. DCS look amazing!
  12. And uncap a bottle of beer, might help :thumbup: Seriously, same here, and i'm not alone in my group, the majority of us have the same issue. Fine in SP, in MP with a few nerds but add somes units and a few more players, and we''re stuck at the loading screen. This problem is certainly related to the high amount of RAM used by DCS, between 6/9gb in SP, depend what's going on, up to 14/15gb+ in a "light" MP server...I hope the team will have a look at this issue, RAM price are insane those days...
  13. Yes, and it work very well. MFAA is great, cost less performance than msaa: https://www.geforce.com/hardware/technology/mfaa At the begining, it was only available for a few games, but now seems to work in every game as long as there is a msaa setting. Performance cost: -10/12FPS, in the screenshot below , compared to the HDR, but it worth the few FPS lost... %5Bimg%5Dhttps%3A//image.ibb.co/d94kB6/Screen_180126_224312.jpg[/img] nvidia Inspector: %5Bimg%5Dhttps%3A//image.ibb.co/huC5B6/Capture.jpg[/img]
  14. It work, but you have to: In game: *select 2x msaa Nvidia Control Panel: *Antialiasing-mode> enhance the application setting *Antialiasing-setting>2x *Multi-Frame Sampled (MFAA)>ON
  15. This is really coming, great! Could we have an estimation about what remain to download, I mean the file size?
  16. Surprisingly, no one report this bug, or maybe my first post is unclear, so a video will better demonstrate the problem: First part, 512 (standard, not every frame) top left corner, have a look at the frame time: totaly crazy, and cause major TrackIr stuttering/juddering, don't know how you call this, FPS counter is showing 60FPS. Second part, 512 every frame, perfect frame time, TrackIr perfecly smooth. Also if you untick the vsync option, don't cap the FPS, you will notice a big performance impact: 99/100FPS with the option set to every frame, 125/130 with standard non-every frame!
  17. Well, finally found the culprit of my horrible stuttering with TrackIr in the Viggen. If the option "resolution of cockpit display" is set at any other setting than "every frames" (no matter the resolution, 256, 512 or 1024), frame time is crazy, despite a perfect 60FPS (you can check frame time by pressing right ctrl+pause twice), if every frames is enable, frame time is perfect (approx' 16.66ms for 60FPS) and TIR perfectly smooth. A screenshot can't capture the moment, but i can post a video later showing the issue. The problem is there's a serious performance drop (like 15/20FPS) if every frames is selected, and a module like the BlackShark, wich use MFCD's, don't have this problem. Another friend of mine have the same problem, so i assume it's not on my end. Could you have a look?
  18. Great! do you plan to release them?
  19. Nice changelog :thumbup:
  20. Happy New Year!
  21. Wonder the same. Tacview use a script to export data from DCS, would it be possible to create a script that allow DCS to create a track with a Tacview recording?
  22. This bug could explain alot on what happened today on DCS_nl server with my team mate.... something like a big explosion, similar to nuke, but no Mig21 in flight (the 21 is the only aircraft who can carry a nuke, isn't it?) and destroy everything on the airport. Server have no integrity check.
  23. You have to load the data contained in the cartridge, to do this: (CK37 control panel) ref/lola, switch position "in", then enter "9099" and press "ls/sku". If you want to input coordinates manually, be sure to enter EAST coordinates first, then north. Not common, but this is how it work.
  24. Quingon a raison, nul besoin de désigner une cible pour le rb04, il te suffit de placer ta cible entre les 2 traits horizontaux qui apparaissent sur ton écran radar, qui représente respectivement la portée max (en haut) et la portée mini (en bas), une fois largués, les missiles vont commencer de scanner et tenter d'acquérir une cible par eux même. Il est important de noter que le switch placé sur la banquette de droite, nommé "grupp" et "enkel" a une grande importance sur la manière dont le missile va tenter d'acquérir son objectif...une règle (sorry, in English :) ) https://forums.eagle.ru/showpost.php?p=3244936&postcount=9
×
×
  • Create New...