Winston60

Edit: The A-10A in DCS World does not have a functioning Pave Penny pod or any laser guided weapons. Maybe someday.......

Just refrain from pressing any buttons, touching the keyboard or clicking the mouse.... until the plane selection comes up. It will take awhile and it will cycle through a few different screens. If you press buttons or keys or click the mouse it will crash the game. If you wait patiently, you will be rewarded with the plane selection screen.

:thumbup:

Agreed! and also the A-10A on the TV guided maverick screen. Guys, this visibility problem is NOT specific to the A-10C and it's TGP. The Su-25T suffers from the same problem with it's TV guided weapons on the Shkval screen and the A-10A on the TV guided maverick and even the IR maverick screen. On the Su-25T and A-10A TV guided weapons screens it seems the objects have nearly the same brightness and contrast as does the landscape, making them nearly impossible to see at distance. Now with the IR weapons on the Su-25T and A-10A, I'm seeing exactly the problem that you A-10C drivers are seeing. As this affects more than one module and seems to be a problem with the new textures on the old map, I would think the priority to fix this should be increased and expedited. Or the Su-25T. Or the A-10A.

The contrast/IR TV display problems like this are widespread in ver 1.5. The A-10C has it, the A-10A has it and the Su-25T has it. As it is now in 1.5, objects are nearly the same brightness/contrast as the terrain. The contrast/brightness of the new textures on the old map needs to be fixed to enable TV and IR displays to function like in the old 1.2 version.

Guys, this visibility problem is NOT specific to the A-10C and it's TGP. The Su-25T suffers from the same problem with it's TV guided weapons on the Shkval screen and the A-10A on the TV guided maverick and even the IR maverick screen. On the Su-25T and A-10A TV guided weapons screens it seems the objects have nearly the same brightness and contrast as does the landscape, making them nearly impossible to see at distance. Now with the IR weapons on the Su-25T and A-10A, I'm seeing exactly what you A-10C drivers are seeing. Clearly this is not a "wish" but a "bug" plain and simple. As this affects more than one module and seems to be a problem with the new textures on the old map, I would think the priority to fix this should be increased and expedited.

Any progress on this? I'm also interested in 1.5 compatability.

Possible explanation 1: It's a video from a very old version of DCS or A-10C. Possible explanation 2: It's not the AWACS calling out ground targets, it's another flight. Time 0:54 -- AWACS (Wizard) calls out in voice 1: "Enfield 1-1, Wizard, clean" Time 2:40 -- Allied Flight (Wizard) calls out in voice 2: "Uzi, tally AAA at bulls 106 for 18"

Try creating a custom snap view that zooms your maverick screen to nearly full screen while holding down a button, then going back to F1 cockpit when the button is released. A quick press of the button will help in spotting targets at greater distances because the mav screen is so big, and releasing the button gets you quickly back to 'heads-up' in the cockpit. I can often lock a target at longer ranges using this method but then I have to wait until it's in range to fire.

I find in the release version of 1.5, the PAC does work better in keeping the nose down while firing. There's still no key to turn it on or off, it still comes on when the gun is selected, and goes off when the gun is de-selected, but the 'nose coming up when firing' is greatly improved now. ....and the G-force breathing is finally fixed!

I still show the Mk-20 Rockeyes in my "A" loadouts in the mission editor. You can put them on in and use them, but you can't rearm with them. Too bad 'cause they are very effective and accurate in CCIP mode. LAU-61's are sorely missed.

All true. Your wingman will have strobes, but not the player or client. Plus you still cannot set the altimeter. This is still not a DCS advanced aircraft even though the flight model was much improved awhile back and in ver 1.5 a lot of the old bugs were fixed. I imagine someday they will give the "A" some love and make it a bit more complex. In the meantime, I'm enjoying it a lot! For more features and realism you have to transition into the "C".

AWACS uses bullseye to call out air targets if you ask for "picture". If you ask for "bogey dope" AWACS will call out relative to your aircraft. AWACS does not see ground targets. Ground targets are a JSTAR aircraft task. However, it would be nice to someday have a JSTAR in DCS. On a video you may have heard some voice acting via a sound file played in the mission.

AWACS can detect airborne targets only.

Just a small bug but still annoying: In the release version of 1.5, in the A-10A after closing the cockpit canopy, the sound continues long after the canopy is fully closed.

Another update after installing patch ver. 1.5.2.49392 * PART OF GROUP IN ZONE - Now works if the group is AI ...... still testing to see if it works for clients.

Update after installing patch ver. 1.5.2.49392 * UNIT INSIDE ZONE - Works if the unit is AI .... now works if the unit is a client. I'll be testing the others later.

Guys, I'm talking about the built in mission editor triggers, not triggers run by scripting. Are you saying that bug 31682 - Client groups not accessible in multiplayer.... is the cause of the mission editor trigger UNIT INSIDE ZONE not working? UNIT INSIDE ZONE - Works if the unit is AI .... Does not work if the unit is a client....... is especially troublesome to me as it renders almost half of my existing missions to a non working state.

I flew in a 1.5 hour multiplayer mission recently. At the end my nav hud heading was still massively different from the heading shown on my A/G hud mode. :dunno: No change for me since sometime in ver 1.2

Update for triggers in 1.5 release multiplayer only (I'm no longer playing or testing in single player). * UNIT INSIDE ZONE - Works if the unit is AI .... Does not work if the unit is a client. * ALL OF GROUP IN ZONE - Works if the group is AI .... Does not work if the group are client(s). * PART OF GROUP IN ZONE - Does not work if the group is AI or clients. Can anyone confirm these, or have found anything different? Remember, multiplayer only.

How does Viacom work when whartsell has said that his Static ATC mod is not compatible with DCS ver 1.5? See last post here: http://forums.eagle.ru/showthread.php?t=138994&highlight=voice+attack&page=3

It's been reported in the 1.5 beta bugs topic that the "UNIT IN ZONE" trigger doesn't work and so it is with the 1.5 release version as well. I've also found that the "ALL OF GROUP IN ZONE" trigger seems to work in multiplayer for AI groups, but not for human players. Perhaps everyone can post here any other triggers that they find are broken in the release version. I wonder what other triggers are broken? I'll be testing other as we replay my old missions in the release version of 1.5. I'm hoping that ED soon will take a close look at these mission editor triggers that are no longer working. Kinda sucks to fly all the way to a combat area and you don't trigger the event.

The difference in heading from NAV mode then switching to A/G mode is an old bug from DCS ver 1.2. It doesn't always happen though. I'm surprised this has not been fixed for sooooo long.

Thanks Coug4r. Very interesting. My server is running on Win 7 Home 64bit.

My server not being visible on the servers list seems to be related to a specific "mission" that I'm running. I have built 22 missions so far in the old 1.2 game. When I loaded all 22 of them into ver. 1.5 release's mission builder and saved them, when running 9 of them on my server the server is not shown on the list but can be joined by entering the IP. The other 13 when running, the server is visible. I've re-saved those 9 over again and even tried to make some small changes in order to fix this, but no luck. There's no errors or anything that I can see out of the ordinary in my log files. If anyone's interested I'd be willing to upload one of mine that shows in the server list, and one that doesn't. That way you can test on your server and see if this is true for you too or maybe someone can catch what's different between the 2 missions and solve this problem.