TWC_Alamo

That sounds great. Thank you.

Looks like a great MOD. Could someone please post the actual mission? Thanks

Thanks VirusAM and maestro72. I started over this morning by deleting the .../saved game/dcs/config/input/F18C folder and copied a clean version of the F18-C Target Profiles 2.2 file from the archive. I replaced of all CD38's with CD13's and even rebuilt the script (although doing so doesn't really effect the kb v220.diff.lua or wh v220.diff.lua---it just rebuilds the DCSWorld.TMC file.) But I did it anyway. I then added the modifiers and loaded the edited kb v220.diff.lua and wh v220.diff.lua files into DCS. And surprise, the NWS still didn't work! On a wild hair, since you guys have it working, I ran the TARGET SCRIPT EDITOR as administrator and....da-dah!!! the NWS works as it is supposed to! I then exited and restarted the TARGET SCRIPT EDITOR normally and the NWS still works. I had forgotten that in the past I've had issues with the Target Profiles not working properly until I ran the TARGET SCRIPT EDITOR AS ADMINISTRATOR at least once. I don't think I'll ever understand Window permissions and ownership. I probably need to bite the bullet and do a clean install of Windows and DCS. Perhaps my misadventure :cry::cry::cry::cry:will help some other poor soul :(:(:(struggling to get his working.

F18C NWS not working after update Yes, I did follow your post and thought all was good, but then discovered the problem with the NWS. I then followed VirusAM's suggestion of doing the find/replace of the 12 occurrences of "cd38" to "cd13" in the TARGET FA18C kb V220N.diff file. That didn't fix NWS problem either. Once NWS is disengaged, it won't reengage---either from the HOTAS buttons or keyboard keys. Reloading the default DCS keyboard file fixes the problem, but then HF's profile doesn't work. Something in the KB.diff file is not right. Can you verify that your NWS is working correctly? Thanks

F18C NWS not working after update The NWS on the F18C is not working after the last DCS update. It had been working great before that. I followed the suggestions in the posts above about renaming all the "cd38" to "cd13" in the TARGET FA18C WH v220.diff and in TARGET FA18C kb V220N.diff. All seems to be working except the nose wheel steering. Holding S3 does not put NWS into the high mode. If I disengage NWS with the S4 button, S3 will not engage NWS. If I use the keyboard "S" key I see the numeric 2 button move on the UFC, but it doesn't engage NWS. If I reload the default DCS kb.diff file the "S" works properly to engage NWS on the first press and shift to Hi-NWS while held pressed. And yes, cat bar is up, which will disengage NWS if down. Anyone else seeing this?

Same here. No mission file is in the MOD.:helpsmilie:

Neat to see the evolution of the design. Ditto on the request for the CAD files.

Terry, I printed the first parts at 0.15mm layer height and 200°C on my CR-10, so may need to step up the temperature. However, rotating the parts by 90° on the bed seems to have done the trick, since that orientation keeps the major forcefrom trying to pull the layers apart. I am using FUSION360 too, so any of those file types should work. I don't have a lot of experience exchanging files in F360, but we can try IGES, unless you know a better format. I want to play with a longer extension ~250mm and see if it will improve the ergonomics of my setup and if the longer stick throw will improve my flying:(. However, it may well result, as you have suggested, in too weak of a centering force, so I may need extra springs. I want to try splitting the "tube" of your version 1 design and glue a aluminum tube in the middle. I plan to run the AL tubing up into the handle to take most of the load off the PLA. I want the TM base on the floor. Thanks for your reply and offering to post files CAD files. Did you ever post your design on Thingiverse?

Terry, Me too. At one time or another, I have broken every piece of the extension at least once!!!! I re-printed the retainer by rotating it 90 degrees on it's edge so the layers are not radial and that proved adequate. I also broke the nut while tightening it down, so reprinted it on it edge. I also increased the thickness of the walls. However, I then put too much force on the extension and broke the tube! I will try reprinting it by rotating it 90 degrees on the bed. PLA may not be strong enough. However, it may be me, my printer or the cheap MicroCenter PLA filament though. I also bought some PETG and nylon to try for increased strength, but haven't reprinted it. Would you mind sharing your CAD files? I would like to modify your angled design to accept an aluminum tube to create a very long (18" to 24") extension. Again thanks for all your effort in creating the design.

I had been wanting to get SRS up and running, so I really appreciate the online workshop, which made doing so very simple. I will try to help my flying buddies bring SRS up on their systems. Thanks for the help and developing the app for the community.:)

MFD cost increase? Has anyone noticed that TM Cougar MFDs are now selling for $130 at Amazon and other online flight sim stores. A buddy and I are wanting to split the pair so we each have three MFD's for the F18. Luckily, I was able to purchase a set from a real world aviation store MYPILOTSHOP.COM for $75 + shipping.

Terry, Great work! I am printing one now. Have you thought of posting your files over at Thingiverse.com, where they would be exposed to a much wider audience?

HomeFries, Any anticipated date for an F/A-18 profile?

