I'll be on about 1815 MST.

Mol... Tough flying against you last night. It was pretty overwhelming being on the blue side of back to school last night. I wish I could have stayed on and fought a bit after taking out the OSA.

Eno, won't be around to help test the mission tonight. Good luck!

Agreed. You haven't been truly vulched until you've sat through 5-10 minutes of system prep and weapons programming in a DCS A10 or KA50,
THEN GET BLASTED ON TAKEOFF!

I don't know, maybe that's how real war is.

I didn't last long after you left. I didn't really go after any A-10s I was interested in testing the Cannon Pod to see if they fixed the glitch and test out all of Enos fixes... which were all pretty well taken care of. I have noticed that the SU-25 has a much closer fighting range than the A-10... A-10 you can stand off and then attack and peal off before you get within the minimum range of the IR missiles... But the SU-25 you attack and you are within minimum range of the IR missiles before you can shoot. the Flares seem to wokr better on the SU-25 though. or so it seems.

Hi Mol,
I've also been testing the SU25T on some single player-made SEAD missions. The KH 25mpu and 58 really do a great job from mostly standoff range.

Question for you- the RWR in the my SU is totally silent. Do you have any audio on it?

UPDATE: Problem fixed by turning up "In Cockpit" volume to 80% or higher in the World audio GUI.

I'd rock the SU-25 when the 6DoF Re-done pit is done.

Mine does but its fairly sutle in comparison to the A-10's blaring RWR.

I do get the blips from the patriots and distant big birds. Also the missle launch indications are not as pronounced as A-10s

The way the Manual appears the Beryoza system doesn't handle multiple indications well. Becuase it separates them into Primary and secondary. Either way a Low pitch tone indcates a aquisition spike... while a Lock tone is high pitched tone.

The SU-25T manual goes into some detail about the RWR in the SU-25 I haven't spent alot of time reading it ... just kinda took an overview of it and hoped that On the Job Training would fill in the rest.

Eno!

Check this out -
http://forums.eagle.ru/showpost.php?p=1590249&postcount=21

M O O N spells Moon!

WC

Mol, wish I could have stayed on a a bit longer but my cutoff time is usually 10pm Mountain.

I enjoyed the challenge. For me personally, the A10 sucks as a defensive aircraft.

I did something slightly different when loading a new mission this morning.

Previously I would back completely out of DCS, and restart the DCS Multiplayer to launch a new mission.

This morning I Disconnected but did not Exit the server - instead I started a new mission from the list. It is still running some nine hours later.

I do think Windows 8 has improved the memory handling for DCS.

WC

or DCS Fixed some memory leaks they had in WDDM 1.2

Don't see it yet @ 1830 MST

Sorry folks... had a bit of a late start here at work. Also had a few last minute adjustments to make...

It's up and running.




Eh Crew- yes I had seen that before but didn't understand the value. Not coincidententally I chose a day with no moon and relatively long dark hours... thanks to that log.

It really is an invaluable resource when you're considering weaving such things into the plot of your mission!

Hey Eno tried out Snapshot and found that you could only get about one engine started before we got straffed by a mig 29 so thats as far as we got.

out of 3 of us we never got one A-10 in motion.

Oh weird. Back to the ol' drawing board. Sorry about that guys- but thanks for going in to check it out. I took a bit of a gamble rolling it out in beta to the group instead of flying it myself first a bit... my biggest thing is if I'm home flying I'd rather be flying with you guys instead of stuck in my own mission alone. Anyway, I think I fixed the issue.




I was under the impression that if you turn your group AI on later with a trigger that it's not on until activated... I didn't have "late activation" checked.

I'm hoping that was the missing link- so I went and applied late activation on all the things I had triggered... hope that works. If not, I'll have to go and turn the AI off with a flag at mission start. Again, that's not hard either...

Crew- any feedback on that setup? Basically I have a bunch of stuff that isn't supposed to "start" until certain zones are entered- I had "group AI on" set for when those points happen... but I can't do that for aircraft groups- obviously because otherwise they'd just be hovering in mid air.

On my second attempt as I was about to take down a comms tower the server crashed.

Eh Blooze... thanks for taking another stab at it. I went back in to see how you were doing and it was disconnected from the master server. Not sure if that was mission related or what that had to do with .

Now... when you say you were going to take out "A" comms tower... was it THE comms tower or just "A" comms tower?

If you found it that fast- I might need to make things a bit more discrete.

I've had better luck with ROE = Weapons Hold. AI On means to spin up radars like on the TOR and such. If you want a group to hunker down, put them on Hold and Weps Hold.

Even if your AI On is still valid for what you want to do, you still need to put the group(s) on hold first.

WC

Good question....it was a very large tower with a building next to it. I dropped 4 GBU10s before I finally got the laser to lase all the way down and hit it. It seems you have to approach from just the right angle and altitude to get a proper lase. Someone more experienced would probably have taken it down with one drop. I took out a few oil storage containers with mavs and directed Pipe to a group of warehouses before a SA15 nailed me. The briefing was right....when you start attacking it brings out some real nasty air defenses. I was hoping the other guys would come in from Hollo Pointe but they must have been too busy there. It's bedtime for me. I like the mission and next time I'll know better how to handle things.

Okay... well there are a few points you bring up above that are reassuring to me that I'm on the right track... and a couple things that I'll adjust.

Good:

1) You obviously hit something at some point that wasn't supposed to be hit which results in a lot of activity. I don't have that expanded around many areas that I'd like... but "bomb in zone" still doesn't really give me the function I want. I may need to enable slmod functions to get that effect in areas I want. I'd rather a "weapon outside of zone" feature for what I'm trying to do here.
2) We fixed the issue with the migs. As I stated I know what happened before and what I missed. The key is going to be in figuring out how to apply what I want the best way.

Bad (which for the purposes of building are still good):

1) There are likely towers throughout the area- but I don't think I expand on the target description enough. I think when I'm able to go in there and look at the buildings, screenshot them and load them into the mission brief... then you'll know exactly what to look for.
2) Once a target is identified, guys should be able to climb up past 5000 feet agl to do the drop. Once the target is located, there's no reason to stay down at 5000 feet. The 5000 feet is a minimum altitude... which I should have explained better.

The complexity in the triggers I'm trying to work out comes with a few different factors:

1) Flying where you're not supposed to. Assets will activate and CAP will launch to go and figure things out. I want these controlled by "duration" limits so that if they don't find anything, they go back to base and power down.
2) If the wrong target is hit... a stepped up response occurs from both land and ground assets- but now the response is prolonged and results in a mission fail.


I'm going to need to revamp my flags more into the code system that crew has established or develop one of my own. Suddenly I'm seeing the value of flag true / flag true / flag true conditions... so that if these three flags are true... then you get victory... or you get beaten down in defeat... depending on the flags. As silly as it makes me sound- I only just grasped how you can use a flag to define an event- and that future triggers / events can be measured against whether that flag has been set or not.

If these three flags are present / true... then your trigger happens to do one thing.
If two of these flags are true but one isn't... then you can set these conditions to a new flag... and countdown from THAT flag if the 3rd flag isn't made true within a certain time.

I was being VERY simplistic in my flag numbering- which was fine when I was sitting in front of the mission thinking... okay...444 will do here- but then a week later I'm going through trying to figure out what on earth flag I used where and why... I need a system.

Thing is- I needed to LEARN this lesson... having crew explain it as he does so well wasn't helping me because I didn't see the value of it. Now I do: Value = True!

lol