Jump to content

nitron

Members
  • Posts

    12
  • Joined

  • Last visited

1 Follower

Personal Information

  • Flight Simulators
    DCS, MSFS2020 …1st was f/18 interceptor on amiga 500
  • Location
    San Francisco, CA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi folks, so for me 2 issues. There was likely a RAM issue, even though I ran memtests. I updated from 2- 4 sticks a while ago and that caused some trouble unmasked after the update. But eventually I saw some more frequent crashes with the previous build too. After increasing voltages things have become much more stable and I could update the latest stable again. On top of that my reverb g2 cable broke down, which I think contributed here as well. It could have been just a coincidence that always when I tried the latest stable built it would crash with those unplug errors. The headset eventually would not be detected anymore with some 4-1 error. They went away when I tried another headset. So many crashes and hours later I think for my part I am good now. Thanks for your input!
  2. Here is another crash when I just tried with the latest stable. I still don't see the 'INFO APP: Device unplugged' message in the log but it was definitely disabled. I had it set in both autoexec.cfg (no_device_hotplug = true) and settings. Yep I am using VR as mentioned in the title. Also I defaulted all my OC settings turned off. dcs.log-20221009-190820.zip
  3. Attached is one of the working sessions with my previous build. I saw suggestions from Flappie about disabling hotplug and I tried that yesterday too. I can give it one more try to double check it was in fact turned off. But with this option enabled it still was fine previously. dcs.working29493.log.zip
  4. Hi folks, Ever since my update to the latest stable the game keeps crashing to desktop quite often. VR picture turns blue and out I am. Tried RAM check and GPU Ram check without errors since I thought I cloud have an issue here initially. I had a liberation mission were this frequently happened and when I rolled back to previous 2.7.17.29493 it se emed to have gone away. Log and dump attached. Please let me know if you need more info. dcs.log-20221009-011452.zip
  5. Just happened to me again. While I typically run into this when returning to the carrier I also get this when returning to an airport like it just happened. I don’t think I had Tomcats close by but it’s definitely some landing and/or communication issue during that phase. The game rarely crashes for me other than now quite often shortly before landing. I use liberation and I also use vaicom/voice attack plugin. While I guess voice attack should not cause crashes here I would still like to point this out it’s being used in my case.
  6. I saw one of the posters was using the persian gulf map. I ONLY get this there as well all the time in hornet and viper. Hope this is going to be fixed soon as this makes it very difficult to use visual tgt search. There is also a „bug reported“ thread here:
  7. Yep, that definitely works, thanks again. ...Ironically it should be the opposite, the more fuel the bigger the boom on such hits. Will see perhaps this can be automated when spawning idle missions in liberation as a workaround.
  8. Thanks, the aircraft are not static per say (created from the static objects flow) in the provided track. They were set to ai + uncontrolled.
  9. Done, 2 direct hits, only shows up as damaged. If you take control and let it burn it should just disappear and the kill would never be counted. ...One more thing I ran this from a liberation mission so you might get scripting errors if it's not running in the background. They can be skipped but you would still get the same result but it's a bit annoying of course. Thanks. migmavpound.trk
  10. This seems to be still an issue with DCS 2.7.9.18080 , I just pounded a bunch of mig-29s on the ground with mavericks and cluster ammunition and they only showed as damaged and eventually disappeared but never counted a kill. Only a pretty direct hit with 2 mk-82s for example gave me a counted kill. This cannot be realistic at all especially with a direct hit with a mav. I am playing with liberation so OCA missions are pretty pointless. They have an issue open to just track damage but I think the fix should be on the DCS side.
  11. A little late to the party, but for the liberation players out here the 12900k(f) is very much worth it! I tested 11th and 12th gen and the larger campaigns with heavy ai are now stutter free with no culling needed. Previously the game would become heavily cpu bound in those cases sometimes becoming unplayable because of stuttering.
  12. I am sure there is some devil in the detail, but super carrier really cannot handle busy decks at all, even if just temporarily, which causes a lot of headaches. Who wants to start over after waiting for the start slot and then after a cold start or even worse at the end of a successful mission not being able to land. 1) If airplanes are landing and launching don’t use the launchers on the deck and only the bow ones. i can imagine this would be done IRL Getting waved off on final just to have a plane pop up on deck shortly before sucks. 2) detect jams/deadlocks and try to remove the blocking plane. I would rather prefer this than starting all over. I believe this would still cause an acceptable flow in most cases in particular with liberation missions in mind 3) Implement some queuing before spawning. This is better than a complete blockage and would still allow a good enough flow in busier missions if isn’t timed too crazy of course.
×
×
  • Create New...