AV8B Custom Lua? HF, I just ran the CTSupdate.exe and I noticed according to the change log the Custom LUA for the AV8B is supposed to be ver 2.05, but what I have after the update appears to still be version 2.04 with a file date of 12/17/2017. I also tried a full install with the same result. It may be just me but thought I'd ask.

I ordered my Jetseat on Jan 21st, Andre promptly shipped it on Jan 22nd and it arrived on Saturday Feb 3rd. For those interested in the shipping the details from Russia to Denver, CO attached is a picture of the shipping log. Installation was easy and it works as advertised. I agree with the consensus of the posts here: The JetSeat adds considerable to the feeling of flying and a whole new dimension to the VR experience. The attachment straps just *barely* fit around my office chair, which I bought from Costco. I may make a set of extension straps, but this won't be a problem when I build my flight chair.

Hey Bucko, "I also let the Nvidia "GPU tweak" program shutdown what it considered unneeded Windows processes. " What nVidia Tweak program did you use?

All the positive comments about the JetSeat and kudo's for Andre's great customer service has convinced me to place my order today. I am looking forward to receiving my JetSeat.

Thanks for the batch file suggestion. I'll had thought of doing that, but like you noted kinda clunky, but I'll give that a try. BaD CrC: That is an interesting possibility. Life would be so much simpler if DCS would incorporate a command line parameter to specify the graphic config. I wonder if Skatezilla could incorporate the graphic configuration file swap in his DCS Configuration Update Utility in the start in VR function?

It appears DCS doesn't allow assigning the VR or mouse functions to keyboard characters. My workaround is using an ancient Belkin Nostromo N52 keypad on my left like you are attempting. I have programmed keys for VR functions, mouse functions, general functions (i.e. quit, pause, active pause, frame rate display, control input indicator and cockpit camera position). I setup a N52 profile that maps the keys to DirectInputs (DI's), which the DCS recognizes as joystick buttons and will accept for the VR and mouse commands. I doubled the numbers of commands on the keypad from 24 to 48 by using one of the joystick buttons on the stick as a modifier. I am happy with the way it works.

Has anyone found a way to have two sets of graphic configurations and be able to start DCS with a command line parameter specifying which configuration setting to use? One configuration would be optimized for use with a monitor and Track IR, while the second would be optimized for VR. I am aware of the --FORCE ENABLE VR/--FORCE DISABLE VR command line parameter, but that seems to only enable/disable VR and doesn't change graphic quality settings. Is there a command line parameter to specify an alternate graphic configuration? I had considered doing second installations of DCS1.5/DCS2.1, which are optimized for VR, but that takes up precious amounts of M.2 NVMe space. It would be better to be able to switch graphic configuration files before or at startup.

I do both. When DCS starts in VR with the Vive, it is only partial screen even with the USE FULL SCREEN ticked. I then press ALT+ENTER to make it full screen.

VR Functions in Home Fries TARGET profiles Home Fries has added basic VR support to his TARGET profiles v1.68 for TM Warthog/MFD users. https://forums.eagle.ru/showthread.php?t=116454 His A10C profile preserves the HOTAS functions while allowing VR recenter, VR zoom, mouse button left/right and mouse wheel forward/back to also work from the TM WH Stick's H1 switch. You can choose whether you want these functions to be immediately available or as shifted functions. You also get double duty out of many of the other HOTAS buttons and switches for instance using the China Hat in a shifted state as the landing gear switch. His profiles also provide the same VR functions in all the other DCS a/c. I was flying with his profiles before I got the HTC Vive so it was easy to bring those over into VR. At my request, he added basic VR support in the latest version ("1.68") . I am sure would be open to further enhancements from VR users. I find a combination of "braille" and mounting the Cougar MFD in the "right" physical space make them usable for VR. With HF's TARGET profiles you get double or in some cases triple use of the MFD switches. The rockers and the switches adjacent to them are easy to find in VR. You do have to memorize the the 2nd/3rd functions and admittedly it is often easier to just "look and click" if they are cockpit functions. However for non-cockpit functions, like bringing up and paging through the kneeboard, the MFD's switches work well. I think the ultimate VR destination for me will be scale cockpit with the most used switches implemented, but in the mean time the TARGET profiles gives me a lot of additional capability.

I have this issue as well, even with the "confine the cursor" box ticked and running in full screen mode, it doesn't keep the cursor from moving out of the DCS screen. I run more than one monitor and it is too easy to move the mouse too much so Windows looses focus. I try to only use the buttons on my HOTAS for mouse control, but often forget and grab the mouse. I have tried reducing the DPI on the mouse to a minimum and even thought of installing the mouse in a captive dock while flying DCS.

ditto

Any update on the resolution of this problem? Attached is a screen capture of the A10C in 1.5.5 sitting on the ground with the game paused. It only seems to happen in DCS. I haven't noticed it occurring in IL2 CLOD, IL2 BOS, or MSFSX. When it happens in flight, the systems stutters badly.