Maniaplanet Forum

Hello,

I discovered a little bug in the MediaTracker while testing other stuff. You'll see it the best if you compare two situations. Go to the in-game MT and put a trigger let's say one block after the start (screen). Add a camera race let's say internal and set the ending value to 0:00.00 (screen). Then validate the map. As expected, nothing happens. Now edit the in-game MT by importing a ghost to the clip with the camera race (screen). Then validate the map. What's this flash?

If anything isn't clear enough then write it and I'll try to explain.

It's a little bug but I think Nadeo should know about it.

EDIT: Added screenshots, you'll see what I mean when you try it.

EDIT2: I've prepared the examples for you (open in the editor, validate (during the race you'll see the bug), then look at the in-game MT):

• Without a bug
• With a bug

Screenshots would help what do you mean by flash?

EDIT: Ty for screens and maps Confirmed...

I haven't downloaded the maps bt I think he means that the camera is changing for about one frame and then changing back. This could be caused by the game engine that has to do two things instead of one. It is simply not fast enough to change the camera, place the ghost and change the camera again in 1/100 of a second.

I don't really understand why you would want to make a 0 sec. cameraclip?

Tobias1595 wrote:he means that the camera is changing for about one frame and then changing back

Indeed, that's exactly what I mean.

zarexz wrote:I don't really understand why you would want to make a 0 sec. cameraclip?

Because this is necessary to do one cool trick. This trick lets a player choose and change a camera on a ghost (gps). And with that one frame change it doesn't look good. In addition, it works well in Stadium (test map: http://webshare.cz/lx70778SvV-Test.Map.Gbx, wait at the start for the ghost).

Ok I just spent ages testing this and trying to find solution.
I can't find out why this is happening but I did find a fix.
Add a timespeed track in mediatracker leaving the start and end key speed set at default settings which is 1.

Thank you for the workaround . Nevertheless, it still is a bug which should be fixed.