• Content Count

  • Joined

  • Last visited

  • Days Won


Dutchman101 last won the day on June 13

Dutchman101 had the most liked content!

Community Reputation

456 Superstar

About Dutchman101

  • Rank
    Global Moderator & Anti-Cheat Team member

Recent Profile Visitors

13,790 profile views
  1. I don't think it was a joke, we saw multiple players using an "aimbot" application which turned out to be fake, and actually a njRAT created by you. So it looks like you advertised something as cheat, persuading some players to download it and infect themselves with a virus. Please don't lie. Illegal activities like this on MTA are always rewarded with a ban. You can call yourself lucky, unban will be in 2 months.
  2. The procedure is that banned players can only ask/appeal for themselves. So please point here and let them make their own topic.
  3. Dutchman101

    MTA Crash

    If it keeps happening to a number of players after they updated, then tell them to put a file called debug.txt into MTA installation folder root (next to Multi Theft Auto.exe) and to hold & release CTRL R + CTRL L simultaneously when it freezes again. That will force MTA to crash, it's a feature designed to investigate freezes. After that, please provide us the crash dumps from MTA San Andreas 1.5\MTA\dumps\private, we can use them to find the cause of a freeze.
  4. Dutchman101

    MTA Crash

    First make sure that your affected players are using the latest MTA version, because some issues were fixed recently. Tell them to re-download MTA from http://multitheftauto.com/ to get the update Also, your own MTADiag log doesn't include any of these crashes. If they next report a crash to you, then first check their version (if it's atleast r18664, from homepage) and if it is, then collect MTADiag log of your players to forward. Note: you can also make sure they are updated by setting <minclientversion> in mtaserver.conf to 1.5.6-9.18664.0 or executing this with runcode: srun setServerConfigSetting("minclientversion", "1.5.6-9.18664.0", true)
  5. You could ask the server owner to whitelist timecyc.dat modifications, or apply their own contrast/brightness to vehicles through scripting or shaders. It's pretty hard to implement exceptions in a sense that MTA would scan which part of timecyc.dat (parameters) are modified, and even harder for us to neutrally judge if certain 'safe' modifications can be whitelisted, because any change can affect balance in different gamemodes in different ways. So it can never be a "safe for all" verdict. This is why we'd rather leave it up for servers to decide on.. sorry.
  6. Dutchman101

    marker bug

    We cannot help you efficiently unless you provide full code @drhx
  7. Dutchman101

    unban req

    I apologize for the delay, but I can tell you that you're banned for cheat development. Send me a PM to hear about the possibilities. Appeal denied for now. @kubr1ck
  8. After you made your last appeal was at https://forum.mtasa.com/topic/117369-banned-by-mta-reason-trainer/, we found out that you were ban evading the global ban being appealed. So it was also banned. Also, that appeal was denied and we had a lenghty PM conversation following that. You know the situation is not going to change, and evading won't make your situation better. Nor does presenting yourself as a different person (registering another forum account to post this) in a matter of a few days, for the second time. @Darkhobit
  9. It was a result of the same issue as described in https://forum.mtasa.com/topic/117131-network-trouble/?do=findComment&comment=956241
  10. A definitive fix is available. Install´╗┐ this update: https://nightly.mtasa.com/?mtasa-1.5-rc-latest @Flexxy @Willian#
  11. Does it work in: - Windowed mode - Borderless mode - Borderless "keep res" mode Please test each of them in MTA settings > video and let me know, @purple baguettes
  12. Please refer to last posts in: https://forum.mtasa.com/topic/117131-network-trouble/?do=findComment&comment=956229 We found another issue and will release a new update ASAP. @Willian#
  13. Okay, we just confirmed the problem. The revert of buggy changes failed partially. Thanks for helping us to test, stick to that build until we get a final update.
  14. You're on the right version now. There's no logical explanation for the issue to be found in recent MTA changes, since the thing that caused spectator bugs & network trouble was reverted. I'll still forward it for further investigation, although it is possible that as I indicated, it being a script flaw often found on racing servers, your renewed attention for spectator in general makes you notice it or finally report it. To make absolutely sure, please try with https://nightly.mtasa.com/mtasa-1.5.6-rc-18445-20190525.exe
  15. @Flexxy, i just checked your client and it turns out you're not using the right update. You're on r18560 and the fix for spectator issues arrived in r18660. You can verify that you're not updated by writing "ver" in F8 console. Please install this build: https://nightly.mtasa.com/?mtasa-1.5-rc-latest So all doubts about the fix in this topic are thus far unconfirmed