Jump to content

toilet2000

Members
  • Posts

    419
  • Joined

  • Last visited

Everything posted by toilet2000

  1. I've had this happened because the aircraft wasn't properly trim. Make sure to trim the Ka50 when in hover, then engage the auto-hover. The reason for the drift is that the autopilot system doesn't have full authority over the stick and collective. If the forces required to hover the ka-50 are bigger than what the auto-pilot is willing to output, it'll just apply as much as it can (but not enough), thus making the aircraft drift. Make sure the forces on the cyclic and collective are close to zero (trimmed) in auto-hover before engaging the AP.
  2. No it's on Caucasus! And on 1.5 it was almost always on "5", not "2". But good idea!
  3. @RagnarDa IIRC you talked about TERNAV causing troubles at one time. I don't know if it has any links, but it does seem like the performance drop happened at low altitudes and on the ground, but not at higher altitudes. Moreover, it seems like the TERNAV system is stuck on status "2" (TERNAV OK, mode rough search. System is attempting to orient itself in a particular area).
  4. I just upgraded from an i7-2600 to an i5-8600K, same everything else (apart from MB and RAM), same Windows install, same DCS install. I was experiencing this stutter before, but it seems to be gone now. Maybe it's hardware related? If you want more info, don't hesitate to ask! Thank you and Heatblur in general for your great module and great work/support!
  5. I'll test it as soon as I get home! I'll post back the results.
  6. Alright thanks! I wasn't sure if the known problem was simply about the MP RAM leak or if it included what I am experiencing (VRAM memory usage). Haven't seen it reported as a symptom of the memory problem most are experiencing.
  7. I've got some kind of problem with TERNAV in 2.5 too, where it seems stuck on status = 2 (5th digit), mode rough search. Is it just me?
  8. It seems like memory usage gets bigger over time, after 2 or more missions. I get 10-11GB VRAM usage (according to in-game overlay) on a typical mission (which seems HUGE by itself, with Medium visibility range, 100 000 preload, high texture, high terrain texture). But after running multiple mission/scenarios, I've seen usage go up to 23 GB of VRAM! At least according to the in-game performance overlay. Has anybody got the same kind of VRAM usage?
  9. +1, I've got the same issue on 2.5. I was wondering why my performance in VR was weird, but only with the Viggen. I'll try using "every frame" and see if it helps with FPS consistency.
  10. I got up to 23GB of VRAM usage using the in-game tool... There's definitely something wrong with VRAM usage too.
×
×
  • Create New...