[Agent_Koopa]

I downloaded Inferno, and I'm getting into it, when I get to the mission with the Independence battling the Diablo and I have a problem. When the Independence is hit by the Diablo and its beams taken out, the Diablo never fires a shot, and neither does the Independence after that. I investigate, and lo! The Diablo doesn't have a beam turret. For that matter, it doesn't have any turrets! This makes it impossible to take out the forward beam turret, and the SOC ship never jumps in, making it extremely difficult, if not impossible, to take out the Diablo! Oddly enough, on a previous playthrough, the front turret was permanently glowing.

Great campaign though, even if the ships aren't as high-poly as could be hoped for, and I feel that this is what a space sim should be like. You should be in a fast, maneuverable ship, with plenty of targets to shoot at. Feels like the Star Wars movies! 

[Dark Hunter]

Someone else had this exact problem just a few days ago...

Goober5000 suggests restarting the campaign using the most recent build of the SCP (which would 3.6.9). Says it's caused by something going wrong in the mission just before that one.

I never heard whether or not this will work, so: good luck! If it doesn't work, tell us.

[Agent_Koopa]

I am using 3.6.9 Final. Would doing the previous mission suffice, or do I have to restart the campaign?

[Snail]

Goober said it was caused by the previous mission so i guess replaying may help.

[snake60]

i have the exact same problem, i was just going to post it.

Just redoing the previous mission (in the tech-room i guess ???) should do the trick ?

I'll give it a try this evening

[Snail]

NOT in the Tech Room. Press Replay Previous Mission at the red alert screen.

[snake60]

Thanks, i did not remember it was two "connected" mission, silly me !  :

edit : i've tried to redo the previous mission two times, with the same result. Even worse, now when i click on the commit button at the red alert screen, i'have a freespace program error "freespace encountered an error and must close"    Do you want me to try with the debug build ?

[Snail]

What the hell is going on? This is fudged up.

This is strange. I wonder... What happens to the Kismat? Any problems with that one?

[Mobius]

I can't believe I have to restart the campaign...

I don't see the Kismat at all.

[Snail]

?

The Kismat is not there?

[Mobius]

No. I see the Independence. I can target incoming Nahemas and Serpents. I can't move at all.

[Dysko]

Strange... I have none of these problems.
I can move, I can see the Kismat, and I can target the Diablo's turrets.

[Mobius]

I have started the campaign with RC8. I wanted to play it once again and see if our Steadfast is better.
Uhm...

[Dysko]

I have started the campaign with RC8.

Try installing the official 3.6.9

[Mobius]

I have installed it. The problem is that I started the campaign with RC8 and now I must restart it.

Uhm, restart...


Back where he started is prophetic!

[Agent_Koopa]

Well, replaying the blockade worked for me.

[Mobius]

But I lose the achieved kills. It's important for me, I want to reach 100,000.

[Goober5000]

I have installed it. The problem is that I started the campaign with RC8 and now I must restart it.

Uhm, restart...


Back where he started is prophetic!

"There is the theory of the mobius. A twist in the fabric of space where time becomes a loop, from which there is no escape." -- Lt. Worf, ST:TNG, "Time Squared"

Anyway, did replaying the campaign fix it?

[Mobius]

No. I failed it five times.


There's another theory about Mobius-Stonehenge,made by megaliths,is a superweapon instended to destroy asteroids. Mobius is a place on the darkside of the moon.

[haloboy100]

i had a similar problem. the diablo was completly disabled and disarmed with no subsystems oporational. and even worse it was facing the wrong way. i replayed the mission before countless times and that diden't help. guess i'll restart too..