unknown Posted June 28, 2016 Share Posted June 28, 2016 (edited) Hi all, i'm asking for confirmation for some problems i encountered in the open beta 1.5.4. I ask this because i don't know if this is a general problem or if this is related to some modifications done to the options.lua (preventing the black screen bug introduced in 1.5.4ob) and the trackir default.lua(problem with axis introduced in 1.5.4ob). I noticed that if i place the Mi-8 in the ME and start the mission my manual frequency selector is screwed up and i can't contact ATC, see picture below, frequency is 122.499 instead of 122.500. <- SOLVED! Also i noticed that if i use the cargo indicator everything works fine until i switch the "automatic cargo release", after that the cargo indicator is not working anymore, the position indicator(circle) is not moving. In some cases, perhaps if i'm to close to the cargo, DCS is crashing if i push the button for the cargo indicator function again. I hope somebody can confirm or not confirm this problems so i know if it's only a problem on my side and i need to do a repair or wait for the next patch or not. Thank you very much for your help in advance. :thumbup: Edited June 28, 2016 by unknown Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1 System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
ED Team PilotMi8 Posted June 28, 2016 ED Team Share Posted June 28, 2016 _and the trackir default.lua(problem with axis introduced in 1.5.4ob). it is general problem. ED will resolve it _I noticed that if i place the Mi-8 in the ME and start the mission my manual frequency selector is screwed up and i can't contact ATC, see picture below, frequency is 122.499 instead of 122.500._ such a small difference in frequency should not affect the radio (bandwidth is about 6 kHz). Another reason..we changed the default modulation: AM now, instead of FM. But it may just be a bug, we need track _Also i noticed that if i use the cargo indicator everything works fine until i switch the "automatic cargo release", after that the cargo indicator is not working anymore, the position indicator(circle) is not moving. In some cases, perhaps if i'm to close to the cargo, DCS is crashing if i push the button for the cargo indicator function again. will testing it Link to comment Share on other sites More sharing options...
lxvanwyk Posted June 28, 2016 Share Posted June 28, 2016 Also when alt tab is pressed then the FFB trim force disengages and Track IR is "unplugged". Press it again and track IR is plugged but FFB (trim function) is not. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
unknown Posted June 28, 2016 Author Share Posted June 28, 2016 _and the trackir default.lua(problem with axis introduced in 1.5.4ob). it is general problem. ED will resolve it I know, that was just to inform that i did modify both files in the way SkateZilla described it to fix these problems. I don't have the black screen or trackir bug anymore. I solved the problem with the radio! I installed the [Mi-8MTV2] "Vasilissa the Beautiful" HD Cockpit Mod which worked in 1.5.3 open beta but it seems not in 1.5.4. After changing the custom cockpit from "english" to "default" the radio problem was gone! That's why i was asking here if anybody else is having the same problems. I will test if the cargo indicator bug that i had is also related to this mod and report back here! Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1 System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
unknown Posted June 28, 2016 Author Share Posted June 28, 2016 (edited) As i sad in the posting above the problem of the not working radio because of the wrong frequency is solved, it was the english cockpit mod. But the problem with the cargo indicator still remains for me, can anybody else confirm this problem or is it only me? Edited June 28, 2016 by unknown Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1 System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
Cibit Posted June 28, 2016 Share Posted June 28, 2016 Both huey and Mi-8 crash after closing the cargo indicator window i5 8600k@5.2Ghz, Asus Prime A Z370, 32Gb DDR4 3000, GTX1080 SC, Oculus Rift CV1, Modded TM Warthog Modded X52 Collective, Jetseat, W10 Pro 64 [sIGPIC][/sIGPIC] Adding JTAC Guide //My Vid's//229th AHB Link to comment Share on other sites More sharing options...
unknown Posted July 1, 2016 Author Share Posted July 1, 2016 @PilotMi8 Thank you very much for fixing this problem with the newest update for the open beta. :thumbup: Your are working fast! :thumbup: Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1 System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
Teapot Posted July 4, 2016 Share Posted July 4, 2016 Also when alt tab is pressed then the FFB trim force disengages and Track IR is "unplugged". Press it again and track IR is plugged but FFB (trim function) is not. Yeah, this happened to me as well .. last night (I just bought the module). "A true 'sandbox flight sim' requires hi-fidelity flyable non-combat utility/support aircraft." Wishlist Terrains - Bigger maps Wishlist Modules - A variety of utility aircraft to better reflect the support role. E.g. Flying the Hornet ... big yawn ... flying a Caribou on a beer run to Singapore? Count me in. Extracting a Recon Patrol from a hastily prepared landing strip at a random 6 figure grid reference? Now yer talking! Link to comment Share on other sites More sharing options...
Recommended Posts