It has trouble with the gaps where the badges are. I made this interface to give a little more insight into what is going on. The problem with these gaps is that it takes a lot of cpu to check the end of each line for those gaps. I still have to make some improvements and maybe hardcode the individual icons, but that takes a lot of time.
It depends on what your operating system/drivers think the quickest way from rendering pixel to your screen is. Since NXT uses OpenGL for rendering, DirectX isn't necessarily involved in that. Some driver update could decide that it's quicker to skip the DirectX part. I wouldn't try to tinker with that as no other software is usually concerned with this.
Updated the afkwarden chat alerter settings. It will now show what it is reading and you can click on whatever you want to set as a trigger.
Also improved the color picker for the chat alert a bit to work on bright backgrounds as well.
Added an alert that triggers what an dialog shows. You can use this to trigger when your inventory is full.
It's very common that directX capture doesn't work. In the NXT client it is more of a coincidence depending on your hardware if it does work. OpenGL should work on all hardware and driver combinations, however it can get messed up by other capture/overlay programs. OBS for example breaks Alt1 OpenGL capture if you start it before Alt1. You should try disabling some capture/overlay programs if you use those. Things like shadowplay/obs/fraps/steam overlay. You have to restart your rs client if you think you found it otherwise it won't help.
Have you tried opengl or desktop capture? It should troubleshoot/toggle this automatically when you use some Alt1 features (pressing alt+1 or opening an app). It's fairly common that directX capture doesn't work, it depends on a lot of things like your graphics card, os, drivers etc. That's why there is opengl capture.
I forgot to update that text, the alert was triggering for those already.
I'm going to leave it at jad waves for now, you have about 5-10 sec to react before the first hit which should be enough. Otherwise i'm afraid it will alert more waves than not and the jad alerts are like 50sec early. The progress bar also starts filling 3 waves before jad so it should at least give an indication of when to start looking. I'll probably make an interface to choose the waves in the future but i'm going to leave it at this for now.
Scale, i could make one without to much trouble but i need some images of the wave number indicator. I just did wave 1-5 with a random preset before getting a dil without melee weapon. If you can post some images of the wave counter with number 6-10 on i'll make it into an alerter. You can use alt+2 shortcut to make and upload the images then just paste the url here.
I actually got quite far with this for the java client. The nxt client works slightly different from java and makes it a lot harder to do. By far the largest problem is not looking up the value like jagex claims it to be, it is recognizing the items. There are a ton of items that look very similar and they also look different between updates or depending on your graphics settings. There are 40000 different items now. There is also the problem that some items actually use the exact same model. Tectonic energies and ashes are quite bad in that (700k vs 200gp).
For now the project is on hold as I don't have a lot of time to work on Alt1 anymore, the new problems with nxt and i'm also kind of waiting to see what happens with the bank rework. I'm kind of expecting jagex to make it and ask money for it like the wealth elevator. I might pick it up later if that's the case.
Make sure that compatibility mode is not on, Alt1 does a lot of DPI related stuff normal programs don't have to do and treating it as DPI-dumb makes it a lot worse.
The Alt1 menus should scale along with all other programs on your computer. The apps will scale to the level Alt1 thinks rs is at, it might have detected the scaling level of rs wrong. Make sure the override dpi checkbox is not checked.
Also, you have to restart your computer after changing DPI related settings in windows for it to fully take effect.
Do you get the lost fps back after closing the app but leaving Alt1 open?
- If you do get the fps back it probably means some weird problem with the built in browser.
- If you only get the lost fps back after closing Alt1 or restarting rs it is probably a conflict with Alt1 and another capture/overlay program you have. In that case there should be no lag if you switch to desktop capture, turn off the automatic capture mode detection checkbox and restart rs. However desktop capture sucks for other reasons.