Jump to content

SKay

SPCT
  • Content Count

    1363
  • Joined

  • Last visited

Community Reputation

186 Excellent

9 Followers

About SKay

  • Rank
    That one bloke who's got a birthday daily

Recent Profile Visitors

1583 profile views
  1. I forgot to weigh in on this thread when this was originally posted. Better late than never. The reason why EAC disables manual editing of CPU Affinity/Priority for processes it attaches to is for security reasons. For most games, EAC is considered a child process which starts and hooks into the game where necessary. On start of a child process, the child process inherits the parent process Affinity for simplicity reasons on Windows. Very rarely will you ever need a child process to access more processing cores than the parent process, and also simplifies data access across processing cores. Setting process priority higher for the game process should not be necessary. Very rarely does it do anything, and has much wider implications. To quote this article's answer on Stack Overflow: "A realtime priority thread can never be pre-empted by timer interrupts and runs at a higher priority than any other thread in the system. As such a CPU bound realtime priority thread can totally ruin a machine. Creating realtime priority threads requires a privilege (SeIncreaseBasePriorityPrivilege) so it can only be done by administrative users." Any process that has real time priority essentially can get ahead of anything else, force other threads to wait until they are done and are one level below the Operating System in terms of priority for CPU time. Perfect if you wish to have your game squeeze a frame or two, or if you wish to get your cheat to circumvent EAC detection by bypassing it altogether. And as for forcing CPU Affinity/Priority through Registry Edits, this is NOT SUPPORTED by EAC at all, and has resulted in bans for EAC circumnavigation in other games. You perform this Registry Edit AT YOUR OWN RISK. As far as this RegEdit is concerned, it would be considered circumnavigating an EAC safeguard.
  2. A ban is not handed out without reason. The fact that @MattScott has said "Customer Service deleted your graphics library after getting my approval." should be an indication that you made graphical designs that were against the Terms of Service. You were obviously warned by a GM, then ignored the warning. When a GM tells you not to do something, do not neglect what they say and try the exact same thing again.
  3. Almost like Ketog is enlightened. Or maybe he actually understands that ARMAS guns are variant guns. IR1 is an insult to anyone who bought it. HS3 at least justifies the weapon's existence.
  4. Bump. Don't worry, it's for a reason. Slightly newer machine the webserver sits on. Now includes a re-write. This is Version 1.2, but it's also only the beginning while I actually write code that isn't chicken scratch.
  5. I heard a rumour. The rumour was SuperToaster is actually SuperSuperToaster.
  6. That would just end up back to the old behaviour, especially seeing as most stages are 4+ stages long. So this does absolutely nothing other than even making it worse for lower skilled players.
  7. That's... that's me. Yeah. I voiced a few (and wrote the script of several) of the JMB videos for SlimTheShady back in the day. This is indeed one of them.
  8. I created a video "advertising" the N-TEC 7c "New Glory". Just as a personal venture into content creation after being inspired by content creator Ahoy. For me personally it was to get back into content creation again and to try and achieve a level of professional quality. As well as a sort of experiment into how I want to contribute video's going forward. Hope you like it.
  9. I'm presuming you're downvoting the post you quoted because of this image of a fair amount of zombie processes. The post I put up explained what these are, so I'm not sure why you're downvoting it. To quote myself:
  10. The APB_Catcher is the process that handles exceptions thrown by the main game executable. Contrary to what OP states this process is absolutely necessary. Without it the game can potentially crash in a way that is not graceful and can cause issues beyond that. The APB_Catcher is a child process, i.e it's parent (the main game executable) is responsible for handling it's execution and termination based on it's own run time. The issue you're seeing is to the fact that the APB_Catcher process is not being terminated correctly by the main game executable, resulting in a zombie process. A zombie process needs to be terminated manually or by a program that is designed to determine any dead processes. Also instead of pinging Matt Scott directly, maybe leave a bug in the proper place. For like the 100th time. - SKay
  11. Iazer

    FeelsBirthdayMan Happy Birthday FeelsBirthdayMan

  12. You're now proving my point, thanks. Experimentation with changes is the aim of the game, trying to see where they could push the RFP to. They never said "woops we messed up", that'd imply a mistake was made when they were experimenting on where to place the RFP. It was never pushed to the LIVE action districts, it was in a closed off area where the testing of the changes was encouraged, yet no chance was given by the wider community for the aforementioned reason of "they thought they knew better". There is 0 excuse for not testing the changes. You think they were off the mark based on the stats. Did you test them? If the answer is no, you can't just assume your viewpoint is correct. If you're not willing to even bother confirm what you think then this rodeo will continue going around in circles and you will not get your stats. If you want stats, you gotta put in the work. Don't just assume. Confirm.
  13. You really do need to read the patch notes son. This kind of whinging is the kinda thing I'd find from a baby stuck in a pram. A direct quote: "In both districts these guns will both now prevent you from weapon swapping while the re-fire or burst fire timers are active." This is the same treatment the HVR got. It prevents you switching to a sidearm while the action is engaged, i.e you fire, and have to wait for the burst delay to be passed before being able to continue. Please don't make threads as if the forums can be a place for a cult of outrage. There is a thread specifically for this kind of material right here. And that is where it should be.
  14. Except that hadn't happened before when the exact stat changes were given. No-one bothered. Not now, not even back in the day. No issue with giving stats at a later date to give time for blind testing. But the effort needs to be put in first by the community. Armchair stat scrutiny is the main reason why a lot of APB's items are as they are. Because people thought they knew better and didn't bother actually testing.
  15. And that's exactly the reason why you should test the changes when the servers come back online. Armchair stat scrutiny helps absolutely noone.
×
×
  • Create New...