SizzlepopBACON

Hey yall sorry if this has been reported or asked about before, but I am not about to scroll through 250 pages of random stuff in hopes to find my question, which may not have even been asked before. Regardless, I'm having this weird issue with the Current Hill S350 assets where so much as having their location in my FOV will tank my fps down to unplayable levels. If I look away, fps goes back up. This happens even if the site is miles away behind mountains, where I would think the textures and graphics shouldn't be loaded... I haven't been able to get within eyesight of them because, like I said, unplayable fps even from miles away when looking at them. I'm not totally sure what's causing this... The obvious possibility is that loading their high quality textures and displaying them to too much for my poor computer, but given that this issue happens even when I can't actually see the units, just are looking in their general direction, I feel that's unlikely. In addition, this issue seems to only exist with the S350 units. All other CH units do not exhibit this issue... Is this a known bug? If it is, any suggestions on how to alleviate the symptoms? (OTHER than just not looking at them, which is not a very good solution lol). If it is a new issue that's not been reported, feel free to respond with whatever questions you may have. ED still hasn't fixed their <profanity>ty replay system so sadly I can't attach one. Well, not one that works... I have attached my dcs log file for the flight. Every few mins (I think every time I look in the direction of the S350) I'll get huge lists of the same error "ERROR ED_SOUND (Main): invalid host position(Shell-n) : [x, y, z]" so maybe that has something to with it? Thanks dcs.log

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.

Sorry, I forgot to save the track (silly me) so I'll have to go back in and run it again tomorrow... In the meantime I've got another thing to throw at you... Mission 5 - the attack on Al-Tanf, there seems to be a discrepancy between the map in the briefing material and where things are in-game. Particularly, the in briefing page that shows the location of waypoints 1-4 and the target area, the target circle seems to be moved south-east, further down the road of the actual in-game location. I'll attach a photo of both for your comparison. The first photo I attached is what is seen in the kneeboard/tablet thing and in the briefing (both in-game and in the doc file), and the second is the dcs F10 menu during the mission. I don't use F10 much when I'm flying single player cuz immersion, but I pulled it up after I died wondering where the heck the targets were, because I was searching based on the briefing material. In blue I circled where the briefing told me Al-Tanf was, and in red I circled the actual location of Al-Tanf in dcs... Weirdly enough, the briefing material seems to have a thinner circle over where Al-Tanf actually is, but the large "TG" circle is off by a bit. Just thought I'd bring to your attention in case its a mistake of some kind. If its intended, just ignore me! Thanks again, the missions are a blast so far.

I may be silly and if I am, please let me know. Mission two, task one where you need to land on the destroyer, I find my apache rolling forward on its wheels when I touch down. The first time it happened, I had forgotten to lock my tail wheel and apply parking brake again after takeoff, so I assumed that was why. But the second time I tried, I did both of those things and my aircraft still rolled forward, despite the parking brake being applied. It was a slow roll but even full cyclic aft and full wheel brakes did not arrest it and I bonked the nose into the back of the destroyer, and smacked the crap out of my main rotor... After flying that 45km flight at 100knots twice, ending with a buggy crash, I didn't have it in me to try a third time that night, so I looked around for a bit after to see if that was a known bug or something but couldn't find anything. That's making me think I did something so any tips would be appreciated. Trim was neutral on touchdown btw. Thanks!