TWC_Alamo

Great job on the Hawg! While working on building a HOTAS profile for the '47, I noticed three issues with keyboard commands not working. (1.) Horizon Cage/Uncage keyboard command "RShift + V" will only UNCAGE the artificial horizon. It will not CAGE it. (2.) Oxygen regulator Diluter lever Auto-Mix On-Off keyboard command "RShift + B" doesn't activate the lever. (3.) Oxygen Regulator Emergency By-Pass Value keyboard command "RCtrl + B" does not activate valve.

Temporary P-47D TARGET Profile I know Home Fries is or will be working on a new profile for the P-47D module, but if you are like me and your muscle memory is so tuned to the "buttonology" of his profiles, that it just doesn't feel right to fly without them.:huh::cry::( So, as a "stop gap measure", I have put together a "TARGET P47D kb v228.diff.lua" and "TARGET P47D wh v228.diff.lua" files for the P47D that will work with his P-51D TARGET profile. (Sorry no Cougar profile, since I don't have one.) Also included are JPEGS showing the mappings for the MFDs, Warthog Stick and Throttle. Installation is simple, just select Home Fries's TARGET P-51D profile and install the above mentioned lua input files for the P47D DSs keyboard and TM Virtual Controller. Since I had to adapt the mappings to work with the existing TARGET P51D profile, don't expect the normal level of sophistication with long tempo and short double presses, but all the basic function seem to work with un-shifted and shifted (i.e. +S3) buttons. I noticed some functions aren't working in the P47D module (it is early access) from the keyboard, like the artificial horizon toggle (you can "un-cage", but not "cage" it.) The O2 regulator key commands aren't working either, so I didn't include those in the profile. Thanks to Home Fries for creating this incredible tool for DCS that some of us have become so dependent on.:thumbup::thumbup::thumbup: I hope these work for you until the genuine Home Fries P47D profile becomes available. Don't complain or ask for help from Home Fries if you have problems with this. It is a monster of my own creation and he had nothing to do with it, but PM me and I'll try to help you out. P47D_TargetProfiles.zip

Lorthirk, Excellent! I like your solution. I find it annoying to have to re-install the Windows Store when I am forced to get an App there.

Thanks Lange for the confirmation that it still works. I think yesterday I had my head up one of my wheel wells! Spent all day trying to make it work with no luck and gave up about midnight. Amazing what a good night sleep and a fresh mind will do. First thing this morning I tried it again and had no problem changing it using the 20200325 version. I didn't understand the sequence of steps needed to create a profile, calibrate it, change the HWid and then upload it to the T50. I thought after I created a profile and changed the HW ID, it was automatically writing it to the T50. I didn't understand that I needed to use the :LOAD VPC DEVICE" button.

Help changing VID/PID Cyph3r, I just received my T50.CM2 base and I'm trying to configure it to work with my T.A.R.G.E.T. scripts. However it appears your software no longer allows you to change VID/PID's. It refuse to accept the change and reverts back to the original HW id (03EB/2046). Can you confirm if it is still possible to change the T50's hardware IDs? Or am I doing something wrong? I love the quality and smoothness of the T50 base, but I need to use some very complex TARGET scripts. Any help would be appreciated. Thanks Alan

