RzTen1

Except this has been placed in the main forum, and not the bug reporting subforum... unless bug reports are supposed to go here?

Hey MODs, this was in the bug report forum for 1.5 and it got moved here with no note as to WHY. This doesn't occur in 1.2... I'm guessing that means it's been reported, but some kind of feedback would be nice.

Mine takes about 10 seconds from when the update window disappears to the 'DCS World' start-up screen. I've got 15 modules loaded. It doesn't look like there's a ton of disk activity on startup, but the thread seems to hold at 100% on one CPU the whole time. Perhaps it's CPU bound?

I think the Ka-50's LWR may be broken unless every Russian armored vehicle never uses their laser... I created a quick test mission with every Russian armored item in the editor (attached) and flew though the grouping a couple of times. I never get a LWR warning. The few times I managed to make it though without exploding I ran the self test mode on the LWR and although the audio announcement doesn't always play for me the warning lights do come on. I think the announcement not playing may be due to damage as it does play on a fresh helicopter. I'm running 1.5.0.46175. This issue was mentioned in http://forums.eagle.ru/showthread.php?t=151260, but that's been moved so I'm resubmitting this. If this isn't actually a bug and none of the Russian vehicles laze please disregard. test2.miz

I think it may be broken unless every Russian armored vehicle never uses their laser... I created a quick test mission with every Russian armored item in the editor (attached) and flew though the grouping a couple of times. I never get a LWR warning. The few times I managed to make it though without exploding I ran the self test mode on the LWR and although the announcement isn't playing for me the warning lights do come on. test.miz

You're correct, I was mistaken. It doesn't have a badge icon at the bottom of the screen and doesn't show up in the instant action missions, but I can fly it though the mission editor. That is a little confusing as all the other modules don't work that way. I suppose the badge and quick launch options will come later.

I just got a newsletter saying it should be out today... 'The Fighter Collection and Eagle Dynamics are pleased to announce that Su-27 for DCS World is now available for download via ingame Model Manager and as separate module' I'm not showing it in the manager either although I do see Flaming Cliffs 3. Is there an additional delay or was the newsletter premature?

I've been playing a bit with my FF2 and I do get some stick shake. Force feedback does seem to cut out after a crash and respawn though. I have to exit out of the mission completely to get it to come back.

AMD Radeon 7970

I think the main issue is once you've done it incorrectly with navigators weapon panel set to I instead of II you have to restart the entire mission. Once you've done it wrong it's broken forever. Anyway, I've done it correctly in this video if anyone is interested: I still turn on ESBR heat even though I don't need to though. I think I've just gotten used to turning everything on. :D

Actually, I think I've figured it out. If the pylon selection knob in on I when you hit B, the drop knob breaks and is no longer usable. If I set it to II immediately when I start the mission, everything seems to work fine. It looks like hitting 'B' even with everything disarmed still breaks the knob.

I've posted a video of what I'm doing here: I've tried the pylon selection knob on both I and II but the drop knob always sticks.

The right weapons are loaded at mission start (verified with the external view), but just to be safe I tried reloading them anyway. No change, the knob still sticks and I can't drop anything.

I'm playing the campaign missions in 1.2.8 and I'm up to number 18 where I need to drop the SAB-100 flares at night and I can't get them to drop no matter what I do. I can force all of them to release but only from the pilots emergency switch, the co-pilot's emergency release won't drop them. I've set the weapon system breakers to on, the master arm to armed, set the pod select knob to 1, armed the bombs (both switches up) on the co-pilots panel, set the bomb drop knob to I and turned the enable switch to on. If I press 'B' to drop one nothing happens and the bomb knob get's stuck. No matter what anything else is set to, the knob will no longer turn. I've tried opening and re-saving the mission in the hope that would fix it, but no dice. Is this a problem with 1.2.8 or did I miss a step?

Normally F1 should jump you back into your currently controller vehicle. You might try running the DCS repair tool, and making sure the serial numbers are showing up in the Module Manager. It's acting like you haven't bought the modules, even though they're installed. You normally jump to the map directly when you've either joined a new multiplayer map and haven't selected a vehicle, or when you've made a map with nothing controllable, or you've made a map with something you can't actually use (ie: an A-10C without the A-10C serial). If you've got anti-virus or extra firewall programs installed you might try shutting those off too and see if anything different happens. You may also try removing the standalone A-10C version... I've never tried having it installed at the same time as DCS World, but it's conceivable there could be a conflict. Does the Su-25 work? Also, did you ever get the DRM 'enter serial' dialog? I usually get it the first time I launch a new module that I've never entered the serial number for. It's possible it opened 'under' the DCS window... try alt-tabbing around once the game is running.