Czar

Yeah, good call....they are AI A-10Cs on OPs mission. AI helicopters can "spawn on ground" outside parking spots. Only AI fixed wings are prohibited.

Ah! Thanks Razor. Learning new things everyday. @Dragan your Warthogs in your mission are set to spawn in a "turning point" at 33ft Set to "Start on Ground" instead like on my images above.

That's a track file. Use "Take Off From Ground". To from ground.miz

Can you post the mission file?

Well... whatever can be easily accessed through the hotas for a quick glance to grab coordinates and such. The multiplayer dedicated one clumps everything together; player messages, kills, players joining server etc. It can get impractical quite quickly in dense missions. In Single Player however, there is no such message/chat window for quick access. One must press 'escape' to get to 'message history' window, and even that doesn't have any filter to apply for better consulting a certain set of information. Of course, nothing like a good physical notepad and pen in hand like the folks that had flown/flies the real deal irl... or the Phantom canopy for that matter. lol OP mentioned the need to a hotas binding to grab that window up for quick access, and I think it is fair. Maybe something a dual virtual kneeboard can bring in an easy manner (2d and 3d).

You can actually. Hence the referencing to that message system. When you open the box to type a message it enables access to a scroll bar IIRC (it is been a while I had to use it). Something more robust for both modes, Multiplayer and Singleplayer would be preferable. It is been a bump on the road to open the messages history while playing singleplayer and it is as well while playing in co-op multiplayer.

Hey Hedgehog, it happens. These tiny aircraft names on the forum can get confusing for anyone, especially their being so similar. Sorry for assuming it was for Flaming Cliffs, its been ages I haven't visited the Eagle on that module. This could possibly be an accidental mouse wheel action when the cursor is coincidentally over the lever in game. Very hard to tell from this perspective. I've flow with this bird the most and that never happened, in other hand a few of little accidents with mouse being in an unfortunate place and a click or scroll is made unknowingly. If it happens again, a track would be the most valuable tool to figure it out.

uhmmmmm.... what?... The FF F-15C has been released? How long was I asleep for? Is either you've got exclusive access to a module that's not released or you're using mods for the Flaming Cliffs one to be talking about mouse pointer and mouse wheel stuff. If it is the later. Remove the mod. If it is the former: congrats man. Let us know how the module is. BTW, this is the forum section for the Flaming Cliffs stuff, but if you're using a clickable cockpit mod, that's unsupported: https://forum.dcs.world/forum/866-flaming-cliffs-bugs-problems/

Sorry if my english is not up to par to report this because I'm not familiar with the terminologies with the different tracking and pointing methods. If you order George to search the area, in this case "forward area", then slave him to a point before ordering him to scan for targets on that point. The TADS/George will get stuck in a looped glitch. It wasn't like this prior to the latest patch, I think, but definitely there is a bug. Shown here in a unlisted video (youtube). Need the link to access or watch it embedded here: The track file came from the flight on the video. Track and mission file attached bellow. Simple Caucasus mission in air start made in mission editor. The issue can be shown on the track or verified in less than 2 minutes. Steps to reproduce: Forward area search. Point, using the button you order George to fire a weapon - > Slaving George to the current point of interest, in this case Waypoint 1 where there are a few armored vehicles). Search, using the same button above, after TADS is slaved to the POI (waypoint 1 in this case). Glitch occurs like George is changing TADS FOV indefinitely while scanning the forward area at the same time. This does not occur if you order George to slave the TADS to a point from a fixed TADS or with TADS somewhere else but searching the forward area. Scan at point after forward area search bug.miz Point Bug.trk

I mean... sudden death is something that can occur on a person, but is the CPG (or the AI buddy on the Apache) meant to be on the system failures table? I thought it was related to the aircraft only. Not even ordinance are affected by the random failures, afaik. Restarted the mission and it was fine, meaning it most likely was the random failures being triggered. Random failures was turned on.

Disable any CPU managers. Keep your CPU at factory settings. Cap your framerates so your CPU doesn't choke on some frames here and there.

Hey OP, @Able Dog. Given you marked my comment as a solution, I hope you've found the culprit. If you don't mind, please credit Yurgon instead as I took their thesis to find how your problem was being generated. Happy flying on the hog!

I really hope this type of work is replicated in the Iraq map. The vegetation there is a lot less than sub par for low level flying. A lot of Iraq's map by the center of the high quality areas have very dull, sparse and homogenous vegetation like no care were taken to place them by any system or human.

Disable the historical units switch, the small clock watch on the bottom of the screen in the mission editor. The new units have a [CH] by the end of their names. The packs from Currenthill's website have a [CH] before the unit's names.

This is an old shot used when PTO asset pack was first announced as an AI unit, way before the FF Zero module was official. It can very well be an AI only C. The FF module can expand into the C variant like how the P-47 did. Many possibilities.

It is working as intended on my end. Fine tuning between 0% and 50% is possible. Any cockpit mods?

I like this. ...and it should be added to this wish list: Ability to change only the livery without having to rearm every time after pressing 'OK'. Ability to change only the aircraft numbers if available without also having to rearm after pressing 'OK'. Currently, to use a different livery or numbers, you need to press OK triggering the rearm functionality even though are the same weapons being loaded in. Keep in mind that in modules like the Hornet, if you move while rearming, even though the same weapons already loaded are being rearmed, it will trash the weapons making them unable to be fired/released. A checkbox for every changeable item on the rearm window would be very valuable additions to quality of life on this sim.

They won't function as intended as their code is for AI use. It is far away from ideal.

Uncheck the historical switch on the bottom of the screen and the units will appear. I've seen all of them already in the editor. It is indeed a bug with the clock switch for historical units being checked on, perhaps.

You're spot on on this. I believe you've found the issue. APU RPM% gets stuck at 60% if any engine is out of the fuel cut off position or idle before the APU is fully started. (not a bug)

I went for accuracy by volume of "fire". The chances of OP also having a confusion on the gauges are high given how cluttered the front panel is and the APU EGT gauge which usually hovers at the 6 marker on startup of an engine is right next to the actual APU RPM gauge with the name 'APU' a bit covered at certain angles. Is hard to fumble the apu start. Is easy to forget the APU gen switch as no other module (american) has that need to turn on the APU gen. I took my chances. As an addition. The Warthog without fuel while attempting to turn on the APU will feature the RPM stuck at 30%:

Several years ago + feeling instead of knowing for sure through many trials is not good enough. (I've been there many times) Approach it from the ground up. It can be a simple switch not found in other modules/aircraft that's by default off like the pesky A-10C APU GEN switch. The APU might be running, sound queues are not good enough as you said you took some time off, and the APU Gen is off giving you only cockpit partial power and a bad diagnosis. To add on what others helpful people pointed out above: Go with a start up checklist, un-modded Warthog, check the right front lower panel especially the APU Gen switch. Fair skies.

That 'Play All' button is absolutely cursed!! I was with headphones on. This is some all star work superb database and the 'quiz' is something that adds so much value on the learning experience, some manuals could benefit the inspiration from it. I cannot imagine memorizing all of this, at all. Is it an attainable proficiency to recognize these sounds?! I'll re visit it in the future for sure.

The issue is already reported.