I just received my T50.CM2 base and 200MM extension upon which I have mounted my TM F/A-18 grip. I am super impressed with the quality and the smoothness of the action. However, I am quickly becoming disappointed. It appears that VIRPIL no longer allows you to change the hardware id of their devices to work with TARGET. I thought I had researched this thoroughly and saw several posts of people doing this exact same thing. (for ex. https://forums.eagle.ru/showthread.php?t=254002&highlight=TARGET). Before I placed my order, I read the VIRPIL Advanced Software configuration guide, which shows where you can change the VID/PID in firmware. However there was nothing about *NOT* being able to change VID/PID. Maybe I am doing something wrong. After I change the VID/PID to 044F/0402 and tap CREATE PROFILE it acts like it is doing it, but then comes back with the original VID/PID. I use some very complex TARGET scripts and this would have been a definite deal killer had I known they eliminated this capability. I hope I am doing something wrong. Can someone confirm that VPC no longer allow you change hardware ID's in order to work with TARGET scripts?

Is it possible to have a separate MissionScripting.lua file for each server instance running on the Dedicated Server? For instance if I want to enable Persistency on only one of the three severs running on the dedicated server by commenting the lines shown in the MissionScripting.lua (below), but not allow it on the other two instances? do sanitizeModule('os') --sanitizeModule('io') --sanitizeModule('lfs') require = nil loadlib = nil end

I can't attest to the accuracy of these, nor I have printed them, but they might be a starting point, especially if you are going for a "VR braille" cockpit. https://www.thingiverse.com/thing:3759861 https://www.thingiverse.com/thing:3781639

Baltic Dragon: Wow! Well maybe to expand a little on that: I have never had as much fun doing the DCS Training Missions as with the ones for the Harrier. I bought the AV8B when it first came out but put it aside after seeing how incomplete it was and how "ham handed" I was handling it. Coming back to it two years later is almost like having Christmas all over again and discovery your training missions is making it much easier than the first time with only a few Youtube videos to watch. Just a couple of comments after a few days working my way through the missions. I have just completed M09, so I still have several more to go. (1.) The night missions really makes the Harrier shine. :huh: However the white narrative text makes do them difficult in VR. For instance in the night version of M07, it is like having a 1000 watt spot light shinning in your face while trying to see the KC130 and drogue. Although the text is up and to the right, it is so bright it cause all kind of reflection in the HMD. I assume there is no way to dim the text. Would it be possible to have a F10 menu option to toggle on/off the text? (2.) After going through a training mission a number of times, I would like to be able to repeat the mission on my own without the narration and prompting. Could that also be an F10 menu option to run the mission without the instructor? If that would make them too complicated to program, another option would be to provide a "solo" version of the missions as INSTANT ACTION. This would definitely improve the quantity and quality of the IA missions for the Harrier. Thank you for this outstanding set of missions. I agree with others who have said these are the absolutely best training mission in the whole DCS fleet.

I just tried this mission today (1/16) and had the same result. Luckily the air start sub parts work okay. BD you have really done some outstanding work! Thank you.

Does anyone know how disable the blue and white WMR Debug Cross Eye Alignment Tool that popups when you start DCS in VR? I have the Samsung Odyssey Plus HMD and this menu pops up every time I start DCS in VR. My settings are fine and I always just "X" out of it. Based on BigNewys sticky thread (WMR DEBUG TOOL - cross eye alignment), I tried creating an autoexec.cfg file with the following entry: force_cross_eye_recovery_tool = false in my saved games\DCS\config\ folder, but it didn't work. It would be nice to eliminate this mouse click, especially when startup without the HMD on.

Sometimes, I have to right click and select "run as administrator" to make TRACKIR work, even though I have "run as administrator" set in the short cut properties.

Yep, same here.

HomeFries has a really slick interface for managing comms in his TARGET profiles. It uses the Mic switch along with Stick hat switches H2, H3, & H4 to control in game radio calls. It also integrates in game comms with the use of VAICOMPRO/SRS/Discord and is consistent across most DCS Modules. https://forums.eagle.ru/showthread.php?t=116454

What is the best practice in setting up VOICE CHAT when running multiple instances of the DCS Dedicated Server on the same machine? According to Note 1 in this post: https://forums.eagle.ru/showthread.php?t=256203 the server will use port 10309. Note 2 shows how to change the voice chat ports, but warns that clients are pre-configured for port 10309 and would also have to reconfigure to the same port as well. Having three instances of the server running on the same machine would therefore, require opening up two additional ports other than 10309. However clients wouldn't be able to access the voice chat on the other two without manually editing their configuration. Will enabling the UPNP option solve the problem? If all servers use 10309 would clients on different severs be on a "party line"? Luckily this appears to be a transitory issue and be resolved when ED fully integrates VC where it will use the games port #.

Mystery Solved! Thanks to DiscWalker for the PM pointing me in the right direction. I need to be more vigilant in reading the change notes on the updates. What happened makes perfect sense now. :thumbup: From a post in the DCS World 2.5/Bugs and Problems/Voice Chat https://forums.eagle.ru/showthread.php?t=256203 Note 1 for server hosters ONLY. Voice chat system use port 10309. Routers with upnp option will translate that port automatically (tested) as soon as DCS server launched. But some routers can't do it due to unknown reason. In case of your clients doesn't hear one another (and even doesn't see one another in VC panel) just manually translate that port for both TCP+UDP protocols. So does this mean that if we run three servers on one machine, we will need to open two more ports in addition to 10309? However There was a caution about problems for clients, if the server use a different port than 10309.. Note 2 for hosters: to change VC port add line webrtc_port=XXXXX into 'Saved Games\%DCS_SERVER_HOME_FOLDER%\Config\autoexec.cfg We do not recommend to change this port because of client should do the same. In future planned to incorporate sound stream into main DCS network data and use one port for both DCS and Voice Chat.

Yesterday, before applying the latest (Dec 4th) update, all three of my servers were running the DCS dedicated server openbeta just fine. The servers run on the same box using ports 10307, 10308, and 10309 respectively. Because of the recent restriction of only two servers per account, servers 1 & 2 are attached to the first account and server 3 on the second account. After the Dec 4th update, everything seemed normal. I was able to manage each server by logging into their DCS account. However; my BuDs began complaining about their clients hanging up while loading the mission on server 3. The other two servers were fine. This mission, the 476th vFG NTTR mission, had been running without problems for months. Thinking it was something to do with the mission, I loaded the same mission that was running on server 1. However clients continued to hang while loading this mission as well. The logs showed no problems and all mangement functions of server 3 through the DCS web worked. Server 3 was showing up on the master list of servers. The client would hang while loading whether connecting through the master list, or directly with IP address, using either internal LAN IP or external IP. Thinking it may be something to do with the DCS account, I tried switching server 3 to account #1 and server 1 to account #2. However, clients still would hang on server 3. So I next thought there must be something wrong with the instance of server 3. I did a line by line comparison of autoexec.cfg, options.lua, serverSettings.lua, and dedicatedServer.lua. They all appeared identical except for server name, game port # and WebGui port. Maybe there was something else in the files that I was missing, so tried copying the entire server 1 save game directory and changing server name and ports to make a new server 3, but that didn't fix the problem. The only difference between the three instances are server name, dcs port # and WebGui port and DCS account. So on a wild hair, I swapped the port #s, between servers 1 and 3. Then server 3 (running on port 10307) began working; however server 1, running on port 10309, began hanging up clients when the mission loads. The port number must be the problem!:smartass: I checked port forwarding in my router, which is forwarding the range of ports 10307 thru 10309. I also checked that the Windows firewall is set to allow connections to DCS Dedicated Server. I next changed the router to allow the range of ports to include 10310 and assigned server 3 to port 10310. That worked. However,t none of servers will work on port 10309. So for the time being I am leaving server 3 on port 10310 and scratching my head about port 10309. Anyone have an idea why port 10309 won't work? :helpsmilie:What computer, DCS or networking issue would allow correctly managing the server through the web interface, but cause clients to lock up while loading any mission? Even more perplexing is server on port 10309 worked before the update on Dec 4. Sweet mysteries of life and DCS! Gee, I could have spent my afternoon flying DCS rather than this.

Rather than having a somewhat useless splash screen taking up desktop space, I wish ED could add some useful information to it. Like a "heartbeat" or status indicator to indicate all is well and it listed on the master, time in current mission and number of logged in users. But as my grandma used to tell me "wish in one hand and spit in the other and see which gets full the fastest." ;-) ;-) ;-)

My servers have not de-listed in the last 48 hours.

Since making the additions suggested in Post #83, my servers have been rock solid. I hope that statement doesn't jinx me! Since that has been added to the update, do we need to remove those statements from the autoexec.cfg?

For VR flying I've settled on 3 elements to avoid touching the keyboard and mouse. (1.) Homefries' TARGET Profiles for all normal HOTAS (and adding an extended set of a/c commands on the HOTAS, like landing gear, hook, master arm, etc.) (2.) VAICOMPRO for communication with in game AI and Voice Attack for view and sim management ("show flyby", "show map," "labels on", "active pause on" etc.) (3.) PointCTRL for everything else in the cockpit.

Anyone looking for an inexpensive way to get into VR? https://www.newegg.com/p/N82E16826190064

I have on my "todolist" a task to explore if it is possible to have VOICE ATTACK to send a command to Windows to reset focus on DCS. I also use Miles' PointCTRL system and that does help a lot, but you can still inadvertently bump the mouse.

Yoyo, I fly in VR with TARGET profiles every flight. There is a problem with TARGET and the Microsoft Windows Store App that causes some systems to not hide the physical TM controllers when the virtual TM control is activated. Take a look see at this thread for the solution: https://forums.eagle.ru/showthread.php?t=232737

Is the two simultaneous logons per account still in effect?