Gannet Posted November 26, 2012 Posted November 26, 2012 Hi Chaps I may of course be doing something stupid, but I'm getting a problem that has occurred in P51 campaign and also some FC3 missions. Upon loading I have no mouse or joystick input. I can hit esc to abort mission and the F keys views work as does TIR. Mouse commands do not work and there is no joystick or axis input (TM WArthog). Alt/tabbing doesn't help. I have unticked "disable Aero". A baffled gannet. See attached track if this helps.no control p51 C1.trk i7 8770 4 16MB RAM Geforce GTX 1070 8GB, Win 10 64, TH Warthog Hotas, Saitek Pedals, TIR5, Woodburning Stove, Dog, Zamberlan boots, P&H Kayak, Getaway Car[sIGPIC][/sIGPIC]
Sabre-TLA Posted December 31, 2012 Posted December 31, 2012 Is the mouse seen in the Options, Controls? MapleFlagMissions - Read Our Blog for Updates
Gannet Posted January 11, 2013 Author Posted January 11, 2013 Hi Sabre Yes, all the profiles are visible. I'm getting similar problems with Ka-50 too. Got a felling its something to do with windows and the Aero problem, as there seems to be a flickering and visibility of desktop icons when I move the mouse (cursor is visible, just can't click on anything). Keyboard also occasionally doesn't respond. Can sometimes get it back by alt-tabbing but not always. Cheers i7 8770 4 16MB RAM Geforce GTX 1070 8GB, Win 10 64, TH Warthog Hotas, Saitek Pedals, TIR5, Woodburning Stove, Dog, Zamberlan boots, P&H Kayak, Getaway Car[sIGPIC][/sIGPIC]
SkateZilla Posted January 11, 2013 Posted January 11, 2013 ALT-TAB to desktop, ALT-TAB Back to DCS, Mouse Cursor should be restored to DCS. make sure "Disbable Aero Interface" is unchecked. make sure you're not clicking stuff when the sim transitions from menus to the 3d Renderer. make sure you dont have programs running that monitor the mouse or trigger windows aero events. (Usually IMs do this). Once it does it once, the only way to clear it, is to shut down the system, and boot it back up. POWER OFF, NOT SLEEP/SUSPEND. as It has to close all the processes. Skype, FRAPS, and team Speak all seem to trigger windows to Fight with DCS over the Cursor for me. 1 Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
Gannet Posted January 12, 2013 Author Posted January 12, 2013 Thanks Skate I've followed these issues from other threads but could never quite get the scenario to match mine.. I've got it going again, for now. "Disable Aero" unchecked, start DCS from reboot and hands behind my head whilst loading the 3D render. :-) I've been playing with these settings for a while and it all seems a bit hit and miss. I had a visible cursor but couldn't click, keyboard comes and goes, and joystick was inop. Alt-tabbing currently working so I'll hold my breath and endeavour to persevere. Cheers aye. i7 8770 4 16MB RAM Geforce GTX 1070 8GB, Win 10 64, TH Warthog Hotas, Saitek Pedals, TIR5, Woodburning Stove, Dog, Zamberlan boots, P&H Kayak, Getaway Car[sIGPIC][/sIGPIC]
Loz Posted January 13, 2013 Posted January 13, 2013 ALT-TAB to desktop, ALT-TAB Back to DCS, Mouse Cursor should be restored to DCS. Skype, FRAPS, and team Speak all seem to trigger windows to Fight with DCS over the Cursor for me. Thanks for this SkateZilla. Couldn't work out why my mouse buttons could not be bound like they used to. Disable Skype from starting up with windows and hey presto. Mouse buttons bind-able as before. :) Deserved Rep Inbound :D i9 9900x at 5.1 Ghz // ASUS ROG Maximus XI Formula EK Bloc // 64Gb Corsair Vengence 3600Mhz DDR4 Ram // Gigabyte Aorus 3090 Watercooled block//Samsung SM951 M2 x4 SSD // Windows 10 64 Bit //48inch LG48 @ 3840x2160 120Hz//Asus ROG Swift PG35VQ 3440 x 14440 144Hz // TM Warthog HOTAS (Ser. No. 00836) //MFG Crosswind Pedals // TrackIR 5 //Varjo Aero An old pilot is one who remembers when flying was dangerous and sex was safe. My YouTube DCS World Four Screen Videos
Gannet Posted February 6, 2013 Author Posted February 6, 2013 In case it's useful to anyone, I found the problem to be a Touchbase touch screen driver that was loading at start up (tbdaemon.exe). This was crashing when starting the 3d render. Once disabled this solved the locking/crash problem. Cheers i7 8770 4 16MB RAM Geforce GTX 1070 8GB, Win 10 64, TH Warthog Hotas, Saitek Pedals, TIR5, Woodburning Stove, Dog, Zamberlan boots, P&H Kayak, Getaway Car[sIGPIC][/sIGPIC]
Recommended Posts