CrackerJack

+1

This has occurred for me in both Create Fast Mission and the Bear Trap Campaign. Easy Comm is on. Prior to entering runway I select 'Request Takeoff' and ATC responds with 'Abort Takeoff'? If I do not request takeoff via the comm menus then ATC will automatically deliver the takeoff clearance as I taxi on to runway. The issue only occurs when requesting clearance via the comm menus.

Thanks Hollywood that got me going. I've been I've been flying the F15C campaign Bear Trap in 1.5. I couldn't get 'Request Startup' to work and then I saw earlier in this thread that its a known issue so I added it in. But even after adding it in the command does not execute. I changed F1 to F3 and VoiceAttack recognizes it as a derived command but its not executed by DCS. When I call 'Request Takeoff' the voice command is recognized but it executes 'Abort Takeoff'?? Are there any comm changes in 1,5 that would cause this?? Anyone else have issues with 1.5 and FC3?

I've been trying out VAICOM for F15C. When I say "ATC Options" the list of options is displayed while I keep the PTT pressed I then say "Select One" but the option is not selected. As soon as I release the PTT after requsting "ATC Options" the list is cleared from the screen. I'm wondering if there is a bug? I would have thought that after requesting the ATC options I would release the PTT and then press PTT again to select from the list while it was displayed?

Looking forward to 2.0! This is a great tool, thank you for your efforts!

I was able to get the F15C profile loaded and for the most part everything has been great. The only issue is the TDC. I use the TM Warthog and TDC just jumps all over the VSD, its like its picking up some background input. When I fly the A10C the slew control works fine. Any suggestions because right now I have to use the keyboard. I didn't change anything in POLARIS1's profile. Thanks! EDIT Got this sorted out. For whatever reason I had to recalibrate my throttle in Windows. Once I did that the slew stick works fine, it also fixed the issue I was having with the slider for zoom.

I was just about to post a question about ILS Nav in the F15. I just started flying it and have no idea how to be certain I've selected the correct ILSN nav point. I have the same chart you've attached and I agree wholeheartedly that its very confusing as is. As you suggested the addition of the N number would be a great help! I guess the only way to do it now is to check range and bearing?

I also believe that its an SLI issue. I never had it until I used Nvidia Inspector and enabled SLI and AFR2. I'm running a GTX970 so the frame rates are good even with high settings.

This is for DCS 1.5 I'm not certain if the same behavior occurs in 1.2.X I'm running the TM Warthog. I noticed on my pre-flight checks that elevator and aileron deflections resulted in noticeable rudder deflections. I checked my Axis Command mapping and can't see a reason for this behavior. Is this normal??

Thanks I missed that step. I manually loaded each device profile and now the settings are there. The one issue I noticed is that the throttle slider for Zoom does not zoom smoothly, it goes from default view to a very zoomed in view with no transition in between?

Thank You! One other question what is a good utility to use to check FPS and GPU load while running DCS??

I thought that these profiles might work with 1.5?? Not sure if anyone has tested but I gave it a try and I'm not sure if its me or there is a compatibility issue with 1.5. I copied the Input folder into \saved Games\DCS.openbeta\config but when I load up the control settings in the sim the config files don't seem to be recognized. I noticed the the Joystick and Throttle lus files have what appears to be {.....} serial number in their names?? If anyone has got these profiles working in 1.5 I'd be interested in finding out. Right now I'm just interested in the F15C.

This is a noob question. When I load Nvidia Inspector I don't see DCS or Blackshark or anything DCS related in the list of profiles??? Does it have to be created??

I see that with 1.5 you still have to run in Full Screen mode to enable SLI which is a real bummer! I guess I can't have my Helios and SLI together :-(

Well I've been able to get much better results. I went back and did the speech training three more times but I was very deliberate about how I spoke - annunciation! This made s big difference. I guess speech recognition technology still has a way to go before it will be able to recognize everyday speech.

I've been using VoiceAttack but so far my results have not been good. The issue is that VoiceAttack rarely identifies what I'm saying correctly. I did some looking around to make sure I have the settings correct. I use the MS Voice Recognition not the default. I set Command Weight to 95. I've run the MS Speech Training a couple of times and I have tested my mic by recording a track and then listening to the playback. I can't believe I'm the only one whose is having issues with commands being recognized. What has your experience been? How many times have you run through the MS Speech Training?

Thanks Blooze! That did the trick.

I've been attempting to reset the default cockpit view for the A10C. I've used the numpad to adjust. The adjusted view is supposed to be saved as the default using "RAlt+Num0" but this doesn't appear to be happening. I'm not sure what file contains the default cockpit view either. Any suggestions?

I have a second touchscreen setup to run Helios. I recently added a seconded video card. I found that in windowed mode with SLI on the performance is MUCH worse than what you obtain from a single video card. I did some poking around in the forums and it appears that this is a known issue with SLI in windowed mode. Does anyone know if there has been any indication that this SLI issue will be addressed in DCS 2.0?

This is an amazing piece of work! Well done!

Very nice work! I've made a stand out of 4" pipe but I'm not happy with it. It gets in the way. If the offer still stands I'd be interested in the drawings :-)

Thanks Sobe. I looked at Loz's Readme file and he says that if you don't want the gauges to disappear then: "it is just a case of going to the input bindings for the Fuel Gauge panel and Engine Instruments and under "toggle hidden" remove those for Button 3, 4, 5, and 6. Then it won't disappear" I'm poking around with the Helios editor seeing if I can make the changes as Loz suggested above. If I get it working I'll let you know in case you're interested. EDIT: I was able to remove the bindings and they fuel and engine gauges no longer disappear. You need to select the fuel and engine panels in the profile and then click on "set hidden" and you'll see the key binds which you can then remove.

Well Cichlidfan you are of course correct. Last night I realized after some more testing that it wasn't AutoHotKey after all. I'll have to dig into Loz's profile and see if I can disable this.

I'm running Loz SM 2.1 A10C Helios. Recently I loaded AutoHotKey to map a button press and release on my HOTAS to Numpad 1 press and release. I noticed the engine guages display in the lower right of the screen disappears whenever I have AutoHotkey running. Is anyone aware of an issue between AutoHotKey and Helios??

+1 on PiedDroit's comment. I was going through the same process as you not long ago and settled on an ultrawide 34" monitor LG 34UM95. One thing to consider is if you have trackir you will usually be focused on the center of the screen, 3 monitors don't bring alot of bang for the buck in this case. With an ultrawide you get an expanded FOV without the bezels.