Well, my computer isn't immensely happy with 1 ms delay :3 For me the program takes about 30% CPU Load (17-20% on 10 ms), which would be okay, if osu! wouldn't be running :^)Roan wrote:
Guess I'll at least add the option then since that takes no effort anyway :3. There's one thing to note though the osu! graphics are actually graphics, the overlay is just a normal program window so it isn't quite as optimized for quick rendering updates. I'm also not so sure how well the windows timers would handle it since they are imprecise. Also 10 ms is also quite fast![]()
- I implemented a 1 ms and 5 ms update rate for you to play with :3 it does kill your CPU though, my CPU usage has increased by 400%-500% times. Also this in combination with big graph backlog can really kill your CPU. Also you need a very fast computer to properly run this since all the update calculation have to be done in 1 millisecond otherwise the calculations aren't 100% accurate anymore. Well have fun I guess
But anyway, it's still
Okay c:Roan wrote:
Quite right this isn't fixed yet. I read your post after I had already finished the new release. Also because this is quite a difficult bug to track down I have no idea when I will have fixed it completely
Roan wrote:
Better find some more bugs then

Yaay ヽ(。・ω・。)ノRoan wrote:
true however I don't think I'd ever run a program again if it instantly filled up my RAM xD. Is the ! sign even allowed in a windows username? (just checked it is
maybe I should atleast throw an error at the user then in order to prevent RAM overload xD)
- I also implemented a fix for the infinite instances problem just in case someone's username ends with a !
Do you just throw an error message immediately, or did you actually fix it? o:
nah, definitely not the weirdest bug I've ever seenRoan wrote:
I think I'm officially labeling this as the weirdest bug I've ever encountered xD.

This is my weirdest (and deadliest) bug yet
I've seen an antivirus labeling itself as malware, moving important DLLs of itself into quarantine, then completely malfunctioning and finally also moving parts of the windows operating system into quarantine. This bug was pretty bad, since it occurred on every machine that got the update! It was very tricky to fix and if you restarted your computer, you'd just get a blue screen of death on startup immediately, forever 

haha, better fix themRoan wrote:
Even worse, this probably affects other programs I wrote too hmm...

It does! ^^Roan wrote:
- Filter the config selection dialog to only show config files. This makes finding the files a lot easier xD.
Great! c:Roan wrote:
- And I also fixed the rendering problem you were having, well it's really persistent so I'm not 100% sure but atleast your config file works now.
Those would be great, yeah (ノ・ω・)ノRoan wrote:
And that's it for nowgoing to work on editable config files next :3 (no eta though
)
So, here are a few more feature requests and bugs and other stuff:
1) Bug: Pressing any arrow keys won't move the window by one pixel, it will move it by two instead

2) Notice: I just stress tested your program, I have to say, it is better than I thought it would be! When idle it takes about 2% CPU Load, while under maximum stress I could simulate (around 700 keystrokes per second) it takes around 35-40% CPU Load! So when idle, it really doesn't do anything besides refreshing it's display, but when it has to, it goes very high on the CPU and still doesn't struggle c:
2.5) Another extra notice: I played around with it some more


3) Feature request: Add an option to the context menu that allows the user to change the options again! So simply the option "Configure" that closes the overlay and reopens the config window! This could be combined with 3.5) very nicely.
3.5) Make the overlay live-configurable. So when clicking on the Configure button, the overlay doesn't close, but the config window still opens!
This config window would have to be slightly different, there qould have to be an Apply button, that doesn't close the window, but I don't think it would be that hard to do! Correct me if I'm wrong, of course c: