boerdi

Well, the idea was to force a freeze to find out if disabling Tacview made a difference. Most of the time I browse "normally" through units to see what's up on the map or to check if the carrier deck is free. But I also had freezes happen in cockpit, e.g. landing on carrier, turning on deck to park and bam, freeze. My current preload radius is 150000 On my system, browsing through units is rather fast and usually no problem. Even on a busy MP server. The freezes have always shared these traits: - MP server with at least a couple of players up to full server. - Proximity to carrier. On deck or in a 20-40 nm bubble around it. - AI Tomcats in the vicinity. - With one exception to the presence of AI Tomcats: Game froze once on Hoggit GAW (Caucasus) with no AI Tomcats present (in phase 1 of map). But in phase 2 of the map there is a possibility that they pop up on carrier deck or around carrier trying to land. So there is a possibilty that these Tomcats may be buried (non-activated) in the mission file even in phase 1. [edit] I'll throw in my examples from July again: [edit 2] Here is another example of in-cockpit freeze I had on Hoggit's PGAW (with AI Tomcats) without F2 "browsing" Freeze at end just after raising the hook and turning my head to taxi off the landing deck.

Did some testing over the past two days. (As stated in my previous post, file integrity has been verified by Steam) Disabled Tacview and joined MP servers with known AI Tomcat units (alternating between Hoggit PGAW and Flashpoint Levant). Trying to force a freeze by joining the round normally, doing one or more missions and while en route "browsing" through the other air and naval units (players and AI) via F2 and F9. Including camera movements around the units. Disabling Tacview gave of course a FPS boost and I played many missions on first day without a hitch. That gave me hope and that streak continued today until now. Freeze happened again on Hoggit PGAW (early game with most bases still uncapped and AI Tomcats over carriers doing CAP): Flying in Hornet. Taking off from Washington. Did two sorties (with a landing on carrier to rearm and refuel) taking out two tracking radars. All the while "browsing" through the other units. On the way back to the carrier (I think I was around 20 nm from the Washington) the game froze during camera movement when F2 hopped to a player Hornet at Al Dhafra. Detailed log attached dcs.log

Tacview and SRS? When the 2.8 update finished, the purity check thing in the MP server browser showed me that the countermeasures LUA of the Hornet didn't pass the integrity check. It's the only file I modified by hand to save my custom Manual 1 and 5 programs for flares and chaff. I had the original file saved and wanted to revert to it but I lost SA with my file naming and deleted of course the backuped original. This led to a repair process/integrity verification on Steam to regain the original file. So the game's integrity has already been checked after 2.8 update. The freeze happened shortly afterwards. For completion's sake, here are my specs: DCS Steam Edition Addons: Tacview and SRS No mods Primary plane: Hornet Do I own the F-14 module: Yes Specs: i9-12900K 3090 Ti 64 GB RAM DDR5-5200 (MemTest: zero errors) Audio: Soundblaster X4 (USB) DCS installed on 2 TB M.2 NVMe drive OS installed on 1 TB M.2 NVMe drive Windows 11 OS and all drivers up to date (afaik)

Sadly I just had another AI Tomcat freeze with 2.8

No luck with 2.8 Got another F2 camera freeze while viewing AI Tomcats on MP Server Screenshot is grabbed from Shadowplay showing the frozen last frame Detailed log attached dcs.log

Potential fix incoming. Let's hope for the best!

Fingers crossed!

And again... Game freeze on MP server (Hoggit GAW) while F2 viewing AI Tomcat trying to land on carrier (Roosevelt). I took the screenshot out of reflex and the game froze a second later after turning the camera to get a side view of the AI tomcat Detailed log attached pro forma dcs.log

Yep, just like the freezes related to the AI Tomcat (c.f. this big thread with problem acknowledged by heatblur) Image freezes, ambient sound on loop and then the process has to be killed via task manager. Difference is that there are no AI Tomcats in the air. Or SHOULD'NT be. I don't know if there may be some hidden/forgotten AI Tomcats buried in the server's mission file. In phase 1 of the mission on the GAW server I have never seen an AI Tomcat, but in phase 2 there is one that sometimes pops up on the carrier deck.

