Hey tater!!

[swdw]

Your PM box is full and I had the following question for you:
----------------------------------------------------------
Hi tater,

Don't know why I didn't think of asking you earlier.

There was a problem with the torpedo attack mission Beery put in RFB caused by the 1.4 patch. As soon as the cruiser hits one of the waypoints, you cannot keep the scope locked on the target in either manual or auto targeting. This was not a problem in 1.3

The problem persists until it looks like it reaches another waypoint.

Because of this, I had to pull the mission. Would you be able to take a look at it and see if you can fix it? If you don't have the time, could you recommend someone that could take a look at it?

I know nothing about the mission editor and don't have the timne right now to learn it.

Thanks,

Sam

[tater]

Wow, that is really odd. There are no waypoint parameters I can think of that would cause this.

I did a lot of testing on making the scope lock on things other than ships to try and make the photo recon missions I wanted and saw this. but it was not waypoint limited, it was that certain things cannot be locked.

Bizarre.

Is this the same mission that's been in RFB for a while?

[tater]

I see nothing at all that might cause this in the mission.

[tater]

I assume the tug is there to make it look like a towed target. In my experience the only thing that controls being locked is the unit type. That happens upon the mission load, so I'm just not seeing what might happen.

[swdw]

bummer, I liked the way he had the mission set up. Wonder what they changed in 1.4 that messed with the mission. It worked fine under 1.3

Guess we'll keep the stock one until someone can write a new one for it.

[tater]

All I did was look at the file in the editor. If it works in stock, then the problem is clearly some really odd RFB conflict.

It would be interesting to figure out since I'd dearly like to know what controls "lock" for the scope.