hobbes57

Does anybody else with a Quest3, the v63 version and running the DCS through Virtual Desktop with experience a very noticeable decrease in image quality? I can start and run DCS just fine (through VD), but compared to "a few weeks back" when I last played, I notice that the textures now look mushy and blurred, almost low-res? This is on my RTX4090 with most things set to High (both Textures for sure). A few weeks back all of this was pretty crisp and fast (~70FPS) and "Wow!" in my headset. Now it is still fast (same FPS) but just looks ugly. The cockpit textures are smudgy, faraway mountains are a washed out blurry blob and the overall feeling is very "Meh". Something broke and since I didn't change anything - expect probably the automatic update to v63 - I'm wondering if this might be the cause? thanks!

Ah Nealius, that explains my troubles. Thank you - hopefully this can be added to VAICOM. For all interested, https://github.com/Penecruz/VAICOMPRO-Community/issues/55 is the VAICOM enhancement request.

No, I'm not sure if the Forrestal works the same as the SC, regarding ATC comms. Does it? I'll try it out again tonight and with debug and take a look at the logs. I didn't know that was possible, so maybe that'll give me a hint. Thanks

Hi all, recently, I dug through the Supercarrier (which I own) manual and its detailed landing pattern description (Talking to Approach, Marshal, the LSO etc.). I also see that my nicely working VA+AIRIO setup has voice commands for Approach, Marshal, the LSO listed in the manual. However, when I try to follow these procedures while approaching the Forrestal, I don't get the expected responses. For example, when, as listed in the VAICOM manual, I say "Marshal, Inbound for carrier", I get the little happy beep after "Marshal" (which tells me the recipient was recognized) but an unhappy low beep after "Inbound for carrier" - and no response. In short, how to get this working correctly on the Forrestal? Does that actually work or am I trying in vain here? Thanks!

Lots of great replies here, thank you all! Lots of costly options too Ideally, I'd like to reuse my TM Warthog grip - the grip itself is fine and has lots of buttons which I like. I'm thinking about exchanging the base only to make it smoother and easier to control. Currently thinking about a VPC WarBRD base - this seems to work with the Warthog grip and may also fit a VPC V.F.X Grip at some point. Can a VKB Gunfighter III base support a TM Warthog grip? I believe so. So both bases seem to be an option, with WarBRD the noticeable cheaper one. Is the higher cost of the Gunfighter III base worth it, compared to the WarBRD? The Rhino FFB base is out of my budget I believe.

Hi, for years I've been flying a (center, desk mounted) Thrustmaster Warthog an I'm generally pretty happy with it. However, I notice the 'hard' center of the stick more and more these days, especially during F-14 refuelings and landings. Do you have any recommendations for a better and smoother experience? If possible, I'd like to keep my Warthog Throttle and Joystick base with my existing desk mount. But maybe a stick that has a "lighter" touch? Thanks!

For anybody interested, I looked at https://whitemagic.github.io/JoystickGremlin/ which has something called Modes. They seem to be just what I'm looking for, so I'll try it out sometime: Mode In certain situations it can be beneficial to split a profile into several parts, called modes. Each mode can have their own individual set of physical input to action mappings. For example in flight simulators this can be used to have one mode for air combat, one for ground attack, and one for communications. One powerful feature of the mode system is the inheritance capability. A mode can inherit from a single parent which results in the child mode executing whatever action their parent defined for a given input if the child has no actions of their own specified. This allows creating basic modes and then fine tuning them in a child mode for particular usage scenarios without having to duplicate common functionalities.

Hi, I'm using a custom F-14 profile for the TM Warthog that I'm starting and running with the TM Script Editor (or whatever the tool is called). It has all of my pilot controls nicely mapped to my Hotas. I've not changed any default F-14 keybinds in DCS itself. This works lovely - as long as I'm in the pilot seat. Now I'm starting to dabble with some RIO controls and would like to use my Hotas as well. However, when I use "2" to switch to the RIO seat, my Hotas of course still sends the pilot keybinds when I press any Hotas button. Do you know of any way in which I could switch between a "pilot" and "RIO" F-14 TM profile, preferably on the fly, when I press "1" and "2" in the sim? I would like to keep all my Hotas mapping external from DCS, if possible, relying on default keybinds and the TM scripts. How do other Thrustmaster Warthog Pilots/RIOs solve this "switching" issue? Thanks! And many thanks to Heatblur for a really high-quality module

Hi all, for years I've been using a Logitech G19 keyboard which had 12 freely "programmable" G1 - G12 keys. It looks like it's breaking down soon, so I am looking for a simple, similar solution. I have a TM Warthog HOTAS, but in addition, these keys could be nicely used for things like kneeboard on/off, radio channel up/down, etc. Great and simple to set up for different airframes. Can anybody recommend something similar? I'm not planning to go down too deep into the rabbit hole of custom simpits or button boxes, as I'm getting laughed at enough by the wife and kids Thanks!

Hi Chichowalker, I just set up VAICOM PRO last night for the first time and it works nicely in the sim (single player only). I mapped PTT buttons to my HOTAS, can issue commands, have them recognized by VAICOM and Voice Attack and the f-14 RIO and the Ground Crew react to them (i.e. "Chief, connect air supply"). I don't have radio menus on the screen at all. I followed the VAICOM user manual step by step, for all of it's looong 40+ pages. It took me about two hours to get it all running, but I'd recommend you do that again. Especially the VAICOM preferences are pretty complex and somewhere in that documentation the "don't display radio messages" is mentioned too. Good luck! Now for a question of mine: VAICOM F-14: How to tell Jester to tune the -182 radio to a station? Hi, I'm getting into VAICOM with the F-14 RIO extension and it's fun stuff. One thing I haven't figured out: How do I tell Jester to tune his -182 to a ground station, i.e. Nellis AFB? I try "Jester, Select Nellis" and while VAICOM does seem to recognized the command, nothing happens. Is this the right command to use or do I have to phrase it differently? Thanks!

Thank you @MAXsenna, I now rebooted with a disabled Power service and my stutters are mostly gone. Still pretty bad FPS with my 3090/G2, but that's a whole other journey

Hm, double clicking just opens the properties but I cannot Disable or Stop it there anywhere:

Folks, could I ask *how* you disable the Power service? In my "Services" panel, I see the "Power" service running, but the Stop button is disabled (even when running Services as Administrator). So, how do I do it? thanks a lot, H

Thank you all - for me, all of the six pages are empty (I do not carry any weapons). I made kneeboard pages out of Rudels detailed startup checklist, so I'm set for now.

Hi all, I just got started on this strangely fascinating bird but: When I open up the kneeboard, I see about 6-7 pages of empty yellow notepad, followed by the many airport charts. Is something supposed to be on these yellow pages? Specifically, a startup checklist of sorts? I was looking around the files section but didn't find any detailed checlists, ready-made for kneeboard usage (which is surprising, given the age of the module). Where do you guys get yout startup checlists from? thanks, H.