shyjonathan1588

Something definitely changed, but I think I figured it out. All of my preexisting radio transmission actions had been AM, but changed to FM suddenly when I updated from 1.2.4 to 1.2.6. Also and importantly, radio transmissions now only work for me if I give them a name. Third and finally, I had concurrent "AI task set" actions that should have happened simultaneously with the radio transmission (and worked in 1.2.4) but they now cause the game to crash unless they are changed to "AI task push".

Radio transmission is no longer working as a triggered action. The difference between "radio transmission" and "sound to all" is essential to hundreds of triggers in my missions. Is this a 1.2.6 thing?

Actually never mind. The mission file is 60MB and won't upload as an attachment.

Will do as soon as I get home to my machine. Thanks in advance.

I'm having a weird problem. Sp mission with 3000 ground units (infantry) divided into 200 groups. Half have delayed activation (5% random x 5% random conditions). It works fine to stagger everyone's start time, so long as I don't delete any groups from the map. If I delete more than about a dozen groups, then NONE of the remaining groups ever activate! Why is that?

sweet. thanks for the speedy reply.

Any way to randomize the location of ground unit group waypoints or get them to loop? I'm thinking of something like the nifty "patrol" function in ARMA.

I'll articulate this again, hopefully with more clarity: Bullseye data in the TAD does not correspond with heading data from the mission editor or the in-game bullseye calls from AI controlled aircraft (I've tested with AI Predator and helicopters). This seems to be a problem related to magnetic variation. Is there a fix available? If this isn't the correct sub-forum for this question, please advise. Thank you.

bump?

Are bullseye calls accurate? Is bullseye data displayed on the TAD accurate? This is from a thread in the A-10 general forum that wasn't definitively answered: A question about bullseye calls for ground targets. In a previous patch ( I believe it was 1.1.1.1) there was a user mod that fixed problems that apparently resulted from magnetic variation not being incorporated into bullseye calls -- as a recall "SPEED" was responsible for this. This worked beautifully until the game was patched to DCS world 1.2.0 and since then the fix hasn't worked. So my question is - does this remain an unresolved issue, or am I improperly setting up the CDU (i.e. is there a place to take magnetic variation into account) to accurately calculate bullseye offset calls from an AFAC or AWACS? If anyone would be willing to weigh in on this I'd appreciate it. I used to find these calls incredibly useful for finding threats, but for now they are only noise. Any help or insight would be appreciated. ===== I noticed the same problem! I place enemy units at bulls 74 for 35 at a mission waypoint. Friendly AI calls them correctly at bulls 74 for 35, but when I hook the waypoint, it shows in my TAD as bulls 68 for 35. Off by several miles.

I noticed the same problem! I place enemy units at bulls 74 for 35 at a mission waypoint. Friendly AI calls them correctly at bulls 74 for 35, but when I hook the waypoint, it shows in my TAD as bulls 68 for 35. Off by several miles.

Too bad, I created dozens of custom sounds and was really hoping to use this trigger action! :(

I'm still curious about the RADIO TRANSMISSION action. What is meant by selecting a trigger zone and the power in Watts? Does the trigger zone define the source of the radio message, or the range within which it can be heard? I'm trying to get AI JTAC to request my CAS when enemy units get close, but I'm not having luck hearing radio transmissions in SP, even when tuned to the correct frequency and modulation.

Will FAC units request CAS on their own? When I contact ground FAC, it either instantly has a target for me, or it thanks me for my good job and tells me I'm all done. I'm envisioning a long duration, highly randomized, and low-intensity, mission. I want to check in and loiter on station, and then be contacted by ground FAC if/when they need support, i.e., if/when they make enemy contact using enroute task FAC. Is that possible? Right now I have to keep checking in with JTAC every few minutes to see if I'm needed.

Roger that, I'll tinker with the ETAs and ignore all the speed values that are red/insanely low. Agreed that would be a nice feature in the future.

A variation of this fixed a terrible jittering problem with my mirrors in the 1.2.0 A-10C. I selected "medium" to start with, then manually configured individual settings back up to where they were in 1.1.1.1. Mirror problem solved, and FPS is still acceptable! Thanks!

Ramp start time independent of takeoff time? The GUI instructions aren't clear on how to do this. For example, I want to cold start at 12:00:00, but want a set takeoff time of 12:15:00. I'm sick of being late to arrive at waypoint 1!