dcs.logHaving essentially the same issue still... tho my most recent attempt did turn up a different result, though, still a failiure to load. Instead of loading partially, then saying "Mission Load Fail" and promptly locking up, requiring a force quit from task manager to close DCS, as has been the norm for all my other tracks. This one loaded only about 1/6 of the way before blanking the screen and displaying the error message "C:\Users\*my username*\AppData\Local\Temp\DCS.openbeta\tempMission.miz:Unexpected end of track fiber track/net : idx = 10510, time = 1978.003000, missing at least 53382961 bytes". After copying the error code and clicking "ok" on the error pop-up, the game locked up on a black screen and again required and task manager force quit to escape. Log file is attached.
Honestly, ED, the first post reporting this issue was made in December 2023. It is now February 2025. That's over a year for those playing at home. This issue has still not been solved. IN OVER A YEAR. In that time, ED has released no less than TEN pieces of paid DLC. TEN. Nearly all at over 60 bucks a pop. With all the work going into making content that people will pay to access one would think there's at least an equal amount of effort going into back-end bug fixes and core game improvements. But considering that game-breaking issues like these which completely disable entire features of the game has gone unsolved for OVER A YEAR while TEN new paid DLCs were released, I have a funny feeling that there's essentially no resources going towards core game improvements in comparison to how many resources are going in to making paid DLC. And that, in my opinion is a real shame, and, in fact, is a pretty scummy and pathetic way to run a business. I read through this entire thread and the few messages put here by ED say nothing more than "external scripts don't seem to work". Yea, no <profanity>. My question is WHY? WHY do scripts (which are an advertised tool that is included in ED's own mission editor) completely break replays? WHY did they work before Dec 2023, but not since? And WHY is ED not putting more resources into fixing this, when its their OWN DAMN SCRIPTING FEATURE that's broken. Its not like its some third party plug-in that isn't made by ED that's breaking it. Its their own damn mission editor.
Maybe the issue is so ingrained within the replay system that it would require a complete redesign to fix the issue... you know what I say to that? GOOD. Even when its working, the replay system we have where they literally just spawn everything in their starting positions and play back everyone's inputs is an archaic, inefficient, performance hogging, barely adequate way of doing things that badly needs to be completely trashed and replaced with a real replay system that lives up to modern standards. Sure, DCS is an old game, and many of the under the hood things are old too, so such drastic modernizations may be difficult, but that's ED's own damn fault. They could have been incrementally updating core features as they went, but NOOO, they decided all that mattered was content, content, content. And now that the game is so pathetically bloated and data-stuffed (381 GIGABYTES, what the actual <profanity>), and is being held together with gum and toothpicks, we're supposed to be understanding of how hard it is to make sweeping changes to outdated systems that they allowed to get freakishly outdated. I freaking love DCS and there truly is nothing like it, but cmon ED, you can do better than that. I believe in you.
