Torso Posted March 3, 2017 Posted March 3, 2017 MIG-21 shows up as 1.5.1. In 2.0 my Mig-21 is showing as 2.0.5, every module except Vig is showing as 2.0.5, some with beta, some not. But all 2.0.5 :huh:
Mud Posted March 3, 2017 Posted March 3, 2017 Oh, I see. Perhaps due to the fact that I don't own the MIG-21 then. Spoiler W10-x64 | B650E Gigabyte Aorus Master | AMD Ryzen 7 7800X3D | Noctua NH-D15 G.Skill Trident ZS Neo DDR5-6000 64Gb | MSI RTX 3080ti Gaming X Asus Xonar AE | VPforce Rhino + TM Hotas Warthog MFG Crosswind pedals | Valve Index
Supersonic Posted March 3, 2017 Posted March 3, 2017 Fellow Pilots, Do you have VC14 runtime installed as per update 1 change log ??? MoBo Asus TUF X570-Plus (Wi-Fi) / CPU AMD Ryzen 9 5900X / GPU Asus TUF RTX3080 / RAM 32GB Corsair Vengeance RGB Pro DDR4 @ 3600MHz / V-NAND SSD 1TB Samsung 970 EVO NVMe M.2 / PSU Corsair RM750 / CPU Cooler Corsair H100i Platinum / OS Win 10
Mud Posted March 3, 2017 Posted March 3, 2017 Hey Supersonic, Yeah, it was pointed out on page 2 of this thread by Eight Ball. Despite my current install being pretty new, I'm going to do a clean install and see if that solves it. Mud Spoiler W10-x64 | B650E Gigabyte Aorus Master | AMD Ryzen 7 7800X3D | Noctua NH-D15 G.Skill Trident ZS Neo DDR5-6000 64Gb | MSI RTX 3080ti Gaming X Asus Xonar AE | VPforce Rhino + TM Hotas Warthog MFG Crosswind pedals | Valve Index
Supersonic Posted March 3, 2017 Posted March 3, 2017 Hey Mud, Oops my bad, just about to load up my rig and update. Only other thing is to delete all the save game file stuff and let DCS World rebuild, don't forget to save your config file. MoBo Asus TUF X570-Plus (Wi-Fi) / CPU AMD Ryzen 9 5900X / GPU Asus TUF RTX3080 / RAM 32GB Corsair Vengeance RGB Pro DDR4 @ 3600MHz / V-NAND SSD 1TB Samsung 970 EVO NVMe M.2 / PSU Corsair RM750 / CPU Cooler Corsair H100i Platinum / OS Win 10
joey45 Posted March 3, 2017 Posted March 3, 2017 doing the saved game delete/rename still does it to the Viggen. The only way to make sense out of change is to plunge into it, move with it, and join the dance. "Me, the 13th Duke of Wybourne, here on the ED forums at 3 'o' clock in the morning, with my reputation. Are they mad.." https://ko-fi.com/joey45
ac5 Posted March 3, 2017 Posted March 3, 2017 So, the Viggen in 2.0 is very broken. It spawns on the ground with gear up then puts it down when it has damaged itself. It cant get more then 25% fuel even when I put it at 100% in the editor. I cannot for the life of me turn on the radar. In airstarts the plane is shutdown. Is this just on my end? Same problem here, though the fuel is set to 100% in the editor and in game is then 0% (Mission and screenshots included). Engine stops of course. NO WAY to turn on the radar. Happens regardless if in the air, starting on runway, ramp or parking lot, and regardless if starting from the mission editor or quick mission. The Viggen is impossible to use in DCS 2.0.5.2576 Update 1.:cry: Leatherneck please advise.Viggen Test.zip Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
ac5 Posted March 3, 2017 Posted March 3, 2017 Addendum: No mods installed Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
razo+r Posted March 3, 2017 Posted March 3, 2017 Same problem here, though the fuel is set to 100% in the editor and in game is then 0% (Mission and screenshots included). Engine stops of course. NO WAY to turn on the radar. Happens regardless if in the air, starting on runway, ramp or parking lot, and regardless if starting from the mission editor or quick mission. The Viggen is impossible to use in DCS 2.0.5.2576 Update 1.:cry: Leatherneck please advise. I put myself on the Runway with the Viggen, 100% fuel and had no problems, all my fuel was there and everything worked and no problems with the gear occured
ac5 Posted March 3, 2017 Posted March 3, 2017 I put myself on the Runway with the Viggen, 100% fuel and had no problems, all my fuel was there and everything worked and no problems with the gear occured With an external tank it works, provided you start in the air, though only 20% fuel is available, in the mission editor internal fuel is set to 100%. In the ground, with an external tank, it crashes down, goes up again, but damaged and the engine goes off, fuel, in spite of the external tank = 0% Happens regardless if starting on runway, ramp or parking lot, and regardless if starting from the mission editor or quick mission.:cry: Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
razo+r Posted March 3, 2017 Posted March 3, 2017 I had a clean loadout, nothing attached, not even a tank And i did not experience any jumping
Mud Posted March 3, 2017 Posted March 3, 2017 It's not really jumping. It spawns in a gear up state, so falls down a bit and then automatically lowers the landing gear, lifting the Viggen up to it's normal state ... albeit damaged. Spoiler W10-x64 | B650E Gigabyte Aorus Master | AMD Ryzen 7 7800X3D | Noctua NH-D15 G.Skill Trident ZS Neo DDR5-6000 64Gb | MSI RTX 3080ti Gaming X Asus Xonar AE | VPforce Rhino + TM Hotas Warthog MFG Crosswind pedals | Valve Index
Supersonic Posted March 3, 2017 Posted March 3, 2017 Just finished updating and despite installing latest C++ DCS World would not start, some C++ dll missing rubbish error ?? Anyway I reinstalled a fresh copy from Microsoft and DCS World fired up no problem and now have the Viggen sitting on the ramp at Nellis all loaded with arms and Jet A1 ready to start. I'd already installed the latest runtime before the update BUT for some strange reason DCS would not start until the C++ runtime was reinstalled. MoBo Asus TUF X570-Plus (Wi-Fi) / CPU AMD Ryzen 9 5900X / GPU Asus TUF RTX3080 / RAM 32GB Corsair Vengeance RGB Pro DDR4 @ 3600MHz / V-NAND SSD 1TB Samsung 970 EVO NVMe M.2 / PSU Corsair RM750 / CPU Cooler Corsair H100i Platinum / OS Win 10
pj Posted March 3, 2017 Posted March 3, 2017 I have the same problems when spawning (landing gear and 0 fuel), but I was able to get through the start procedure. I also noticed that I cannot adjust the main altimeter, but the standby altimeter works ok. Also, after starting the plane I get nothing on the radar. If I start a quick mission in the air I can adjust the altimeter but have the 0 fuel and full up-trim problems. Win 10, Gigabyte Aorus Ultra with i5 9600KF @ 4.6GHz, 32G DDR4 3200 RAM, GTX 1070, TrackIR 5, TM Warthog stick on VPC Warbird base, Warthog Throttle for jets & helis, CH Throttle Quadrant for props, CH Pro Pedals, 500GB SSDs for installed sims :gun_smilie:
Crowman Posted March 4, 2017 Posted March 4, 2017 Hi All Having same problems as mentioned by yourselves also noticed that Hud doesnt seem to be working either. I am able to refuel on ground to 100% then aircraft can be flown ok. Also noticed when spawning cold cockpit is powered even though battery switched off. Chilliblast, ASUS P8-Z77-V Pro, I7 3770K@3-5GHz, 16GB Corsair PC-3 12800 DDR3 @1600MHz, MSi GTX 1080 8GB, Creative SBZ, Logitech LT Z906 5.1, ASUS 24"Monitor 1080 60Hz,120GB SSD, 1TB SSD, 2TB HDD, 4TB HDD, Corsair CX 750W PSu, Win 10 Home Prem 64bit, TM Warthog, TM T Flight Pedals. Track IR, Occulus Rift S, Black Shark SA, DCS A-10C SA, All DCS Current Aircraft Modules, DCS 2.5 Stable and Beta.
wolle Posted March 4, 2017 Posted March 4, 2017 https://gfycat.com/VengefulAstonishingGibbon gif of spawning I'm having the exact same problems:cry: [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
Mayo2017 Posted March 4, 2017 Posted March 4, 2017 Chiming in with the same troubles. Drop on start with damage and gear extension following, unable to rearm/refuel, all of it. Wiped all configs such, removed all mods, ran a repair, installed VC++ as required, no luck. [sIGPIC][/sIGPIC]
Caput_58 Posted March 4, 2017 Posted March 4, 2017 Same here. Happens in single player and multiplayer. Happens when plane is set for "client" or "player". Happens on cold ramp starts and hot runway starts. One thing I notice, in a paused multiplayer session, when you first spawn in, the gears are down. As soon as you hit "unpause" they instantly disappear, only to slowly deploy again after you've fallen. I also tried 3 random online servers. Same problem. Don't know if that means it's client side or not. Would love to know what happens when a person who isn't having problems hosts a session and others join. Any chance that the hydraulic pressure is momentarily getting zero'd, like the fuel, and that makes the gear collapse?
whartsell Posted March 4, 2017 Posted March 4, 2017 Gear doesnt need hydraulic pressure once they are down and locked Arduino,EOS and Helios Tutorial Static ATC menu mod
Crowman Posted March 4, 2017 Posted March 4, 2017 Hi All Quick update on my previous post, I incorrectly posted that the HUD was inop, I was wrong this was due to me not following correct startup procedure. I am currently flying the default quick mission for the NTTR ie the cold-start. I refueled on the deck to full tanks (Invulnerable by the way) I followed the checklist, and so far have managed to taxi out and takeoff without a problem, currently flying around, I have noticed in flight so far, 1:The radar appears totally inop, 2: The aircraft is consuming fuel even though in options its set to Infinite fuel or what ever it is. Apart from that so far so good will update as and when find things. Chilliblast, ASUS P8-Z77-V Pro, I7 3770K@3-5GHz, 16GB Corsair PC-3 12800 DDR3 @1600MHz, MSi GTX 1080 8GB, Creative SBZ, Logitech LT Z906 5.1, ASUS 24"Monitor 1080 60Hz,120GB SSD, 1TB SSD, 2TB HDD, 4TB HDD, Corsair CX 750W PSu, Win 10 Home Prem 64bit, TM Warthog, TM T Flight Pedals. Track IR, Occulus Rift S, Black Shark SA, DCS A-10C SA, All DCS Current Aircraft Modules, DCS 2.5 Stable and Beta.
Crowman Posted March 4, 2017 Posted March 4, 2017 Hi Again Quick addition just noticed missing texture error displayed on Kneeboard, waypoints mission cards etc appear ok airfields displayed, think its the map backgrounds. Chilliblast, ASUS P8-Z77-V Pro, I7 3770K@3-5GHz, 16GB Corsair PC-3 12800 DDR3 @1600MHz, MSi GTX 1080 8GB, Creative SBZ, Logitech LT Z906 5.1, ASUS 24"Monitor 1080 60Hz,120GB SSD, 1TB SSD, 2TB HDD, 4TB HDD, Corsair CX 750W PSu, Win 10 Home Prem 64bit, TM Warthog, TM T Flight Pedals. Track IR, Occulus Rift S, Black Shark SA, DCS A-10C SA, All DCS Current Aircraft Modules, DCS 2.5 Stable and Beta.
RagnarDa Posted March 4, 2017 Posted March 4, 2017 Good news! I am able to replicate the problem on my end. Bad news: don't know yet how to fix. DCS AJS37 HACKERMAN There will always be bugs. If everything is a priority nothing is.
Flagrum Posted March 4, 2017 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. 1
Goblin Posted March 4, 2017 Posted March 4, 2017 Good news! I am able to replicate the problem on my end. Bad news: don't know yet how to fix. Software development in a nutshell..! ;) You'll find a fix.
grunf Posted March 4, 2017 Posted March 4, 2017 Good news! I am able to replicate the problem on my end. Bad news: don't know yet how to fix. I wonder if the starforce is causing this issue. Somewhat similar bug was plaguing the Hawk some time ago, and it turned out it was starforce's fault. And there was an announcement a few days ago on the forum that the starforce is updating or something like that.
Recommended Posts