Jump to content


  • Content Count

  • Joined

  • Last visited

About Coug4r

  • Rank

Personal Information

  • Flight Simulators
  • Location
    The Netherlands
  1. If you do it on mission level you could use timer.getTime or timer.getAbsTime and add it to the mission start time and date. Not sure what happens if you'd pause the mission though if that would apply or if that method would be accurate if a missions runs for more than 24 hours
  2. Came across this post while I was trying to do the same thing. Not that it would solve your problem but there are 2 bugs in your code. DCS.getRealTime is a function so you have to use DCS.getRealTime() and getModelTime() lacks the DCS. prefix. It would be nice to have some function to get the actual mission time on server level indeed.
  3. Maybe this can be made optional for the servers or auto detected if SSE4.1 is available so the players/pilots can have the advantage of it.
  4. Yeah noticed this too. With little roll input nothing much happens but when slightly increasing the input the roll suddenly kicks in. Very different from other AC.
  5. Got this one today after maybe 30 minutes of flying. Running DCS unmodded. textures/dubai_objects.varyhouselod4.1.selfillumtexture @ mods/terrains/persiangulf/models/dubai_objects/dubai_objects.texture.zip
  6. Even tacview logs it's higher than that. Either way, is there a way we can change the default? Most people don't even get 120 fps on their sim rig, might be a little over the top to have a server tickrate that high.
  7. I'm looking at an average of 135.7 fps now, doesn't appear to be limited at 120 fps.
  8. Were the latest updates supposed to have this fix yet? I'm seeing an fps of roughly 80-120 depending on the mission but the max fps is set to 30 in the autoexec.cfg.
  9. Tested on Caucasus, PG and NTTR and the results are the same so it's not a map issue.
  10. Seeing quite a bit of increase in the dedicated server CPU usage (DCS core), it used to be 30-40% before the update and now it's like 85-100%. Anyone else seeing this?
  11. You can also try set a FOV in the viewport config in your monitor setup file. 1.0 is the default value >1.0 is FOV+/zoom out <1.0 is FOV-/zoom in This is what i'm using atm: Viewports = { Center = { x = 1080-250; y = 0; width = 2560+500; height = 1440; [color=Red] FOV = 1.30; [/color] aspect = 2.1944444444444444; }, }
  12. Maybe this was fixed in the meantime but this doesn't seem to work anymore. OB v2.5.4.28090
  • Create New...