Session fresh out of the oven: 42 minutes on Hoggit's Georgia at War (phase 2) without a hitch. CAP (6 airkills). Departure from Kras-Pash and landing at Sochi. Log (detailed) attached. dcs.log

Hi The freezes are VERY random. Usually I can play without any hitch on MP servers, even flew a nice sortie yesterday on that server (launch from carrier, kill a ground target and couple of bandits, return home to carrier and land CASE I). And theses freezes "happen" and "feel" like those related to the AI Tomcats, although there are none present in the air at time of freeze. [edit] The install is also rather "fresh" But I did the integrity verification: no major problems. The process only replaced the lua files that include the default the airplane loadouts (i delete those entries to clean up the rearm screen)

And again a random freeze... same server, same map/phase... Attached log to this post and added everything else to the Google Drive link (Minidump, Tacview, Track...) Just like an AI F-14 freeze but there are none around. Hidden/forgotten leftover units in the mission file? Or has my system a quirk? Buzzkill deluxe dcs.log

Greetings, Due to the AI Tomcat freezes I stuck to MP servers without those units (e.g. Hoggit's Georgia at War) Just now I had a random freeze on GAW, a server which was never problematic in the past concerning game crashes. In phase 1 (when the freeze appeared), the server has no AI Tomcats (afaik). Although I spotted AI Tomcats in phase 2, they just pop up on the carrier deck and disappear again. I am not sure whether there are any "hidden" Tomcats somewhere or if my game/system simply has another problem. -> Here are the detailed log, track, Tacview and Process Explorer minidump files DCS Steam Edition Addons: Tacview and SRS No mods Prior to this, DCS has been started several times for MP sessions during the day without problems. Specs: i9-12900K 3090 Ti 64 GB RAM DDR5-5200 (MemTest: zero errors) Audio: Soundblaster X4 (USB) DCS installed on 2 TB M.2 NVMe drive OS installed on 1 TB M.2 NVMe drive Windows 11 OS and all drivers up to date (afaik)

Can confirm that freezes also still happen on MP servers (e.g. Hoggit PGAW with AI Tomcats) Just landed with the Hornet on the Washington in "carrier corner", F2 viewed another Hornet on the Stennis during refuel/rearm and game froze. Two-ship AI Tomcat patrol nearby in the air. This is a fresh DCS install on a new PC. Freeze identical to those on the older machine. Detailed log attached. dcs.log

To be able to enjoy MP, I only joined servers with no AI Tomcats. Last couple of days I tried joining Hoggit's PGAW again and kept to the western side of the map, not taking off from one of the carriers in the east and staying "out of visual range" of the friendly AI Tomcat patrol. Things looked promising and I had no freezes doing CAP and AG stuff in the western part. Even engaging the Iranian AI Tomcats didn't cause a problem in several rounds. That changed today when the game froze again... An Iranian AI Tomcat fired a Phoenix at me and I went defensive when the game suddenly started stuttering like hell and FPS dropped to single digits and then became slide show with a frame every couple seconds until it froze completely. I did not even view any Tomcat with the external cam, it seems to be the mere presence (in visual range) of an AI Tomcat that starts spinning the "will-DCS-freeze-or-not" wheel... Here is the log (detailed mode enabled):dcs.log It's really super frustrating

After the last Open Beta patch I thought the freezes had vanished. Was able to play longer on MP maps with AI Tomcats. Sadly, the freeze struck again today Zero freezes on Hoggit's Georgia at War (no AI Tomcats and I played really often and long today). But on Hoggit's Persian Gulf at War the game froze once again near the patrolling AI Tomcats in the south-east "carrier corner". Here is a link with detailed log and Process Explorer mini dump of the crashed DCS process (if it helps): https://drive.google.com/drive/folders/1oAn7raGpQU2FTkW0RcB1m84cpI2cKfgf?usp=sharing

Found this thread just now. Experienced same issue flying the Hornet on multiplayer servers with Tomcat AI fighters. More details in this thread (including videos/basic logs at beginning and extended log/memory dump in post #4) No mods

Oh thank you! Seems plausible with what I experienced. I can reclaim bits of my sanity again But also a bummer... entering the "when will it freeze?" lottery when flying near (or viewing) those planes. If I remember correctly, I also had a freeze on the Flashpoint Levant server (Syria map) with friendly AI Tomcats patrolling along the coast. But that was some time ago and one of the first ones, so I dismissed it as a really random game crash. And I am 99% sure I never had a freeze on Georgia at War (Caucasus). No friendly AI fighter aircraft involved there. [edit] Found your thread on the same issue Cheers!

Another session, another freeze Game ran a bit longer this time though. BVR in the north and landed in Khasab but the game froze when I externally viewed the Tomcats over Carrier Corner... Before this session I enabled additional debug info and started process explorer to get a mini dump (following these instructions) Attached is additional debug info And here is the mini dump of the DCS process after freeze: https://drive.google.com/drive/folders/1pGTniJrp_o9GuptUi3-zZdPBpGOo-Wc7?usp=sharing 2022-07-12 - PGAW carrier corner - example 4 additional debug.log

I disabled Tacview. Game ran a bit smoother (as expected). Game froze again though (crash log attached) Just for context, what I did up to the freeze: Tried to force the freeze as soon as I spawned on the carrier without starting up aircraft. Nothing happened, so far so good. Took off from Washington heading north to suppress/destroy SAM. Dodged Iranian Phoenixes and shot down a MiG-29. No joy with TALDs and HARMs, the land and naval SAM sites were too numerous and I returned to the Washington. On the way home I "browsed" through all the carriers with the external cam. As soon as I viewed the Kuznetsov and turned the camera, the game froze. It's like an asset in that cursed corner that makes the game go nuts... 2022-07-12 - PGAW carrier corner - example 3.log

Greetings, It may be oddly specific but this problem is bugging me for some time now. Where does it happen: on Hoggit PGAW (Persian Gulf at War) multiplayer server in a certain corner of the map. And I don't know if it's my system, DCS itself or a quirk of the MP server. In the past it sometimes happened when I landed on the Stennis or Washington located in the south-east corner of the map. Recently it happened again during a Case III recovery on PGAW (freeze happening at end of video). Sadly, I didn't save the log file for this one I was able to replicate the freeze like this (crash logs also attached to this post): Video Example 1 - Crash Log Video Example 2 - Crash Log Prior to the freeze I am able to fly a sortie and blow some stuff up. After landing on one of the carriers, I check the surrounding ships and AI planes with the external cam. In this case the freeze happens when I view other planes and turn the camera. No mods installed Between examples 1 and 2 I tried a repair (Steam verification of file integrity), to no avail. I do similar stuff on other maps on other servers (e.g. Hoggit GAW [Caucasus] or Flashpoint Levant [Syria]) and no freezes happen. My PC specs: i9-9900k / 2080 Ti / 64 GB RAM (DDR4-3200) / Asus ROG Maximus XI Hero [RAM has been tested with MemTest86 and passed with zero errors] Windows on 1TB M.2 NVMe (pagefile with default settings and managed by OS) DCS (Steam) on separate 2TB M.2 NVMe OS and all drivers up to date Best regards DCS Freeze - PGAW Carrier Corner - Example 1.log DCS Freeze - PGAW Carrier Corner - Example 2.log

Greetings, Discovered this in a MP training session and was able to recreate it in SP Switched to a super heavy loadout to see if I could take off. As expected, flight was barely possible. Switched back to lighter loadout. The flight controls went out of whack in that moment, as if a heavy mass was still clinging to the right side of the Apache. SP track file: https://drive.google.com/drive/folders/1O1a0RYgvIyMyOI_jv6lktn70US6FzRYU?usp=sharing Recorded the test in SP:

Received my Orion Throttle (base + F/A-18C handle) this week. So my impressions are very recent but maybe helpful. A bit of context to explain where I am going with my thoughts: DCS: I fly only the Hornet at the moment, maybe the F-16 and/or A-10 later down the road. Space Sims: I played a lot of Elite Dangerous but DCS took that spot But the itch for space flight is always there, be it Elite or maybe Star Citizen I was (and maybe still am) on an odyssey to find the throttle that fits my needs the best, so I have here at home (in order of acquisition): - Thrustmaster TWCS Throttle (my first) - Thrustmaster Warthog Throttle - Virpil MongoosT-50CM3 - Winwing Orion Thottle (with F/A-18C handle) I try to summarize my experiences and preferences as brief as possible: Thrustmaster TWCS Throttle Pros: - The complete HOTAS set is great for starting out on a budget! (if you can find it for the adequate retail price) - Buttonwise you are flexible and I never had any issues with malfunctioning buttons. When something started to act up it was always the joystick. - Rudder pedals Cons: - USB cable cannot be unplugged from throttle - No detents out of the box Neutral - The build quality/feel is more than ok but cannot compete with the higher level throttles. - A bit of better grease on the throttle helps to improve friction/smoothness. Easy to apply. Thrustmaster Warthog Throttle Pros: - Good overall chunky feel - Good direct button feel (except the ministick... c.f cons) - Good weight/stable - The detents (and lifting up) took some time getting used to but are reliable. No accidental engine cutoff etc... - I think I like the mechanism to lock the handles together on this throttle the best. Easy to reach and open/close. The handles also stick nicely together. Cons: - USB cable cannot be unplugged from throttle - The slew ministick for the TDC is... hmm... suboptimal. I changed that one for the Delta Sim Electronics upgrade. Worth it! - Many switches are the wrong "type" for the Hornet and I left many unused - Would love a "push through" detent for afterburner instead of the "lift handle up" out of the box - Getting the throttle/afterburner positions right was a bit finicky but you can google the fitting user curves for the Hornet Neutral: - This throttle will definitely be used if I start flying the A-10 Virpil MongoosT-50CM3 Pros: - USB cable can be unplugged from throttle - Great overall build quality - Handles have a nice chuncky feel and stick nicely together. No wiggle - Versatile adjustable detent sets and friction - Very high number of hats, switches and buttons... (maybe even a bit too many?) - Definitely great for space sims. If I return to Elite or start Star Citizen I would use this throttle and put the detents in "Space Mode" Cons: - The type of buttons/switches are also not optimal for the Hornet. Couldn't find a suitable layout and left many buttons unused. - The LED buttons in the 3x2 field feel a bit "squishy" and you have to really hit them at the right angle for the button press to register Neutral: - At first I was overwhelmed by the sheer number of buttons, hats and switches - Takes some time getting used to the presence of that many hats in the zone where your left fingertips rest on the handle - The handles are quite big. Definitely bigger than Thrustmaster/Winwing. Winwing Orion Thottle (with F/A-18C handle) Pros: - USB cable can be unplugged from throttle - Good overall build quality. Just a tad below Virpil CM3 - The detents have a very satisfying "chunk" - Perfect handle button layout for the Hornet (duh) - Overall button/switch quality is good (c.f. neutral) - Good ministick for TDC slew out of the box Cons: - The detents are fixed (not a problem if you use it for planes like Hornet) - The mechanism to lock the handles is not as easily reachable as the one on the Warthog throttle - The handles don't stick as nicely together as the WH or CM3. A tiny bit of jiggle, not a deal breaker though. - The park brake switch makes no sense for the DCS Hornet - The rotary dials for HMD, HDG and CRS are quite slow (or I haven't found the right setting yet) Neutral: - Not sure about the longevity of the cables connecting handles and base. Time will tell - The buttons for countermeasures and radio on the handle could be a bit more "direct" for my taste - The HDG and CRS dials are used for the radio channels at the moment - The additional F-16 and A-10 switches are nice to have but I have to find a suitable use yet. - Also had the issue where throttle movement influenced the neighbouring slider sensor mapped to the zoom axis. So that throttle movement messed with zoom. At the moment I do not use any of the sliders. Zooming is done via the countermeasure switch on the handle (slow zoom in/out and zoom reset). Countermeasures are fired via joystick. Mkay, I went a bit overboard there

Ordered F/A-18 Orion Throttle on 22 December Destination country: Luxembourg Received shipment notice on 5 January Estimated delivery on 13 January [edit] Part 1 (throttle base) delivered early on 11 January Part 2 (handle) delivered on 13 January