eAi

How about looking at the documentation for the function that it's very clearly telling you you're using incorrectly?

It may be harder, but I see no reason why you couldn't save this as a map file with a script. Map files can contain anything.

Can it save to .map files?

That is not what the Field of View is. The FOV is the angle you can see on your screen. Typically racing games widen the angle the faster you're going as this accentuates the feeling of speed. Games tend to have between 45 and 90 degree FOVs. Having a smoothed chase camera with a distance that is based on your speed is something else entirely (though often used in conjunction with FOV changes, vignetting, motion blur and other post-processing effects.) MTA tries to generally provide the smallest building-blocks possible and let you build what you want in scripts, rather than trying to do things for you that your script could do itself. There are exceptions of course, but that's the direction we're generally moving.

I would have thought a screenshot limiter would be a better choice. I'm not sure what the state of the screenshot code is, but we may be able to multithread it to improve performance.

Just download it from the lua website! Compiling the code will protect it from casual viewers, but not hackers etc. It will very slightly speed up the loading of the resource, but have no impact on it's performance while it's running.

Beyond what Towncivilian is suggesting, I'm not sure we can do much to help, without being able to reproduce it on our own computers. If we could, we'd profile MTA and see what's happening, but this is probably hard for you to do yourself (unless you're willing to get down-and-dirty with the code!)

What would onPlayerScreenShot be useful for? fileRename: Useful yes, though the workaround isn't that hard. I can't think of any reason setCameraTarget wouldn't work on peds. Looking at the code on Google Code it looks like it'd be a one line change to fix this. Report it on http://bugs.mtasa.com, or better still, write a patch for it! The onPlayerChat one sounds like a bug. Looking at the code on Google Code, I can't see an obvious reason for that though. I suggest reporting this as a bug on http://bugs.mtasa.com.

The MTA frame rate limited is not very accurate in 1.0.4 - test how well it runs on a local server on your computer. It's much better on 1.1.

Bear in mind that there have been a few 1.0.4 releases since it's initial release.

Severs can limit your FPS, does it happen even on a local server?

No?

You shouldn't be using isPlayerInACLGroup. See the yellow box on https://wiki.multitheftauto.com/wiki/IsObjectInACLGroup

They're called Integers...

ASI files are just DLLs renamed. We're not going to support DLLs, as there are obvious virus risks.

Well, if you, or anyone else can find out what it actually does, then we could integrate it into MTA. I'm not sure what problem it's actually fixing though. You may be able to contact the author and ask him...

Your link doesn't work. But, no, it's not something we'll ever support. We want your game to be as pristine as possible, and allowing mods just opens things to cheats. I can't tell what your link is, but if it fixes a GTA bug, it's something we can integrate into MTA.

Using a timer like that is really bad for two reasons: - setTimer doesn't guarantee that it'll fire after exactly 1000ms. It says that it'll fire after 1000ms, but it could be 1030ms or so, depending how fast your server is running. As a consequence, you're going to overestimate your uptime fairly significantly, adding roughly 12 minutes per day if your server runs at 60fps. - It's also very wasteful triggering a function every second, and completely unnecessary. As MCvarial says, you should use getTickCount(). Record the value of it when you start the server then just subtract that from the current value when you want to show it.

What are you trying to achieve?

You need to put your addEventHandler calls after the functions, rather than before them, as it doesn't know they exist.

Well, you're welcome to give it a go: https://nightly.multitheftauto.com/ Don't trust the roadmap too much - things on there may not get done, and things that aren't on there will get done.

Performance is obviously important. "Similar to using Chromium" means nothing - game UIs have a different set of requirements to web pages - you rarely care that much about the framerate of webpages, and you're quite used to pages taking a second or so to load, but with a game, that's not acceptable. Not that CEGUI does much better... I also don't necessarily think making UIs with HTML is easy. Certain things are really hard that would be quite easy with a traditional UI like CEGUI. Often it's what you know that counts.

TheKid: What? How would you propose we deal with different aspect ratios? Just stretch them? Look at the user interface of Windows on your computer - how does that work if you change resolution?

Indeed

How about not repeating the same bad code over and over again? Get one marker working, then the others. But basically, read the wiki, your code makes no sense at all. "if(marker1 == 0) then" means nothing - an element is never going to be 0. Why do you expect 'open door' to work?