But you said old drivers didn't help you, which is weird, because it helped the others...
I finally RESOLVED this issue. I didn't install anything additionally. I had a weird feeling that NVidia was somehow behind this. To cut it short, all I did was SHUT DOWN all NVidia processes (NVidia share and something else, can't remember the name). This fixed the following for me:Hello, recently I have experienced cursor flickering in the menus and the world map. I will provide screenshots of my settings in the launcher and what I have done to try to resolve the issue. I didn't provide audio settings since I doubt that would have any impact on the matter. There were older threads of this issue but all the things I tried from them didn't work, so that's why I'm making this one, also there was a Reddit post that also didn't help. What Also happens in the world map the game stutters when I try to look around or spin the camera. This isn't present in battles.
Here are the settings:
Previously I used to have my fps locked at 999 and that caused no issues at all, but changing it to 120 seemed to suppress it a little bit, but after a couple of minutes, it appears again.
Things that I have tried:
- Forcing vsync both through the game and through nvidia control panel.
- Locking the fps to 60 with and without vsync.
- Starting windowed then pressing alt+enter to make it fullscreen again.
- Updating DirectX and gpu drivers.
- Changing resolution.
- Reinstalling the game.
- Reinstalling Steam.
- Verifying game files through Steam.
- Disabling Steam overlay.
- Deleting the files in the appdata folder.
- Disabling blood.
- Deleting the .ini file in the Documents folder.
- Increasing the "render_buffer_size" in rgl_config.ini.
- Tried using DirectX 7.
- Forcing Single Threading.
- Tried changing all the settings in-game.
- Running the game as administrator.
- Running the game with Windows xp service pack 2 and 3.
All help will be greatly appreciated. If I need to provide anything else just tell me and I gladly will. Thanks in advance.
drive.google.com
Registered just to say this: God bless you, I hope this solution would work for others as it did for me.This is due to the program doing a SetCursor with NULL making the cursor invisible using GDI, then doing a SetCursor with DirectX to set the cursor visible again. Whilst I do not the exact mechanism as to why it causes FPS issues, I'd guess that it's due to some kind of GDI/DirectX synchronization having to occur.
A workaround is to patch byte at 00216FA5 from 00 to 01 In mb_warband.exe (for steam version at least). This causes the SetCursor to fail thereby preventing the aforementioned hitching. In my system my FPS became steady and never once dipped again.
Side effects may include a cursor being visible when it shouldn't be (though I doubt it).
This may be an NVIDIA bug, it might be a Windows GDI bug, but really, ultimately, this is just a poor programming bug. There is no reason I can think of why the cursor must be hidden by GDI just to be shown again by DirectX. Perhaps editor mode? Maybe?
-----
EDIT: -- I'd like to point out that after further research the above is actually valid and usual way of handling this according to the Microsoft documentation. Why this causes flickering is unknown, and why ignoring the setCursor fixes it is also unknown.
IDirect3DDevice9::ShowCursor (d3d9helper.h) - Win32 apps
The IDirect3DDevice9::ShowCursor method (d3d9helper.h) displays or hides the cursor.docs.microsoft.com
-----
Anyway, I develop programs for my real life, and I've written an automatic patcher to make the single byte change above (for steam version only), I'll link it below (if it works, not sure if the forum will mangle it).
It's an exe file because that is easiest to distribute. Reminder that you should never download .exe files the internet, but here you go:
WarbandPatcher.exe
You can always restore the Warband files using Steam to re-validate them if you think something is wrong.
How do I change an exe file? I need a special proggram or somethign?This is due to the program doing a SetCursor with NULL making the cursor invisible using GDI, then doing a SetCursor with DirectX to set the cursor visible again. Whilst I do not the exact mechanism as to why it causes FPS issues, I'd guess that it's due to some kind of GDI/DirectX synchronization having to occur.
A workaround is to patch byte at 00216FA5 from 00 to 01 In mb_warband.exe (for steam version at least). This causes the SetCursor to fail thereby preventing the aforementioned hitching. In my system my FPS became steady and never once dipped again.
Side effects may include a cursor being visible when it shouldn't be (though I doubt it).
This may be an NVIDIA bug, it might be a Windows GDI bug, but really, ultimately, this is just a poor programming bug. There is no reason I can think of why the cursor must be hidden by GDI just to be shown again by DirectX. Perhaps editor mode? Maybe?
-----
EDIT: -- I'd like to point out that after further research the above is actually valid and usual way of handling this according to the Microsoft documentation. Why this causes flickering is unknown, and why ignoring the setCursor fixes it is also unknown.
IDirect3DDevice9::ShowCursor (d3d9helper.h) - Win32 apps
The IDirect3DDevice9::ShowCursor method (d3d9helper.h) displays or hides the cursor.docs.microsoft.com
-----
Anyway, I develop programs for my real life, and I've written an automatic patcher to make the single byte change above (for steam version only), I'll link it below (if it works, not sure if the forum will mangle it).
It's an exe file because that is easiest to distribute. Reminder that you should never download .exe files the internet, but here you go:
WarbandPatcher.exe
You can always restore the Warband files using Steam to re-validate them if you think something is wrong.
There was not any patch for Native Warband last week. We only changed a setting for modding workshop but that was not a patch that you download.
I hadn't done the patch, and after someone asked for support on reddit I sent them to this post, so I tested this method.
Thank you dude, god bless you and your family!! After hours of searching a solution I found your solution, THANK YOU A LOT!!!!This is due to the program doing a SetCursor with NULL making the cursor invisible using GDI, then doing a SetCursor with DirectX to set the cursor visible again. Whilst I do not the exact mechanism as to why it causes FPS issues, I'd guess that it's due to some kind of GDI/DirectX synchronization having to occur.
A workaround is to patch byte at 00216FA5 from 00 to 01 In mb_warband.exe (for steam version at least). This causes the SetCursor to fail thereby preventing the aforementioned hitching. In my system my FPS became steady and never once dipped again.
Side effects may include a cursor being visible when it shouldn't be (though I doubt it).
This may be an NVIDIA bug, it might be a Windows GDI bug, but really, ultimately, this is just a poor programming bug. There is no reason I can think of why the cursor must be hidden by GDI just to be shown again by DirectX. Perhaps editor mode? Maybe?
-----
EDIT: -- I'd like to point out that after further research the above is actually valid and usual way of handling this according to the Microsoft documentation. Why this causes flickering is unknown, and why ignoring the setCursor fixes it is also unknown.
IDirect3DDevice9::ShowCursor (d3d9helper.h) - Win32 apps
The IDirect3DDevice9::ShowCursor method (d3d9helper.h) displays or hides the cursor.docs.microsoft.com
-----
Anyway, I develop programs for my real life, and I've written an automatic patcher to make the single byte change above (for steam version only), I'll link it below (if it works, not sure if the forum will mangle it).
It's an exe file because that is easiest to distribute. Reminder that you should never download .exe files the internet, but here you go:
WarbandPatcher.exe
You can always restore the Warband files using Steam to re-validate them if you think something is wrong.
I've updated the patcher program to try to automatically detect the correct byte location no matter what version of Warband you have, Steam, non-steam, old versions or hopefully any future ones.
You're right! Not only did it patch WFaS, it also patches Blood and Gold: Caribbean! Neat. Thank you for further developing the app.
nasıl bu şekilde yapılır anlamadım nasıl yama yaparım warband exe yeBunun nedeni, programın imleci GDI kullanarak görünmez hale getiren NULL'lı bir SetCursor yapması ve ardından imleci yeniden görünür hale getirmek için DirectX ile bir SetCursor yapmasıdır. FPS sorunlarına neden olduğu konusunda tam bir mekanizma olmasam da, bunun bir tür GDI / DirectX senkronizasyonunun gerçekleşmesinden kaynaklandığını tahmin ediyorum.
Geçici bir çözüm, 00216FA5'te baytı 00'dan 01 In mb_warband.exe'e (en azından steam sürümü için) yamalamaktır. Bu, SetCursor'un başarısız olmasına ve böylece yukarıda belirtilen otostopun önlenmesine neden olur. Sistemimde FPS'im sabit kaldı ve bir daha asla batırılmadı.
Yan efektler, olmaması gerektiğinde (şüphe etmeme rağmen) bir imlecin görünür olmasını içerebilir.
Bu bir NVIDIA hatası olabilir, bir Windows GDI hatası olabilir, ancak gerçekten, sonuçta, bu sadece zayıf bir programlama hatasıdır. DirectX tarafından tekrar gösterilmek için imlecin neden GDI tarafından gizlenmesi gerektiğini düşünmem için hiçbir neden yok. Belki editör modu? Belki?
-----
EDIT: -- Daha fazla araştırmadan sonra yukarıdakilerin aslında geçerli ve Microsoft belgelerine göre bunu ele almanın olağan bir yolu olduğunu belirtmek isterim. Bunun neden titremeye neden olduğu ve setCursor düzeltmelerini neden yoksaytıp yoksayma da bilinmemektedir.
IDirect3DDevice9::ShowCursor (d3d9helper.h) - Win32 apps
The IDirect3DDevice9::ShowCursor method (d3d9helper.h) displays or hides the cursor.docs.microsoft.com
-----
Her neyse, gerçek hayatım için programlar geliştiriyorum ve yukarıdaki tek bayt değişikliğini yapmak için otomatik bir yamalayıcı yazdım (yalnızca steam sürümü için), aşağıda bağlayacağım (işe yararsa, forumun onu mangle edip etmeyeceğinden emin değilim).
Bu bir exe dosyasıdır, çünkü bu dağıtmak en kolayıdır. İnternet .exe dosyaları asla indirmemeniz gerektiğinin hatırlatıcısı, ancak işte başlıyorsunuz:
WarbandPatcher.exe
Warband dosyalarını her zaman Steam'i kullanarak geri yükleyebilir ve bir sorun olduğunu düşünüyorsanız bunları yeniden doğrulayabilirsiniz.
