homepage Forums Air Combat & Civil Aviation DCS World Eno's Firehouse and Crew's Hollo Pointe Server Lounge

Since we all want to complete missions - especially with the fly in approaching I've been doing some reading in the A-10C manual to look for some useful information regarding targeting that can hopefully expedite our attacks. You guy's aren't military nuts that demand proper radio protocols and the like but it would help if we have something better then "a few miles up the coast near the trees on a hill"!

First would be coordinates - if possible provide MGRS coordinates (easier then long/lat) can be set to show on F10 map instead of long/lat. This only really helps the A-10Cs though, using the CDU and TAD to make a waypoint at those coordinates. Next is bullseye / 'bulls' which we hear the AI spam at us over comms. You can range this on the map with the ruler - so it'll work for anyone. In the A-10C you can have the TAD show your own and/or target's location relative to bullseye. TAD information starts on page 303 of the A10C manual. Bullseye is explained starting at the bottom of page 307.


The next thing I'd actually like to test (unless it's confirmed working or not already) is Datalink usage in MP - obviously limited to the A-10C. The manual states that we CAN send target data between aircraft, if this works - it would be great! Have one A-10 go TGP only, maybe tanks too, and circle high sending enemy locations to the other A-10s! This is described on page 318. Part of this would be remembering who picked what own ID's to know who to send it to. However, part of the selection process displays callsign which we can also set - so I'd show up as WES (I often set mine) and everyone can pick a name (4 characters limit) for quick ID.

If anyone wishes to take it the extra mile, ground commanders/jtacs could issue 9 lines. Outline on page 646 of the A-10C manual an also on page 17 and 18 (pages 29 & 30 in the PDF) of this US military document. - J-Fire
This can be made easier by using the MSG page in the A-10C which is supposed to work aswell, page 355 of the manual.

---

Thought I'd provide that, we could implement it if anyone would like to - to whatever extent best fits. Hopefully this can help us cause more damage, in less time!

MGRS works very well for everyone.

The A-10C Datalink works very very well. We typically use Group ID = 11; Own ID = Nose Number/Slot Number. Only one A-10C in the group should be broadcasting the SPI so it is not confusing. The callsign is a neat feature.


I need to brush up on creating a Flight Plan from Mark Points. Was in Zesti the other day as Blue and trying to triangulate the SA-15 in the middle and not doing too good.

It would be interesting to see/track over time... Well I wasn't sure about exclusions or not, I guess its never really come up till the other night.




There are a couple of us that play all the time and we'd be more than happy to walk you through it TS3. Its very helpful when hunting an elusive target group.

Last time I checked nicknames weren't working but I haven't looked at it for awhile. As mentioned already Wes, we do frequently use the data link feature and the normal Group ID we use is 11. Even if you're on a different ID, if memory serves when a guy is transmitting data for a SPI I'm not sure you can hook it but you can see what network and what ID he's using (there's a 4 digit number near the target data- mine would be 1175 for example).

Quite some time ago we also developed a long list of "own IDs" that you could use to folks on the TAD. I think it's on the first page of this thread actually... So if you usually fly with a particular number we can post it.

The MGRS coordinates are also in use- however the guys in the A-10s usually just use SPI sharing (the only platform I use)... Some guys got really good with coordinates but I was always a bit behind with it. Distance from Bulls works too but I'm not sure if Bulls is placed on the map of any other platform?

I've taken to bringing a 7 shot of WP as well... which I find has been REALLY nice and quick at identifying targets for the other platforms. I often think of real situations in the field where an enemy unit is sitting there with their heads down, listening to the A-10s circling overhead as the pilots look for them with their 12X gyrostabilized binoculars...

Then that smoke round lands 50 feet away... then another 20 feet away on the other side of them... it gets very quiet-

And then the world is turned inside out.


Anyway- as you also stated we're not hardcore but there are guys in there always looking forward to learning something new as well- I think I learn a little something about the aircraft every time I fly... that's why I love it so much!

Absolutely.. there is a REALLY impressive FAC video on youtube and they are only using WP and directional bearings.

Link or it doesn't exist!

please standby as we process your request....


edit: it may be harder to find than I expected. I can't really look for it while I'm at work.

Standing by...

Made some additional adjustments to Killbox and I think I have a good thing going- except that we tried running it twice last night and had some "transport.dll" issue that prompted a change in missions.

We jumped into Wartweasel after that and it seemed to run smooth- I quite like how the command posts sort of sneak into position- but if you can nail them first then it fast forwards you to the next phase of the operation very quickly.

Still haven't seen that yet.

I'm wondering if some types of unarmed vehicles cause instability- I might have to try different types of civilian transport.

Another thing I've noticed with some MIST functions is that things happen on the server- but then they aren't captured by the clients... unless the clients leave and come back. Whether that's what's happening with some of these commands, I'm not 10%

Last night I was talking to someone about how it was that my HOTAS controls weren't sync'd between the game and my existing configuration. I had to put the throttles over the "edge" for example twice before I could get the engines to turn on. The other issue we were having was the GCAS switch- as it was set to NRM on my Throttle quadrant but didn't sync up in game. As a result, I had to turn it off, then back on again... then it worked fine. I must admit, I used that A-10 Ipad ap to figure it out... as it has a good "emergency procedures" menu that takes you through what you need to do for all warning light activations in your cockpit. Apparently it isn't available at the ap store anymore... at least last I heard. For those of you who don't already have it, it's a valuable tool!

Someone else in there at the time mentioned they had the same problem- and the reason (I think) was because there is a setting in MISC in the options section in the SP side of things that gives you an option to "Sync cockpit with HOTAS" or something to that effect.

Evidently, the stock value is "off." So to whomever it was, I urge you to go check that out! Perhaps it'll make the difference!

Eh guys. Had fun last night. Going to need to learn a bit more about the ground commander role, obviously- not to mention the JTAC... however it was great fun and I really enjoyed it.

Anyway, something that came to light last night was that pings over 200 are causing warping when we get about 5 or more people in there. For those of you who are just perusing through the thread and decided not to read back 300 pages, I thought I'd mention that a new stipulation (to the Firehouse anyway) will be a ping of less than (or at least very near to) 200.

We had a couple guys from the UK in last night and one was in the late 100s and another was around 250 or so... I posted a request for the individual to leave but didn't have the heart to kick him. I don't want to kick people for just being too far away- and I HATE that we're being put in a position to have to do it.

So please... if you're seeing your ping constantly above 200 while you're in the server and the number of players starts to get up there, I'm going to ask very politely that you be considerate and head over to a server closer to you.

raven and I flew in Hollo Pointe last night and both got booted with a Server Ping Timeout, and the server had a DCS Stopped Working message - first in a while. I had just jettisoned my Mavs and GBU-38s in favor of guns and rockets in a canyon when the crash happened.

Got back in to Huey Apocalypse and did not fly long when we noticed lagging. I checked our pings and mine was at ~320 and climbing one tick per second -- raven's was at like 1100 ,, huh? Had seen this before, but not in a while.

This morning, raven loaded a mission with -admin load and that also caused a server DCS Stopped Working message.




I did reboot the server. This week I will upgrade it to Win 8.1 YIKES

Eh guys.

Got a new aspect added to EB+D. We were able to complete it with VERY little work from our side... the ground forces weren't even involved. I credit good team work and aggressive attack on the part of the aircraft.

But... if I'm going to keep AI down- I need to keep intensity up.

So I've added another aspect of the mission. An HQ... similar to that included in a mission we haven't flown hardly ever- Operation Snapshot. It's located somewhere out there... and it will be moved around. The concept is a flight of A-10s and SU25Ts are going to need to team up and go to work.

I've reconfigured the attack so it comes on a bit faster and less predictably- so you will have your work cut out for you... going after the HQ is something you do when you have the offensive under control.

I looked around a bit for the issue me and near-blind was having with the anti radiation missiles against the SA-8 OSA but I found nothing on the Ed forum.

I think the radar emissions were so strong they detonated the anti radiation missiles as soon as they armed. Which would explain them blowing up right in front of the plane. We had no problems killing tungs or Buks only the Sa-8s

http://forums.eagle.ru/showthread.php?t=105434&page=17

Found it... Lol

eh.. i still haven't had free time to find that video ENO... Maybe today

No problem blind- I was mostly kidding but if you stumble across it then great!

I noticed a couple of crash logs from last night... I saw the effects.dll one again and I'm assuming that was from wartweasel since it's the common one- when busses start blowing up.

Mol left me a note last night on the server rig- but it looked like there may have been a second crash... anyone see anything?


Thought I'd post up the series of photos from Sweetest's mural... I continue to be pretty stoked about it.









Granted, slightly different light in there now since we decided the other lights we were using were a bit too dim.

It was a good find, but i can't replicate the same search i used before... oh well.

liking the painting a lot!

is the TeamSpeak downtime gonna effect the flyin?

Skate,
We do not expect it to.

We will ask for a replacement TS server (or two) for that w/e. We need a TS server that can handle ~50 users, or two that can handle ~25 each.

Look for a post in a bit.

WC

FINALLY figured out what was up with Killbox Zulu Romeo...

At least, I think I did. Had something to do with the use of script too quickly after mission start. I've also made a few changes- added a red ground commander with enough armour to do some damage... and given a task to FARP CARGO MI8s. Basically, they need to get 4 loads of supplies into ANAPA- and yes, that's a bit of a long flight but the benefit is that each time they get a load in, the blue ground commander gets one more group of either Strikers or Abrams (Max 4 loads needed). IF they succeed in getting all 4 loads to ANAPA, then the US can jump to an early offensive and go mop up all Russian units.

Red GC's objective is to get to ANAPA and destroy all forces at the airbase- but he's got a bit of a long trek ahead of him. The trick is going to be in getting there while being feverishly hunted by A-10s, SU25s and KA50s.

Whoops- spoke too soon.