RagnarDa Posted March 4, 2017 Share Posted March 4, 2017 Ok update: After some ABAB-testing I've determined that starforce indeed seems to be the culprit. I don't have the issue when running unprotected. DCS AJS37 HACKERMAN There will always be bugs. If everything is a priority nothing is. Link to comment Share on other sites More sharing options...
ac5 Posted March 4, 2017 Share Posted March 4, 2017 Ok update: After some ABAB-testing I've determined that starforce indeed seems to be the culprit. I don't have the issue when running unprotected. Hi, and how do you disable this starforce? I don't find a file or running process in my system by this name.... Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair Dominator Platinum DDR4-3000 Graphics Card: ASUS NVIDIA GeForce RTX 3080 10GB Monitor ASUS PA 329 32" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 860 PRO 4 TB Windows 10 - 64 V. 2004 CH Pro combatstick, throttle and pedals Link to comment Share on other sites More sharing options...
RagnarDa Posted March 4, 2017 Share Posted March 4, 2017 Hi, and how do you disable this starforce? I don't find a file or running process in my system by this name.... You as the end-user can't disable starforce. It wouldn't be much useful if you could :) DCS AJS37 HACKERMAN There will always be bugs. If everything is a priority nothing is. Link to comment Share on other sites More sharing options...
spiddx Posted March 4, 2017 Share Posted March 4, 2017 Hi, and how do you disable this starforce? I'm pretty sure you can't as a consumer. Otherwise it would be a pretty lame copy protection. ;) aaaaaaaand sniped! ;) Specs: i9 10900K @ 5.1 GHz, EVGA GTX 1080Ti, MSI Z490 MEG Godlike, 32GB DDR4 @ 3600, Win 10, Samsung S34E790C, Vive, TIR5, 10cm extended Warthog on WarBRD, Crosswinds Link to comment Share on other sites More sharing options...
grunf Posted March 4, 2017 Share Posted March 4, 2017 Ok update: After some ABAB-testing I've determined that starforce indeed seems to be the culprit. I don't have the issue when running unprotected. Good to know, hope you'll fix it soon. It seems that the problem is not specific to Viggen, people are reporting weird issues with other modules too, maybe related. Link to comment Share on other sites More sharing options...
ac5 Posted March 4, 2017 Share Posted March 4, 2017 Ragnar, you might want to talk to BigNewy. It is suspected that this might be a general DCS World problem as several other aircraft seem to suffer from similar problems. BigNewy is collecting infos and trying to reproduce the problem to work with ED on this issue. Indeed. It is not a Viggen - only problem, but rather a DCS 2.0.5.2576 Update 1 problem. I have spent the better part of the morning testing, here the results: A-10C = Perfectly O.K. AJS-37 Viggen = Crashes down to the ground (gear up), gear goes down again, but the plane is damaged and the engine goes off, fuel, in spite of the full external tank = 0%. If starting in the air, it trims uncontrollably up, 20% Fuel (Only the fuel of the external tank, I suppose). BF-109 = Fuel on 0%, just managed to take off, then engine blocks. F-5 = Freezes completely DCS, CTD, regardless if in the air or ground. F-86 Sabre = Perfectly O.K. FW-190 = Exactly the same behaviour as the Viggen. KA-50 = Perfectly O.K. MIG-15 = Perfectly O.K. MIG 21 = Perfectly O.K. Mirage 2000C = Fuel OK, though no way to go to afterburner, even with the throttle full open. It stops at 84 instead of over 240 fuel flow. After about 30 seconds in the air, it trims uncontrollably up, like the Viggen, but much worse. P-51 = Perfectly O.K. SU-25T = Perfectly O.K. By the way, I have uninstalled and reinstalled that VC14 Runtime Visual C++ 2015 Redistributable Update 3 as instructed in the changelog. ED or moderators, please advise, or acknowledge. Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair Dominator Platinum DDR4-3000 Graphics Card: ASUS NVIDIA GeForce RTX 3080 10GB Monitor ASUS PA 329 32" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 860 PRO 4 TB Windows 10 - 64 V. 2004 CH Pro combatstick, throttle and pedals Link to comment Share on other sites More sharing options...
ac5 Posted March 4, 2017 Share Posted March 4, 2017 Forgot: Spitfire: Fuel on 0%, engine stops after a few seconds. Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair Dominator Platinum DDR4-3000 Graphics Card: ASUS NVIDIA GeForce RTX 3080 10GB Monitor ASUS PA 329 32" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 860 PRO 4 TB Windows 10 - 64 V. 2004 CH Pro combatstick, throttle and pedals Link to comment Share on other sites More sharing options...
ac5 Posted March 4, 2017 Share Posted March 4, 2017 You as the end-user can't disable starforce. It wouldn't be much useful if you could :) Of course, now I see, you are a 3Rd party developer. Well, hope this issue will be fixed soon. Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair Dominator Platinum DDR4-3000 Graphics Card: ASUS NVIDIA GeForce RTX 3080 10GB Monitor ASUS PA 329 32" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 860 PRO 4 TB Windows 10 - 64 V. 2004 CH Pro combatstick, throttle and pedals Link to comment Share on other sites More sharing options...
wolle Posted March 4, 2017 Share Posted March 4, 2017 Indeed. It is not a Viggen - only problem, but rather a DCS 2.0.5.2576 Update 1 problem. I have spent the better part of the morning testing, here the results: A-10C = Perfectly O.K. AJS-37 Viggen = Crashes down to the ground (gear up), gear goes down again, but the plane is damaged and the engine goes off, fuel, in spite of the full external tank = 0%. If starting in the air, it trims uncontrollably up, 20% Fuel (Only the fuel of the external tank, I suppose). BF-109 = Fuel on 0%, just managed to take off, then engine blocks. F-5 = Freezes completely DCS, CTD, regardless if in the air or ground. F-86 Sabre = Perfectly O.K. FW-190 = Exactly the same behaviour as the Viggen. KA-50 = Perfectly O.K. MIG-15 = Perfectly O.K. MIG 21 = Perfectly O.K. Mirage 2000C = Fuel OK, though no way to go to afterburner, even with the throttle full open. It stops at 84 instead of over 240 fuel flow. After about 30 seconds in the air, it trims uncontrollably up, like the Viggen, but much worse. P-51 = Perfectly O.K. SU-25T = Perfectly O.K. By the way, I have uninstalled and reinstalled that VC14 Runtime Visual C++ 2015 Redistributable Update 3 as instructed in the changelog. ED or moderators, please advise, or acknowledge. ac5, really nice summary. It behaves exactly like that on my end. I would even suggest that you double post this also in the main bugs forum to make sure the devs/moderators see it without having to look in a sub-forum. [sIGPIC][/sIGPIC] Intel Core I7 4820K @4.3 GHz, Asus P9X79 motherboard, 16 GB RAM @ 933 MHz, NVidia GTX 1070 with 8 GB VRAM, Windows 10 Pro Link to comment Share on other sites More sharing options...
ac5 Posted March 4, 2017 Share Posted March 4, 2017 ac5, really nice summary. It behaves exactly like that on my end. I would even suggest that you double post this also in the main bugs forum to make sure the devs/moderators see it without having to look in a sub-forum. Done: https://forums.eagle.ru/showthread.php?p=3069205#post3069205 Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair Dominator Platinum DDR4-3000 Graphics Card: ASUS NVIDIA GeForce RTX 3080 10GB Monitor ASUS PA 329 32" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 860 PRO 4 TB Windows 10 - 64 V. 2004 CH Pro combatstick, throttle and pedals Link to comment Share on other sites More sharing options...
Quigley Posted March 4, 2017 Share Posted March 4, 2017 Seems Mi-8MTV2 also. I was cruising around Nellis when suddenly heli went vertical and violent spinning, finally tail boom broke off, crashed Link to comment Share on other sites More sharing options...
Mud Posted March 4, 2017 Share Posted March 4, 2017 I reckon they've moved the Bermuda Triangle ;) Spoiler W10-x64 | Z390 Gigabyte Aorus Ultra | Core i7 9700K @ 4.8Ghz | Noctua NH-D15 Corsair 32Gb 3200 | MSI RTX 3080ti Gaming X Asus Xonar AE | TM Hotas Warthog MFG Crosswind pedals | Valve Index Link to comment Share on other sites More sharing options...
Goblin Posted March 4, 2017 Share Posted March 4, 2017 The Viggen works fine for me, in DCS2. I noticed, however, that I was never asked to enter the serial for the Viggen or the Spitfire modules, when I installed them... Link to comment Share on other sites More sharing options...
grunf Posted March 4, 2017 Share Posted March 4, 2017 The Viggen works fine for me, in DCS2. I noticed, however, that I was never asked to enter the serial for the Viggen or the Spitfire modules, when I installed them... If you have them installed in 1.5, I thing it's normal. The keys are stored in the registry and activated for all DCS versions. Link to comment Share on other sites More sharing options...
RagnarDa Posted March 4, 2017 Share Posted March 4, 2017 I've noticed that starting the Viggen from ramp works as far as I can tell. DCS AJS37 HACKERMAN There will always be bugs. If everything is a priority nothing is. Link to comment Share on other sites More sharing options...
Mud Posted March 4, 2017 Share Posted March 4, 2017 I always start from ramp, RagnarDa. No dice though on my end. Spoiler W10-x64 | Z390 Gigabyte Aorus Ultra | Core i7 9700K @ 4.8Ghz | Noctua NH-D15 Corsair 32Gb 3200 | MSI RTX 3080ti Gaming X Asus Xonar AE | TM Hotas Warthog MFG Crosswind pedals | Valve Index Link to comment Share on other sites More sharing options...
RagnarDa Posted March 4, 2017 Share Posted March 4, 2017 Ah too bad DCS AJS37 HACKERMAN There will always be bugs. If everything is a priority nothing is. Link to comment Share on other sites More sharing options...
Goblin Posted March 4, 2017 Share Posted March 4, 2017 If you have them installed in 1.5, I thing it's normal. Ah! Yes, I do... No mystery then. Thanks! :) Link to comment Share on other sites More sharing options...
drPhibes Posted March 5, 2017 Share Posted March 5, 2017 [Note: I cut out some of the irrelevant parts of the following quote] Indeed. It is not a Viggen - only problem, but rather a DCS 2.0.5.2576 Update 1 problem. I have spent the better part of the morning testing, here the results: AJS-37 Viggen = Crashes down to the ground (gear up), gear goes down again, but the plane is damaged and the engine goes off, fuel, in spite of the full external tank = 0%. If starting in the air, it trims uncontrollably up, 20% Fuel (Only the fuel of the external tank, I suppose). BF-109 = Fuel on 0%, just managed to take off, then engine blocks. I'm not seeing any of the problems described here. The Viggen and all other aircraft I tested are working as expected. I just set up a simple mission at North Vegas, and tested ramp start, parking (hot) and runway. All mods disabled. Fuel set at 100% in the ME. Ramp start: - The gear was down on mission start. - Everything started up as expected. - ~100% fuel according to the gauge - Takeoff was normal. Radar works when airborne. Parking (hot): - Gear down - Fuel: 100% - Radar works Runway: - As above. No problems. Air start (multiplayer, AO server): - Everything works as expected. I did all the same tests with the Bf109, and the fuel load was 100% in all cases. I also tested the Spitfire in MP (AO server) with no fuel-related problems. Link to comment Share on other sites More sharing options...
drPhibes Posted March 5, 2017 Share Posted March 5, 2017 (edited) That's the only fault I've seen so far. Can't re-arm the vigg. Haven't tested that with any other planes yet. Edit: re-arming the F86 works. Edited March 5, 2017 by drPhibes Link to comment Share on other sites More sharing options...
Sporg Posted March 5, 2017 Share Posted March 5, 2017 Just tried the Viggen myself, Aircraft and gear are fine, Startup is fine..Try to arm Viggen on ground, No Cigar... Havent tried ramp start with weapons already loaded yet, But asking ground crew to load weapons only gets me a fuel tank.. I was able to arm fine with ARAK, XT and Rb24J. System specs: Gigabyte Aorus Master, i7 9700K@std, GTX 1080TI OC, 32 GB 3000 MHz RAM, NVMe M.2 SSD, Oculus Quest VR (2x1600x1440) Warthog HOTAS w/150mm extension, Slaw pedals, Gametrix Jetseat, TrackIR for monitor use Link to comment Share on other sites More sharing options...
Justificus Posted March 5, 2017 Share Posted March 5, 2017 Just tried the Viggen myself, Aircraft and gear are fine, Startup is fine..Try to arm Viggen on ground, No Cigar... Havent tried ramp start with weapons already loaded yet, But asking ground crew to load weapons only gets me a fuel tank.. Well, I'm one of the lucky ones it appears, as I have no issues with the Viggen at all. Cold start is fine, and I'm also able to rearm without issues. Same is true for all the other modules out there that I have. Sorry to see so many others having problems with this update... I've been there and it sucks! Justificus System Specs:i7 4970K @ 4.8, GTX 1080 SC, 32GB G.Skill DDR 2133,Thermaltake Level 10 Full Tower Case, Noctua NH-D15 6 Cooler, Win 10 Pro, Warthog, CH Pro Pedals, CH Throttle Quadrant, Oculus, 1 32" & 2 19" Monitors Modules Owned: A-10C I+II, Ka-50, FC3, F-86, Mig-15, Mig21, UH-1H, Mi-8, CA, P-51D, BF-109K-4, FW-190 D-9, Hawk, NTTR, M-2000C, SA342, F-5E, Spit Mk. IX, AJS-37, Normandy, WWII A.P., AV-8B, F/A-18C, L-39, Persian Gulf, Mig-19P, I-16, Super Carrier, F-16, Channel, Syria Link to comment Share on other sites More sharing options...
mastercosta Posted March 8, 2017 Share Posted March 8, 2017 at least with this latest update 2.0.5 - a least the same problem AJS-37 crash start from ramp, no radar, and 0% fuel problem as in the spitfire... not try the other modules i only download repair Visual C update 64bits... should i try a a fresh install 64bits and 32bits spitfire i was working perfect in 2.0.4. intel six core-i7-3930k - gtx1080 -16RAM ddr3 -2133 - intel SSD - windows 10 OZOMASTER A10C||F-14C||F-16C||F/A-18C||AV-8B||ASJ37||M-2000C||MIG15||MIG19||MIG21||F5-E||F86||FC3||P51D||Fw190||Fw190 A8||Bf109 D9||Spitfire||UH-1H||Mi8||GAZELLE||BShark2||CA||YAK52||CEagle2||L39||C101||i16||Supercarrier|| ---------------------------------------------------------------------------------------------- WINDOWS10 HOME ||asus GTX 1080|| 3440x1440 34' ||sixcore i7-3930k 3.2GHz || asus sabertooth x79 || 32GbRAM 2133Mhz || TM warthog || saitek cessna pedals || trackIR 5 Link to comment Share on other sites More sharing options...
fjacobsen Posted March 8, 2017 Share Posted March 8, 2017 at least with this latest update 2.0.5 - a least the same problem AJS-37 crash start from ramp, no radar, and 0% fuel problem as in the spitfire... not try the other modules i only download repair Visual C update 64bits... should i try a a fresh install 64bits and 32bits spitfire i was working perfect in 2.0.4. intel six core-i7-3930k - gtx1080 -16RAM ddr3 -2133 - intel SSD - windows 10 Seems to be a Starforce problem, so we have to wait on the developers to fix it. i7-10700K 3.8-5.1Ghz, 32GB RAM, RTX 4070 12GB, 1 x 1 TB SSD, 2 x 2TB SSD2 TB, 1 x 2 TBHDD 7200 RPM, Win10 Home 64bit, Meta Quest 3. Link to comment Share on other sites More sharing options...
Spuds Posted March 9, 2017 Share Posted March 9, 2017 Same here, I ran repair When I enter the cockpit I see sparks in front of nose, then in outside few I noticed nose landing gear is in the middle of extending to gear down. Also, when in outside view I hear the engine running however, inside the cockpit the engine is shutdown. Rampage V Edition 10 I7 6850K (No overclock) Corsair Dominator Platinum 32 GB EVGA FTW 1080 (Single card) Windows 10 Pro TM HOTAS WARTHOG Saitek Combat Pro rudder pedals ASUS Swift PG348 monitor (G-SYNC off) Link to comment Share on other sites More sharing options...
Recommended Posts