Quietman2000

Great campaign so far! I wanted to mention a minor "issue" that I encountered. Mission (#6 I think) -- "A Bloody Nightcap" I just started the mission and the NVG (night vision goggles) were not available by default. The JHMCS seems to be the selected HMD. I restarted the mission and then had the ground crew change the helmet mounted device to the NVG and all was good. DCS v2.5.6.61527 (non-steam)

Just started flying SH2 and like it so far, but I did run into an issue in Mission 1. (regular refueling option) The tanker didn't appear in the airspace at all. It wasn't on the F10 map, nor could I get it on Tacan (10X) or on the radio. I had taken out both SU-25's and got the radio message that refueling was an option. Digging into the mission file, the tanker has "HIddon on Map" and "Late Activation" checked. I skimmed through this topic and didn't notice any posts about this issue. Thanks!

Hello, Quick question to get DCS-BIOS to Autostart with DCS... Is there a way I can manually configure DCS-BIOS to autostart (by creating or editing a file somewhere)? I have DCS installed in a non-standard folder, -AND- I have my Users folder on another drive (didn't want it on my primary SSD). I was able to get the DCS-BIOS Virtual Cockpit connection to work by manually adding the line to the Export.lua file. When I try checking "Autostart DCS-BIOS" in the web setup, I get the message, "error: profile directory does not exist, please start and exit DCS and try again: C:\Users\[uSERNAME]\Saved Games\DCS" The actual path is: E:\BackMeUp\Users\[uSERNAME]\Saved Games\DCS There must be a symbolic link for the C:\Users folder, because if I type a path of C:\Users\[uSERNAME]\Saved Games\DCS into Windows Explorer's address bar, it finds the DCS folder in the E drive. Thanks, --Doug

colo, Thanks again for continuing to work with me. I hope all goes well with your surgeries and that you can get off the pain killers soon. I now have the AMPCD working -- changing the resolution from 600x600 to 400x400 fixed it without any other changes. See the more detailed information below. I still am having issues with the aspect or stretching of the UFD. Is there a width & height should I try for that? AMPCD Details: As I paid more attention to the AMPCD screen, I noticed that it wasn't showing another gage in an old location, it just showed what was in the screen before I switched to the AMPCD. If I had the Left MFD active when I swiped "up" to switch to the AMPCD, it would show the old image from the MFD (not updating). Same thing would happen if the right MFD was displayed when I swiped to the AMPCD. It would show the image of the Right AMPCD without any updating. I didn't notice this because I was always swiping from the Left MFd where I have the stores screen (which doesn't change much). When I went from 600x600 for the instruments to 400x400, the AMPCD worked! Could it have been a bandwidth issue for the color AMPCD display? Thanks, Doug

Hello, I've done quite a bit of searching and continue to have two other minor problems... 1) The F/A-18 UFC output is stretched in both my android displays. I've tried having the source be 600x600 and 600x480 (changing it in aInstruments as well). It changed the display's stretch, but still wasn't quite right. Is there a certain aspect ratio that it needs to be? For my monitor, I'd like to stick with a width of 600 pixels (or less). (see attached picture) 2) I can't get aInstruments to look at the correct part of the screen to see the F-18 AMPCD (CENTER_MFCD). It's like it's looking at a part of the screen I used in an earlier trial setup. The buttons control the AMPCD just fine. Am I missing a location where the screen coordinates for the AMPCD would be stored? (See below for what I've been updating) I've updated the Users\XXXXXX\Saved Games\DCS\Config\MonitorSetup\aInstruments.lua to the correct screen coordinates. (I moved the .lue to the Saved Games location so it won't get overwritten with updates.) I've also checked to make sure aInstruments didn't create a new aInstruments.lua in Eagle Dynamics\DCS World\Config\MonitorSetup. I've also updated the aInstruments25\App\config.txt to what should be the correct coordinates. Attached are my aInstruments.lua and config.txt files. The android devices show the screen location at x=5640, y=880, even though it's set up as 5040, 1580 in those 2 files. NOTE: The x value differs by 1200 pixels between the .lua and the config.txt. I have a 3 monitor setup and my left-most monitor is 1200 pixels wide. My main monitor and playscreen area start at 1200 pixels from the left. Thanks, --Doug aInstruments.lua config.txt

colo, Thanks for the quick response. I've e-mailed you a few debug.txt files created under different connection attempts. Windows IP Address: 192.168.0.104 Phone IP: 192.168.0.105 Tablet IP: 192.168.0.112 I'd really like to get this working, so I'm more than willing to work with you to figure this issue out, rather than request a refund. Thanks, Doug

Hello, I just purchased aInstruments today and have spent most of the day trying to get it all working. I'm impressed with it so far, but have run into an issue. For me, the "Autodiscover" tablets is not finding either of my devices (an android tablet and an android phone). I'm running the tablet app first, then start aInstruments on the Windows computer. I can connect each device manually, but only one will be connected at a time. I cannot get both devices to connect manually at the same time. When I click "Manual Connect," the T1 IP connects, while the T2 IP will not connect. When I enter both IP's, select "Manual", and 2 tablets, the status box says both connected, but both clients say "Waiting for Connection" If I select just one tablet and enter its IP, the tablet connects If I then select 2 tables and add the T2IP, both tables show "waiting for connection" (even though status says the second tablet connected also) It does the same thing if I reverse the order of my 2 devices. Interesting that when I try to connect 2 devices, the Detected tablets box lists only T2, but with the IP for T1 after the T2 label. aInstruments version 2.5 - 15122019 Any help would be most appreciated! Thanks, --Doug