Recluse

Sure, here you go.... I think this is the latest one with Apache FARPS Apaches_Syrian Power v080.miz

I have observed on one server that depending on the starting point, there are some Dead Zones where aircraft may be parked that don't seem to be able to communicate with the tower. Similar to the way DCS parses the location to (for example) switch from the Request Taxi to Request TAKEOFF menu. This drove me crazy for awhile as well as it only seemed to happen with HOT STARTS not COLD STARTS, but it turned out to be a function of the PARKING position. Once I taxiied away from the parking spot, the Tower started responding. Happened to be in a Mirage2000 as well (at Vaizaini)

IF you would like to use the DD.MM.SS.ss coordinates for your waypoint creation so it is consistent with GPS weapon PP Coordinate settings, and you can match up the coordinates on the FLIR with the coordinates fed to TOO GPS weapons you can go to: HSI-->DATA-->AC and click on the LATLN Formatting button and Toggle it from DCML to SEC Image below is from Manual and isn't showing PRECISE coordinates, but it works for them.

Worked OK for me. null As with all the precise coordinate entry of DD.MM.SS.ss, hit ENTER after the SS and then enter .ss It took the extra digit for W Longitude no problem. Are you sure you entered the W for WEST?

I thought the new Base had replaceable springs and cams, though I am happy enough with mine, it would be nice to have the flexibility. When I bought mine, I also bought the adapter in case I wanted to put my old COUGAR stick on, but I read it was not recommended due to the weight of the Cougar handle and the lighter springs. Thought heavier springs might make it more of a possiblity. Might be useful to have the F-16 stick if I go back to flying the A-10, and the BMS 4.37 VR got me interested in flying the Viper again. (or just buy the WINWING F-16EX, I guess, but I can't quite justify that expenditure at the moment).

Thanks!! I was going to ask you EXACTLY where that one bolt lives, since it wasn't at all obvious to me, but I figured I wasn't going to do the detent swap anyway. The Orion (Stick and Throttle) has gotten so many upgrades since I bought mine, I have been wondering if it is worth it. Really more interested in the improvements to the STICK than the THROTTLE.

Yeah, the little curve change definitely helped. I do very often fly multiple aircraft in a session, so I don't want to be tearing it apart and putting it back together. It's fine the way it is except for very specific circumstances. I had enough of that with my old COUGAR that was replaced by the ORION which I had to strip down fix frequently due to worn out gimbals and multiple changes of Potentiometers (both mechanical and Hall sensors).

You are correct!!! As far as I could tell, the whole bottom plate would need to come off. I wish I had waited for the Orion 2, but I was in dire need of a HOTAS replacement, and there was a sale...and despite a little FOMO, I have been very happy with it.

Holy crap man!!!!!! I don't know if it was your settings, or my hours of frustration finally paid off, or the phase of the moon, but I just did 4 "sorta" Case 1 recoveries in a row on the Tarawa! Not by the book hovers by any means. Slow rolling landings with a very light bird, but down safely with no broken aircraft...which is a WIN. My boarding rate was more like 20% before tonight and a white knuckle affair from start to finish. Just knowing I can get back aboard is a HUGE boost. Now If feel like I can actually start working on the full hover landing. Could VTO and transition to flight off the deck as well.

Thanks! Will give it a shot. I never used the SLIDER function before! Wasn't even sure what it did!!

NO RUSH AT ALL... I have lived this long without it. I guess I can just go fly my shiny new MIRAGE for awhile HONESTLY All the modules are fine EXCEPT when it comes to the high throttle states in the Harrier or the constant ROTOR RPM LOW in the APACHE on startup, but once in flight it isn't bad.

That's what I thought MIGHT be a solution. Care to share your curves? LOL.. looks like I would STILL be able to blame my inability to hover on the throttle OUCH! I was really hoping not to have to do Throttle surgery!!! Especially since I fly other modules that I WANT the AB detent for.

Probably a general question for many throttles, but I have the WinWing Orion, so that is the one I am concerned with. I am wondering if there is a way in SIMAPPRO or DCS to reset the complete range of the throttle so it goes from 0 to 100 before the Afterburner detent. Or maybe a better way to do what I want to do: For Helicopter Collectives, and the Harrier, it is annoying to to have the AB Detent to run past. In the Harrier, especially when trying to HOVER, very small throttle movements are needed near the full power mark and going in and out of the AB detent reduces the amount of fine control. Similarly, for Helo collectives, pulling back through the DETENT often puts in more collective than is desired at takeoff or, alternatively, to zero collective for landings. Thinking maybe a suitable curve might do the job as well, so I wondered what others are doing. It is a tradeoff between losing the additional dynamic range of the throttle, and getting smoother control near the HIGH end (throttle) or LOW end (COLLECTIVE). Thanks in advance for any suggestions. I feel like I am missing something obvious

Here you go. - Take off Parking HOT Communicated with ATC for TAXI and TAKE OFF - Communicated with ATC for INBOUND and LANDING. - Landed. Taxied to Parking Area (maybe not the one they wanted...but how would I know?) - Could not access ANY ATC menu items other than F11 and F12. - Accessed F8 to refuel to show Comms were working - Still couldn't access ATC for taxi to runway again. ATCMENU.trk

When I land, and get the message "TAXI to PARKING AREA" I taxi off the runway and Park SOMEWHERE. If I rearm and refuel, I can never get back to the ATC Menu for REQUEST TAXI or REQUEST TAKEOFF. If I just go ahead and taxi to the Runway, ATC will usually come on with permission, even though I was never able to ask for it. My multiplayer buddies don't seem to experience this. They get the full ATC menu back. Some setting I am missing?? Seems to happen to me in BOTH Singleplayer and Multiplayer. I seem to remember this USED to work with the full ATC menu being available again, but I don't know just WHEN it stopped.

IN FLIGHT ALIGNMENT (as I understand it, it uses GPS to continually update the Alignment vs. NAV which is prone to INS Drift and is used in PRE-GPS timeframes) But, yeah you can't leave in in GND Glad you got it sorted out. It is a powerful feature of the Harrier!!

See this post for the new procedure: In brief, WINC LONG (or long press on the Arrow Keys for WP on the EHSD) and select TGT POINT on the ODU.

No real reason Other than wanting to keep them default for muscle memory when actually using the keyboard at other times... and not seeing the obvious - So I realized you could put MULTIPLE key commands in any given spot, so the Muscle Memory thing is no factor - It did work with the simplified key commands, but for the View Commands, I did have to insert a DELAY which kept the action button pressed down for a longer time. Went back and put that delay in for the original compound command it it worked as well.. Looking good now!

Been experimenting further. I contacted the author and he suggested adding some delays/pauses in case the keys were being processed too quickly for DCS. So far no joy on that either, but I was wondering if anyone using VAICOM/Voice Attack have any similar timing issues with complex commands like these. Got it working well for VIEWS and Radio Menus (basically Fx key commands since the menus can change). First time I have used any sort of Voice Command software, and so far it is promising except for the examples above (Cockpit Camera Views and Active Pause).

Just a question: Is there any advantage to using Markpoints vs. hitting the TOO button to create a Target Point? That is what I usually do, though I admit that I have a hard time sometimes getting the TPOD to snap back to the selected Target Point the way I think it should. Not sure Markpoints would work any differently, but you never know!

Latest Open Beta made a change. Name the Markpoints #TP0x instead of T0x and all will be well. No need for the throwaway waypoint any longer either

Just a CODA and a Mea Culpa to my ScratchPad Extensions dilemma. I could NOT get the extensions to work, but I was intrigued enough by the new keyboard by @Draken35 that I set out again to get it working. What I discovered was that AT SOME POINT I had accidentally created a Scratchpad folder in the SCRIPTS folder of the DCS Open Beta GAME hierarchy in addition to the correct folder in the SAVED GAMES hierarchy. Once I deleted that, everything was working fine and I could use the Extensions including keyboards. OPERATOR ERROR again

The Select seems to send a "1". So, if you have NOTHING selected and hit SELECT, it will jump to F1. If you use the Up and Down to get to a menu selection, when you get there and hit SELECT it will "say" "1" but will select that item. Are you getting the sound for the counting when you use your up and down keys?

Not sure. It works fine for me. All I can suggest is to check your Joystick Mappings again in the DCS MENU NAV.ini file. Question: Do you get the Sound (VR) or visual indication (non-VR) when you hit your Toggle or is that not working either? If your Toggle isn't working, check to make sure for some reason Windows doesn't think your Joystick 2 is Joystick 3 or something. If the toggle is not working, nothing else will If the Toggle is working but the other buttons are not, then potentially the thumbwheel isn't sending discrete inputs, though I would imagine you have used it this way before. Also, as I mentioned some time ago on the VR4DCS discord, make sure your Windows Sound playback source is set correctly so you can hear the voice prompts. If using the VR headset as the speakers/headphones, make sure that is what the Windows output is set to. If using another device, make sure THAT is what it is set to otherwise you will not hear the Menu Nav sounds. This tripped me up many times.

So I have read this many times, but in this article (circa 2006) https://apps.dtic.mil/sti/pdfs/ADA498288.pdf about which pod to equip USMC F/A-18D with, it does NOT mention that the LITENING is not certified for Carrier OPS. The article makes the argument for the MARINE Litening Pods even for Carrier embarked Marine Hornets. Anyone have an actual reference to the carrier rating difference between the pods? Then there is THIS.. indicating the ATFLIR is now being replaced with the LITENING, but, this is a new LITENING pod, so it still doesn't answer the question about the "old LITENING pod" https://theaviationist.com/2022/09/07/u-s-navy-super-hornet-makes-first-flight-with-litening-pod/ This is an interesting tidbit: