VAF [136] Striker

Yeah, I didn't realize that it wasn't working. What did you do to get it to work?

I don't have a track since this was about a 2 1/2 hour flight but you can see that the aircraft is still operating as if it were flying. The engines are still running at full power and it's creating dust from being on the ground instead of being a burned out wreck.

I honestly don't know what you're trying to say here but it's obviously a coding bug because this problem does not occur in World 1.2.16. I have hundreds of hours flying the A-10C in 1.2 and I've never seen this happen prior to 1.5.

Thanks WC! That did the trick by the way.

So you make them hold at the waypoint by using the "Advanced Waypoint Actions" but you make them resume their route by using the "Group Resume" action in the triggers?

I tried your suggestion this morning and it still doesn't work. The convoy is stuck at the hold location so something else needs to happen to make it work.

OK, thank you. That actually makes sense to me since the "hold" command is already set. So I'm assuming that "Condition" apply to an either/or situation? We'll give using the flag on for the end condition only a try in the morning.

We set up a mission where the AI convoy stops at a waypoint and needs to resume the route when the nearby enemy units are destroyed. In the trigger list we set the units that need to be destroyed to less than 10% as the condition and when they are destroyed it sets flag 1 to on. Then in the advanced waypoint options we used the unit "hold" option and checked flag one is off for the condition and the stop condition as flag one being on. The convoy stops at the waypoint but will not resume after the enemy units are destroyed so we don't know what we're doing wrong. I searched for a solution on this forum but couldn't find anything helpful. I'm sure there's something simple we're not doing but stumped.

Mine is set to just over 16GB of vram and I'm experiencing the same problem. Everything is fine until I turn on the TGP and switch to WHOT. Then I get terrible stuttering and freezes. They go away mostly but slowly although there's still some presence all the time. I was running the cockpit displays at 1024 every frame and when I switched to 512 every frame the problem gets much better but it's still present. I still have the partially transparent vehicles in WHOT mode though. I'm running a GTX970 and I have 16GB of Ram on a i7 Quad Core.

I did a search and couldn't find anything related to this. Has this been reported yet? In WHOT mode all of the vehicles are semi-transparent. I'm using Windows7 Pro and a GTX970 and everything driver related is latest.

The skval can be activated while on the ground as long as you have the throttles set to the center detent (auto) position which is full throttle. The generators work at 100% in the full detent position. Section 9-16 of the operation manual.

It doesn't come on automatically. You have to press "o" (not zero). Same process with the Su-25T as well. Also, use "o" to uncage. When you lock and lase a ground target it will stay locked even after being hit so you can press "o" so it will uncage that target and then you can slew to the next target.

:doh: LOL, I just posted this and realized activvv stated the same thing.

For anyone else experiencing the same problem, the fix is a lot easier than what's been posted here. I know that this thread is pretty old now but I had this same problem and needed to know how to fix it. What happens when you install DCS and TrackIR, the axis options automatically default the "Zoom" axis to the TrackIR "Z". All you need to do is delete the TrackIR "Z" axis control from the zoom box in the "Axis" options and then assign it to "Absolute Longitude Shift Camera View" box. Then go to "All" control options and scroll all the way to the bottom and assign a button press on your HOTAS if you wish to "Zoom In Slow" and "Zoom Out Slow". This works for all of the FC3 aircraft as well as the T-51D and the Su-25T. It works the same way as it does in my A-10C module now.

Do you know if this would work with 1.2? I have a game server in my office and my game system is right next to it.

I did do a search and didn't find anything reported on this issue. We set up a multiplayer game this evening and my UFC quit working. I was hosting the mission on my system since we haven't updated our server yet. We were all running 1.5 Beta with no mods. I do not have a track as we were 45 minutes into the mission. All UFC controls became inoperable. I could not use the waypoint selector rocker or any of the number pad buttons. After awhile, all UFC functions stopped working. The mission we were running was Operation Bactria and all of the scripts were non functional. So I was wondering if this was a mission related problem. I can try to recreate if it's not a mission specific problem.

Yes, I was able to reproduce the problem. I turned into the wingman and when he took off he damaged the nose. Then I went to the exact same place to repair. As repair finishes, the plane flips around 180, engines go full and turn off. This time I lost rudder, flaps, speedbrake and joystick control. All my control surfaces work outside of the simulation. I had to die twice to do this so hopefully it will help! :smilewink:

Yep, you are right Bignewy! But it's too big for me to submit. The attachment manager won't allow anything over 9.6 MB. And the last time I tried I got a security token error. Is there a way for me to reduce the size of the file or submit it another way? It's saved on my desktop as a 14MB zip file.

Yeah SithSpawn, I just realized that from checking my files. Even DCS World 1.2 doesn't create tracks from single player. I'll try to remember to create tracks so I have a record after a flight.

My install of 1.5 isn't creating track files in single player at all. It does create track files in multiplayer. I've searched all the install and user folders and nothing. Is there something that I need to enable or is it possibly a bug?

I can confirm that this is happening or something very close anyhow. I started the "Georgian Oil War" campaign and went back to base to reload and repair. As repair concluded the jet spun around 180 degrees. After that the flaps and speed brakes stopped working. The flaps were stuck on full landing position. It did not create a track file but I'm including the log file and my system spec's. World 1.5 is not creating any track files for single missions I've been doing. I had to convert them both to text files.

Understood.

Something is wrong though. Look at the AAV-7 or the BMP-3. You can rotate them around like you can aircraft now in 1.5. You can't rotate anything in 1.2. Some of the other ground vehicles are behaving like aircraft as well but other vehicles are just static. Maybe not truly a bug but not right either.

Several of us started an older mission that I created recently in 1.2.16 just to test for MP issues. It's a very dark mission starting at 5 AM. 1. The emergency flood light controlled from the right rear light panel wasn't function correctly. It was cut off half way through the cockpit by a sharply defined cut off point instead of flooding the entire cockpit in a nice even fade to the front of the pit. I forgot to get a screen shot. 2. The front emergency flood switch on the electrical panel did not work at all.

Night vision looked really bad compared to 1.2.16 in a MP mission I was hosting. It's very pixilated and the color seems different and the overall image is very fuzzy. We all had our cockpit textures on the highest level and didn't try any of the other settings. It's a recent mission I created in 1.2.16.