EasyEB

Reference photos: SUU-25 on station 3: http://4.bp.blogspot.com/_VGm_KikuffQ/SPDsdC1d25I/AAAAAAAAAEo/B6TV6SI89ro/s1600-h/060130-F-9999K-002.jpg SUU-25 on station 9: https://upload.wikimedia.org/wikipedia/commons/c/cd/A-10_-_32156159151.jpg SUU-25 on station 3: http://3.bp.blogspot.com/_VGm_KikuffQ/SPDsT1t1RRI/AAAAAAAAAEg/PR2YrSiN6Xw/s1600-h/060130-F-9999K-001.jpg

The SUU-25 flare launcher model is missing. Before it turned invisible it was in bad need of a visual upgrade so here’s my request for that aswell! Keep up the good hard work.

I think ED should rip the band aid and kill the old version when the new one is releasted. They are having trouble keeping one version running smooth as is, so having two just seems like a bad idea. There’ll be some initial whine from a handful of people but looking forward it’s just not feasable to keep giving the old one CPR just to keep up.

Is there any workaround for this game breaking bug while we wait for the patch?

Wow this bug is a real killer. I did a complete wipe of DCS and did a clean install and I got it again first playtest. Glad to hear you may have a solution. Let me know if you need help with testing the build, this bug kills DCS for me every single time. dcs.log-20200502-103327.zip

You need to re-run the script every now and then to update the Reapers orbit point. There are multiple ways of doing this. You are exactly where I was a couple of years ago. I highly recommend start using Moose as soon as you can. If you want to look at some different AI control functions the download Operation Titan Angel, start the mission and launch a Reaper and see what it can do. If you like a certain function then just dissect the mission code.

Again. dcs.log-20200501-172931.zip

They are. They’ve said so multimple times. Don’t be hyperbolic.

I can understand that. I’m trying to pin down exactly what causes it but its hard. DCS crashes every single time i play now, 75% is this bug and the rest are CTDs without crash logs seemingly out of nowhere. Once after resuming after a ten second pause, once when arming the countermeasures on the A-10C, once when turning sharp and a bunch of times just out of nowhere.

I'm starting to see a pattern where the game crashes when there are ground units (vehicles and infantry) move, stop and/or unload infantry near or on bridges. dcs.log-20200501-104608.zip

Moose script: function Reaper1GroupOrbit() local RTGroup = RedTargetGroup local RTUnit = RTGroup:GetUnit(1) local RTPointVec2 = RTUnit:GetPointVec2() local RTVec2 = RTPointVec2:GetVec2() local Reaper1Orbit = Reaper1Group:TaskOrbitCircleAtVec2(RTVec2,3352,200) Reaper1Group:SetTask(Reaper1Orbit, 1) end For non Moose, look here: https://forums.eagle.ru/showthread.php?t=167439&highlight=reaper+orbit

Whats so frustrating is the randomness. Sometimes it works, and then its back again. I feel I might aswell sacrifice a lamb or do a rain dance and pray it works.

Start dcs. Create new mission. Place A-10C. Make A-10C player. Give A10C payload. Give A-10C waypoint on ground. Place enemy vehicle on waypoint. Start mission. Fire missile at enemy vehicle. Wait and see if the problem persists. Problem persists. Exit DCS. Delete fxo and metashaders folders. Start DCS. DCS frozen on logo screen. Ctrl-alt-del. Close DCS. Start DCS. DCS frozen on logo screen. Ctrl-alt-del. Close DCS. Start DCS. DCS frozen on logo screen. Ctrl-alt-del. Close DCS. Start DCS. DCS frozen on logo screen. Restart PC. Start DCS. DCS frozen on logo screen. Ctrl-alt-del. Close DCS. Start DCS. Create new mission. Place A-10C. Make A-10C player. Give A10C payload. Give A-10C waypoint on ground. Place enemy vehicle on waypoint. Start mission. Fire missile at enemy vehicle. Wait and see if the problem persists. Problem persists. Exit DCS. Delete fxo and metashaders folders. Start DCS. DCS frozen on logo screen. Ctrl-alt-del. Close DCS. Start DCS. Create new mission. Place A-10C. Make A-10C player. Give A10C payload. Give A-10C waypoint on ground. Place enemy vehicle on waypoint. Start mission. Fire missile at enemy vehicle. Wait and see if the problem persists. Problem is gone. Start real mission. Game crashes after 26 minutes because of bowwaveemitter error. Start DCS. Create new mission. Place A-10C. Make A-10C player. Give A10C payload. Give A-10C waypoint on ground. Place enemy vehicle on waypoint. Start mission. Fire missile at enemy vehicle. Wait and see if the problem persists. Problem is back. This is how I spent 1 hour and 20 minutes of my two hours of spare time today.

Yeah, for me too for a couple of weeks. Now the problem is back with a vengance and appears even when chimney smoke is set to 0.

I have a mission where it happens regularly, not that I can reproduce it easily but I’d love to help out with testing. Let me know.

WARNING EFFECTS2: BowwaveEmitter: unknown parameter Keeps showing up. Tonight I observed some ground units (vehicles and infantry) near water. Maybe it's when they step into water?

Game keeps crashing guys. dcs.log-20200427-180919.zip dcs.log-20200426-095137.zip dcs.log-20200418-101559.zip

2020-04-25 17:26:38.961 WARNING EFFECTS2: BowwaveEmitter: unknown parameter I keep seeing this in my crashes, happening often. Way too often.

The text on the bar above the G-meter displaying manufacturing date and serial number (?) upside down is backlit, controlled by the Console lighting.

For me the TGP is completely washed out if there is any smoke (from burning vehicles) visible in the TGP field of view. As long as I don't point it directly at smoke it's fine, but as soon as the smoke gets in view the TGP is washed out. Completely white in WHOT, and completely black in BHOT. Adjusting brightness on the in MFCD does not help at all. The view is normal as long as there is no smoke visible.

I’ve got the code for it but not at computer atm, but basicaly you make a script that gets the target groups position every minute or so (faster is not needed) and orders the reaper to orbit that point.

The left engine of the A-10C generates a thin exhaust smoke trail while the right engine does not.

So I can’t seem to get a modified default head position to work. Can someone please babystep me through this?

Yeah it’s been more than a month. I wonder what happened?

Yeah, no.