[colecampbell666]

I get weird FRED/Engine related problems when playing the first mission. First of all, the Nials are nigh impossible to kill, way harder than they were in 3.4. The Yorktown never jumps out, it just sits there forever after the Minbari cruiser leaves.

These problems were not present in the original 3.4.

[IPAndrews]

The Nials are nigh impossible to kill

Bring up the options. Find the one marked "difficulty". Change to easy.

[rbxplayer]

There is also other issues:

1. Alpha 2's voice reading the script and then answering 'Yes, sir' to team commands you give out is a different voice

2. In the last mission. There is a part where first Alpha 3 states that basically we are all gonna die, but then just after that, Alpha 3 tells the team to suit up. Plus, it is in a different voice.


Overall it is a well balanced demo if played on medium. Great models and voice acting

[colecampbell666]

The Nials are nigh impossible to kill

Bring up the options. Find the one marked "difficulty". Change to easy.

Even on easy. It's a lot harder than it was in 3.4.

[IPAndrews]

Difficulty changed a little from 3.3 to 3.4 but not from 3.4 to 3.4a or 3.4b. So it's your imagination. Difficulty is a choice of the mission designer. There are AI profiles to cover easily defeated rookie pilots to aces. The mission designer chooses what to assign.

[colecampbell666]

I get weird FRED/Engine related problems when playing the first mission. The Yorktown never jumps out, it just sits there forever after the Minbari cruiser leaves.

These problems were not present in the original 3.4.

[darkmaster]

I also notice that the "match speed" function is sometimes automatically disabled for unknown reason, and this kind of thing didn't happen in 3.4a.

For example, I targeted a hostile, then pressed M, but 5 seconds later the function was automatically disabled, decrease my speed to 0. I don't know what the hell was going on. Also , sometimes, I can only "match speed" an hostile, but not an ally.

The same thing happened with the alt-M "automatic speed matching" function, like a ghost secretly presses the M button again.

This problem happens in occasion, the first time I met it was while replaying "E-M war" in the latest version of TBP.



 

[IPAndrews]

I've never seen this speed match cancellation bug. Anyone else seen it? It's minor anyway. Put it in MANTIS in the SCP forum and it'll be fixed for the 3.6.10 version of the game engine.

[darkmaster]

I just reported it but it's not a matter with me since I barely use the match speed function.

BTW, what is MANTIS ? what is SCP ? And why must I post it there ? 

[Vidmaster]

The same thing happened with the alt-M "automatic speed matching" function, like a ghost secretly presses the M button again.

sorry to tell you but there is probably a much more resonable explanation (because what you describe never happend before or was reported on any FS stuff before).

You M key is broken 

Remember playing on my old PC, there it was the E key. Sometimes, it did not react, sometimes it got stuck (not the key itself but the sensor) and sometimes I had these ghost button presses.

[CaptJosh]

One other thing. If you blow up the enemy target, there's nothing to match speed with, so you're going to stop. If you want to always match speed, you need to use Alt+M.

[IPAndrews]

Of course! CaptJosh wins the Golden reset button (tech support award) for today.

[colecampbell666]

I get weird FRED/Engine related problems when playing the first mission. The Yorktown never jumps out, it just sits there forever after the Minbari cruiser leaves.

These problems were not present in the original 3.4.

[CaptJosh]

That's because it won't jump out until you do. You have to be next to it, and everyone jumps out when you do.

[colecampbell666]

I jump out, and I get traitor'd. Or do I have to be real close?

[CaptJosh]

Well, there should be a directive about approaching the ship that should fulful when you close to...um...hang on...I need to play this one again.

EDIT: Well, I was pretty much on top of the ship and it worked. I was using the March 3rd XT build. It all went flawlessly. But you have to have the "Jump Engines Online" objective highlighted. This should happen pretty much as the Dublin gets wasted by that Sharlin.

[darkmaster]

One other thing. If you blow up the enemy target, there's nothing to match speed with, so you're going to stop. If you want to always match speed, you need to use Alt+M.

Sorry I didn't have much time to reply to this subject, that 's the cause of this late response. I know how the M and alt-M function! I 'm sure that the enemy was not destroyed, the function was just disabled and I also heard the disabling sound  . And it did happen to Alt-M , too.

My M key is not broken, either. I have tested it in MS Word and it worked properly.

This problem didn't happen all the time, but when it occurs it will rest there and the only way to get rid of it is to restart the computer (quiting TBP didn't solve the prob)

This is just to make clear about the issue, please don't consider it a complain. It doesn't bother me 'cause I rarely use the M key, I just want to provide correct information.
 

[IPAndrews]

If you are convinced you've found a real bug go to the Source Code Project forum on this site and use their Mantis bug reporting system to log the bug. Someone will then look at it. Personally I think the time might be better spent buying a new keyboard or getting a priest to exorcize your PC.

[Jeff Vader]

Indeed. If the problem doesn't go away with quitting and restarting the game, it is most surely not caused by the game engine, hmm.

[IPAndrews]

If there's a bug in the game engine the bug will be there whether he restarts, reboots, goes to bed, gets up again, dances a jig... The real question is if there's a bug in the game engine how come nobody else has seen it.