Werewolves and Vampires are an untapped potential for atmosphere and body horror. With this horror renaissance that has been occurring in the last couple of years, I really do feel like terrifying werewolf and vampire movies are right around the corner.
No more superhero or love stories involving these creatures. Show us them in their full, fanged force. I want to see a vampire drain the fucking life out of a character as we watch the whole process. I want to hear the screams of pain as someone transforms into a werewolf. I want to see genuine dread, terror, and fear in the eyes of characters confronting these monsters.
Y'all, find yourselves someone who will work through all your anxiety and depression with you because they love you enough to help you find the other side.
There has been a bug around for ages, that results in the mouse suddenly jumping to the middle of the screen or other erratic behavior. A simple google search for "wow mouse jumping" shows up a ton of results going back for years. Blizzard has even created a dedicated page to this issue over here: https://eu.battle.net/support/en/article/000014597
Proposed solutions have always involved the following things, among others: Disabling third party mouse software, disabling max foreground FPS, enabling/disabling vsync, disabling/enabling hardware cursor. There isn't a single solution that works for all people, but the proposed solutions have been successful in some cases. So what's up? Turns out the root cause of the issue has always been a race condition. Playing with settings like these make the race condition less/more likely to resolve correctly. So what's really going on? People playing World of Warcraft on Linux through Wine have analyzed the winAPI calls that are being made. Schematically, WoW does something like this:
OnMouseButtonPressed(): HideCursor() SaveCurrentCoordinates() WarpToWindowCenter() OnMouseButtonRelease() ShowCursor() WarpToSavedCoordinates()
So when you press the mouse, it's is hidden, the current coordinates are saved, and the mouse is moved to the middle of the window. When you release the mouse button, the cursor is shown and warped to the saved coordinates so it appears at the same location where you left it.
However, in the winAPI (and under wine as well), it is NOT allowed to warp the cursor while it's visible, since you'd then have a program moving the mouse cursor. So why does this piece of code still work in most cases? We have a classic race condition: ShowCursor() will complete as soon as possible, so it doesn't lock the thread that is executing this command. What it actually does, is that the cursor will be made visible on the NEXT frame. Therefor, the WarpToSavedCoordinates() command will still be able to move the cursor while it's still invisible.
If WarpToSavedCoordinates() is quick enough, this code will work fine, but if the cursor is already visible, the cursor cannot be moved. This means for the end user, the cursor will appear/jump in the middle of the screen, because the cursor was moved to the middle of the screen during the OnMouseButtonPressed() code.
The fix for this issue is incredibly easy: Simply swap the... keep reading on reddit ➡
Recently, I've been having this debate with my dad as well as my roommate when I attended Michigan and it was prompted when the OSU/Clemson matchup was announced.
Having attended both Michigan State and Michigan (my alma mater), I've never been a fan of OSU. I also really appreciate the entire rivalry + all the history, which is one of my favorite aspects of CFB.
However, if I'm being honest with myself, the big reason why I hate OSU is because of the schools I went to and their rich histories. Again, I love this aspect of CFB and love cheering for my schools, but I never had a personal reason to hate OSU. I'll admit, they have a very respectable program and I've never met a "bad" OSU Fan (in person).
Now, when it comes to Clemson, I've actually never liked their team or Dabo. Anytime they play, not only do I want them to lose, I want them to get destroyed. I feel as though my hate for Clemson has more personal reasoning compared to my hate for OSU, which is mostly the historic rivalry.
However, when it came time to the OSU/Clemson game, my Michigan friend and my dad were both surprised and almost disgusted that I would ever cheer for OSU.
My friend said I'm basically turning my back on my school and just because Michigan is having a rough time recently, it doesn't mean I should give up on them or jump schools.
I will admit that I do feel a little "dirty" cheering for OSU or admitting that I want them to win the championship, but I also believe that as Michigan's rivals, I'd rather we play the best team in the country every year, even if they kick our ass, instead of a bad program. I also think a win for OSU is a win for the B1G, which benefits all the schools in the conference. Also, I think the recruiting process has changed and is more national compared to regional, which means a school in your conference winning doesn't mean you'll have no good players to recruit.
Even with those arguments and thoughts, my friend still disagrees with me and thinks I'm a horrible Michigan fan who is giving up on his team. And I've seen similar comments throughout this forum and game threads.
So my question is, when is it fine to root for your rivals? If your school isn't in the picture but your in-conference rivals are, that is who you want to win. What are your guys' thoughts on that?
Ant group looks like it will Be forced to return to basic money transfers and concede any realm which may interfere with Chinese banking giants (Crony communism ehh?)
Ali Baba Has also implemented a 10B stock buyback, but it wasn’t enough to keep BABA from trading lower in Hong Kong in the early hours.
Just when we thought the worst was behind us last week ...
Fuck the patriots!
Hey there r/androidapps! I'm here to show off a new Android app I've published that I think a certain audience may find useful.
Ever heard of ADB? If not, you likely won't need this app. But for those of you who have used or encountered ADB in the past, you know that you usually need a PC to shell into your phone. While yes, apps such as Termux exist, they don't have elevated privileges as ADB does.
Behold, LADB! A truly local ADB shell server. That means no root, no computer, and no hassle.
Here's how it works. LADB bundles an ADB server within the app libraries and extracts it upon runtime (W^X compliant). Normally, this server cannot connect to itself because it requires an active USB connection to be visible. However, Android's Wireless ADB Debugging feature allows the server and the client to speak to each other through localhost. LADB initializes the ADB server and asks to connect to localhost, solving this limitation.
So, what can you do with it? Well, anything that ordinarily uses "adb shell <command>" can now be done locally. That means granting apps special privileges for things like SystemUI Tuner, many logcat apps, and generally anything else that needs elevated privileges. That's not all though. You can disable system apps using
pm disable-user com.android.whatever, you can enable and disable system overlays with
cmd overlay, you can get a logcat with
logcat -d | tail -n 20, and the possibilities go on.
Here's the link to the app. It is paid, and it's actually my first paid app in a very long time. If you just need to use the ADB server for a minute, you can buy the app, use it for a few minutes, and then refund it through the store (don't tell Google).
Note, this app is also open source! I'm a huge fan of FOSS so I went ahead and published the app on GitHub so that anyone can compile the app for themselves for free. Any purchases through the Google Play store can be considered as donations <3.
I'm always available for support if you encounter any issues either by direct message, by telegram (... keep reading on reddit ➡