71st_Mastiff Posted March 19, 2019 Posted March 19, 2019 Axis do not work with the F-14B RIO...Virpil T-50 Mongoose. "any failure you meet, is never a defeat; merely a set up for a greater come back", W Forbes. "Success is not final, failure is not fatal, it is the courage to continue that counts", "He who never changes his mind, never changes anything," Winston Churchill. MSI z690 MPG DDR4 || i9-14900k|| ddr4-128gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || G10 RGB EVGA Keyboard/MouseLogitech || PiMax Crystal VR || 32 Asus||
imacken Posted March 31, 2019 Posted March 31, 2019 Pleased to say the copying of the view.lua file from stable solved all my orange entries in all modules! Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
imacken Posted April 3, 2019 Posted April 3, 2019 (edited) I am amazed that this OB build has been moved to the stable release considering all these controller issues. Stating the obvious, but best not to update stable release and lose the view.lua file that gives us the workaround. Edited April 3, 2019 by imacken Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Redglyph Posted April 3, 2019 Posted April 3, 2019 I am amazed that this OB build has been moved to the stable release considering all these controller issues. Stating the obvious, but best not to update stable release and lose the view.lua file that gives us the workaround. I don't think they read this thread unfortunately, they would have acknowledged by now. System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR
imacken Posted April 3, 2019 Posted April 3, 2019 I don't think they read this thread unfortunately, they would have acknowledged by now. Well, that's disappointing if true. I believe they read every thread here. Also, there are other threads on this issue. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Redglyph Posted April 3, 2019 Posted April 3, 2019 Well, that's disappointing if true. I believe they read every thread here. Also, there are other threads on this issue. I may be wrong, but normally a bug is tagged [REPORTED] (or other tags like "not a bug" and so on). We can see an example below in another thread - actually there is only one I can see. Otherwise we bug reporters wouldn't be able to know whether they are aware of a problem or not, that would make reporting bugs very problematic, and not motivating at all. System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR
bemme Posted May 10, 2019 Posted May 10, 2019 Hello everyone, is there a way to bind the Huey "carg view" to HOTAS-X ?
imacken Posted May 10, 2019 Posted May 10, 2019 I may be wrong, but normally a bug is tagged [REPORTED] (or other tags like "not a bug" and so on). We can see an example below in another thread - actually there is only one I can see. Otherwise we bug reporters wouldn't be able to know whether they are aware of a problem or not, that would make reporting bugs very problematic, and not motivating at all. Completely agree with all you said. Unfortunately, bugs are not always marked as [REPORTED] which does make life difficult and frustrating at times. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Ewertsp Posted July 25, 2019 Posted July 25, 2019 (edited) Damn, after years playing dcs, this problem got me yesterday. I lost like 90% of my keyboard binds for the M2K, not sure if there's more. I just can't modify the binds, it's kinda crossed out. My dcs is always uptodate and last download I did was NTTR and f18 agressor campaign I bought last week. Already deleted DCS user folder and repairing afterwards. I tried deleting DCS game folder/inputs and mod folder too, the problem remains... Haven't tried to roll back dcs version yet. Any ideas? S! Edit: HAAA! https://www.facebook.com/RazbamSims/posts/2325547244198567 Edited July 25, 2019 by Ewertsp
Redglyph Posted July 25, 2019 Posted July 25, 2019 https://www.facebook.com/RazbamSims/posts/2325547244198567 FB? What a strange place to post that. Soon we'll see business announcements on Flixter and Classmates too :D System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR
nobuttons Posted February 24, 2021 Posted February 24, 2021 (edited) OMG this just bit me in the ass. Spent 45 mins applying new bindings to my new throttle. Went to configure axis. Set up the eft throttle, and bam! It not only locked me out of doing any more axis bindings, but it cleared all my other bindings I had just set! Edit - Open Beta, F14 module Edit 2 - I have a work around, which is to quit steam VR before editing controls... somehow that's made it all stick? Edited February 24, 2021 by nobuttons SYS : RYZEN 9 5950X + Crosshair VIII Hero + RTX 3090 FE 32GB + TridentZ NEO 32GB 3600MHz + FireCuda 520 1TB VR : Pimax 8KX : DCS 1.0, VR, Steam 100% (3148x3160), FOV 120 degrees || Quest2 || Index || Reverb G2 SIM : DCS || Star Wars Squadrons || Rise of Flight || IL2 Battle of Stalingrad || Elite Dangerous || Star Citizen DCS: Textures & Terrain High, Water & Vis Medium, Heat Blur Low, Shadows Medium, MSAA 2x, DoF OFF, Lens Flare Only, Motion Blur Off, SSAA & SSLR Off, Clutter 170, Trees 66%, Smoke 0, Anisotropic 2x, Terrain Shadows Flat, Cockpit Global Illumination On PIT : VKB Gunfighter base + VKB F14 grip || VKB Kosima grip + Virpl TC50 CM3 throttle + Logitch G pedals + Pimax Leap Motion hand tracking + SimShaker feedback
Recommended Posts