Ziptie

Oh wow, yeah that status is not what I saw. MEGA sir! Lot of work there for sure. What rudder pedals do you use? Cheers, Ziptie

Indeed this is where using the laser mavericks in a 'cluttered' area can prove more effective / less bothersome. That being said, those obviously require a continuous good spot from the laser - either requiring you to be in a more vulnerable position for a longer period of time, or getting a buddy lase. I agree, the FLIR showing trees/plants/telephone poles with the same intensity as a moving vehicle is a bit frustrating. Very much looking forward to when that can be corrected. Cheers, Ziptie

Was the INS warning labeled P/INS ? Ensure that you are choosing the IFA position rather than the NAV position, via the rotary selector. There has been procedural changes for the Hornet, in that respect. There is also a way to speed up the alignment process, similar to the 'fast align' process for the A10C I/II. If you aren't sure, happy to share that process - it's incredibly simple, literally two additional steps, if you would like to skip the full 10 minute alignment process and shorten it to more like 2 minutes or so. After selecting CV/GND alignment via rotary selector: 1. box STD HDG on the HSI via OSB button 2. after alignment indicates 'OK' on HSI, select IFA via rotary selector. Done. Cheers, Ziptie

How do you deal with the lack of resistance / limitations of movement when using the touch controllers, if you don't mind me asking? Cheers, Ziptie

Also something I do frequently. Using the TAD with hook from bulls is nice for giving a bearing and range to other aircraft quickly though - talking on to a target or waypoint :thumbup: Cheers, Ziptie

Glad to hear sir, happy employment and here’s to many more shacks! :thumbup: Cheers, Ziptie

I currently use Coolie Switch Aft with regularity - sometimes makes an easier flow switching display pages on each individual screen, sometimes to swap MFD for quick press of an OSB while keeping the right hand on the stick, sometimes to assist with some glare as another stated. That being said, I also look forward to having that functionality change for the HMCS SOI command. It would be cool to replace Coolie Switch Aft long with the former functionality that Coolie Switch Aft short commanded, as the current Coolie Switch Aft long command is not something I ever use - but to each their own for things like this! Off topic, but I am looking forward to seeing how the incoming CMS functionality change works out. Very very use to how it has functioned for years now - this is the one that gives me the most "worry." But like all things, adapt or die - in this case quite literally could be the situation :lol: Cheers, Ziptie

Wow, that is mighty impressive sir. Well done :thumbup: Cheers, Ziptie

We always use a bullseye in our server, crazy to think that some don't do this - and I agree that having the TAD set to hook from bullseye can be a very useful tool. Cheers, Ziptie

+1 on having a visor that is able to be raised and lowered (with visual impact for us - not just for looks on external views). Cheers, Ziptie

Glad I purchased it during the pre purchase, when it was discounted. Have logged 12:xx hours in it so far, don't see any more being logged anytime soon. It's fun to fly, very far from complete and while I'm sure it will get to complete status - I'm banking on it being quite sometime. It's nice to learn systems in groups, as it can be easier for some to learn that way. I'm more capable in the Hornet, compared to the Viper - because I've logged literally a couple hundred more hours in the Hornet (428:xx hours as of today with two logbook resets in there) compared to the Viper. A10C driver originally, so since the "II" has come out, neither 18 or the 16 will be getting any seat time until some serious steps have been made in the status of their build versions. That being said, the Viper rips - is lethal as it is and in my opinion is a completely different type of bird in comparison with the Hornet. If I wanted to do a mix of AA and AG, Hornet. If I wanted to just do AA, Viper. My .02 Cheers, Ziptie

Yeah, for sure remember that - and am also enjoying the "break" from Bitchin' Betty. While I understand her importance, it's absolutely been a terrific break from the old girl! Cheers, Ziptie

Pretty cool setup, any new additions to it since your last update? Cheers, Ziptie

Correct, the real aircraft will change the aft "stop" after WoW switch has been disengaged Here's the thing - it's really not that big of a deal in game. Not once, in the 3xx hours of flying the Hornet has this small zone between flight idle and ground idle been an issue for me. You can also reference with your peripheral when the digital throttle stops moving aft and stop your physical throttle aft movement when it does. How often are people using full flight idle in the game while flying? Can't imagine it really happening much, and when it does, these people are really making that small of an input from flight idle that the small "dead zone" from ground idle to flight idle is an issue? Come on, not happening. Much more important things for dev's to focus on. This is a non issue.. AAR, BVR, ACM, BFM - you're not living in that throttle quadrant - and if you are, you're doing it wrong! Next......... Cheers, Ziptie

Or display the FLIR on the AMPCD - then you get the more standard "black hot and white hot" display. I do not use this method, but many seem to do so. What the others were talking about is just a reference scale that is displayed on the DDI after 'boxing' gray - it's just a tool used while adjusting the brightness/contrast settings of that specific DDI. Cheers, Ziptie

Ah, didn't realize we were possibly talking about different airframes. My apologies sir. Won't bother getting back into the original C, so no worries - poor girl will do nothing other than collect virtual dust since the "II" was released. Good to go! Cheers, Ziptie

Coolie Switch short and long commands all work as desired/intended for me. Just did a short hour flight to test some things for others and more times than I could count, utilized coolie switch functions. I'd suggest double checking the keybinds in the options menu to make sure there isn't anything double bound, or changed since the new update. When I initially downloaded the A10C "II" there were all sorts of funky binds as stock. Cheers, Ziptie

^^ this is spot on ^^ and the method I use all the time. It's good advice. Cheers, Ziptie

Can confirm, with 6 mavericks loaded across stations 3 and 9 - CHAS twice will get you to the next station - so it is possible to fire them in a manner to keep the aircraft "balanced." Can also confirm that RIP PRS is not available for any AG bomb on station 5/7, per the information that I last posted, regarding the potential for released weapons to impact each other - potentially causing damage to the aircraft. Just tested this quickly today with the little free time I had. Cheers, Ziptie

Just tested briefly today, there is no difference for me when I disengage autopilot via the engage/disengage button aft of the throttles compared to commanding authority from the rudder/stick that takes the autopilot outside it's limitations, in terms of audible tone/command. Cheers, Ziptie

Affirmative. Cheers, Ziptie

Indeed you can, in the options menu - look for subtitles and check/tick that box. Cheers, Ziptie

Yeah, I'm not sure why the links don't work. Maybe something with the fancy new forum...? As for the quote - I believe it's covered in one of the A10C(original) training exercises. It's also been quoted in another thread, from back in 2014 if I am not mistaken. The simple part is, the clearance between the two stations not being sufficient for the system to release from both stations at the same time, due to the possibility of stores impacting each other - which is clear what could happen if that were to occur. Cheers, Ziptie

Fairly certain you can find this in the A10C flight manual, which is provided by ED when you have downloaded an aircraft - or you should be able to source it from the DCS website - https://www.digitalcombatsimulator.com/en/downloads/documentation/ https://www.digitalcombatsimulator.com/en/downloads/documentation/warthog_2_flight_manual_en/ "Pairs cannot be released from stations 5 & 7, this is due to the close proximity of the stations to each other not allowing safe clearance between weapons as they separate from the aircraft. Therefore the IFFCC is programmed to only release from each station separately, even if a pairs release is set in the weapon profile." Cheers, Ziptie

Well spotted, I missed that part of the issue. Problem solved. Cheers, Ziptie