• Content Count

  • Joined

  • Last visited

  • Days Won


AleksCore last won the day on January 25

AleksCore had the most liked content!

Community Reputation

9 Neutral

1 Follower

About AleksCore

  • Rank
    Punk-@ss B*tch


  • Interests

Recent Profile Visitors

1,186 profile views
  1. --client-side code addEventHandler ( "onClientVehicleEnter", root, function () iprint(setVehicleHandling(source, "modelFlags", 0x00002000), "client-side") end ) --server-side code addEventHandler ( "onPlayerVehicleEnter", root, function(theVehicle) iprint(setVehicleHandling(theVehicle, "modelFlags", 0x00002000), "server-side") end ) client side returns false for some reason, server side works great. Weird
  2. actually forced resource to stop on map change and it worked!
  3. You need this functions: and or or Example: function myFunction() --code here end addEvent("myCustomEvent", true) addEventHandler("myCustomEvent", root, myFunction) Then trigger this event using one of the trigger functions, for example: triggerServerEvent("myCustomEvent", root) "root" means it will be triggered for all elements and all resources, see wiki for more details That's it. P.S. not 100% sure thought, lazy to check P.P.S. also it can be something like that: myResource = getResourceFromName("myResourceName") myResourceRoot = getResourceRootElement(myResource) triggerServerEvent("myCustomEvent", myResourceRoot) So you call this event only for 1 resource, instead of telling all other resource about this event and creating additional load on CPU etc
  4. Well, exact problem is resource not stopping sometimes for some reasons. And no one start it manually, it's all done only using include feauture, so I think it's a bug. Maybe really not a big problem. I will use some event (something like onMapStopping) to reset all the things in my coremarkers, then it should work I think. P.S. oh no. That's dumb. I am completely lost P.P.S. funny thing it's all already working great but bug happens sometimes and it's really annoying. So maybe in future projects better to not use include at all to avoid bugs
  5. Hello. I have a problem, I think <include resource .. thingie possibly a bit bugged... And I need a help with it. I have made so called "coremarkers" resource. How it works: you create a race map, put objects (solid boxes model=3798). Open map meta.xml and add <include resource="coremarkers" />. Then when map starts, coremarkers resource starts too and it converts solid boxes into floating boxes without collisions (pickups). Usually it works great, so, map starts, coremarkers start, map stops, coremarkers stop. BUT sometimes coremarkers not stop and it cause problems. I think it's a bug and I don't know exactly how to reproduce it. At some point of testing,coremarkers simply not stop or not start when map starts. Perfectly coremarkers should start when map with coremarkers starts and restart if map played again or stop if map without coremakrers started. And it actually works like that but not always. Must be possible to fix it using Lua scripting but I feel like it's rather hardcoded problem with <include resource.. and honestly no idea how to fix it ezly. Need to write checker which will look into meta.xml and see what resource included and then start it when required and stop. I really don't like this solution Sounds like some annoying bug no one will look into but I hope someone can help me or at least confirm it. About include resource is bugged I know long time ago I think even some scripters confirmed it too. I hope it can be fixed as it's really important thing. and map for tests
  6. maybe this script will be useful for you
  7. Aaaand I finally found a solution which I like and I want to share it with everyone. So basically now I am using "borderless keep res" mode in MTA. In the app Gamma Panel (link above) I set brightness profiles. One is "High" for MTA with a bit higher brightness and hotkey Num8, and one is normal, default, hotkey Num5. Of course it would be pain in the ass to click hotkeys everytime to change brightness, so there is a solution for this also! Install "AutoIt!", create a simple script and run it: While 1 WinWaitActive("[CLASS:Grand theft auto San Andreas]") Send("{NUMPAD8 down}") Send("{NUMPAD8 up}") WinWaitNotActive("[CLASS:Grand theft auto San Andreas]") Send("{NUMPAD5 down}") Send("{NUMPAD5 up}") Wend Now for me it works perfectly. I am personally happy with this tricky solution. Good if someone will use it too. P.S. never used AutoIt before, but hopefully did a correct script. It works then its correct I guess (CPU usage by script 0%)
  8. that's currently the best what I found. Not automatic but at least with hotkeys
  9. There is a solution, use borderless mode. But then there is trouble with brightness. I have an idea about this too, but need programming skills which I don't have. Need a small app which would increase brightness when MTA SA window is active and then return brightness to normal when minimized.
  10. Ok sorry, it's KINDA not a problem directly with MTA, because I have just tried MTA SA version 1.4.1 and bug reproduces. Then as Haxardous guess on GitHub it's a problem with Windows 10 latest updates. That's really sad then as I don't want to downgrade my windows.
  11. Also I asked players, they also experience this problem. So basically now we returned to 2006 year when minimizing basically didn't worked. Now it works but better to don't use it Borderless mode should be fixed or Fullscreen, it doesn't matter for me but something requires a fix
  12. It's not a problem with my game or PC (problem isn't on my side so I can't fix it)
  13. CPU and everything is pretty relaxed, gta sa process are not in "do not respond" status
  14. Topic name says everything. Happens really too often so I can't do scripting or play. I am using fullscreen mode because in borderless modes brightness too low and can't be changed (probably in borderless mode such bug not happens but I can't use it as it's too dark). Happens on any server. As far as I know this problem is pretty popular but I haven't found a topic about that. Sometimes game restores but it takes too much time. Sometimes crashes. PC is good, also never had this problem before in earlier MTA versions (though haven't really played last year or more).