![]() |
|
#11
|
||||
|
Quote:
After installing the 4gb patch i logged in and out of 4 different accounts and 30+ chars and then played the game all day and did not crash once, without it i crash every other logout. I also tested it on the qeynos zoneline and zoned in and out of north qeynos 20+ times not a single crash. The 4gb patch makes my game beyond stable, if i remove it i crash on qeynos zone 50/50 and every other logout. I have a rtx 3070 GPU and a ryzen 7 3700x CPU incase that matters. I also have dgvoodoo with custom texture packs installed and i run the game in compatibility mode. | |||
|
#12
|
|||
|
noticeable improvement for me as well, rtx 3060 ryzen 5 9600X
windows 11 didn't like the midi driver apparently, i had to reinstall it today and haven't installed 4gb patch or midi driver in linux yet, i was crashing a lot switching characters there so i assume lowering it to 4gig vram will fix that because i had it set to the highest possible in Lutris iirc | ||
|
#13
|
|||
|
bump
| ||
|
#14
|
|||
|
wow i didnt do anything of this, lets check how it goes! thanks for the effor!
| ||
|
#15
|
|||
|
didnt know about 4Go patch, thanks ! this is a very usefull thread
| ||
|
#16
|
|||
|
Can you please post the install portion again? I followed the instructions step by step in the current wiki guide and for some reason the Launch Titanium keeps giving me the error message "windows cannot find eqgame"
| ||
|
#17
|
|||
|
To use Everquest with a utility that forces borderless windows (I use SmartContextMenu), go to DirectX tab of dgVoodoocpl and make sure 'Disable Alt-Enter to toggle screen state' is checked.
In nvidiaProfileInspector, make sure antialiasing is turned OFF in the Everquest profile. Otherwise text will be unacceptably blurry.
__________________
_____
Green: Feressa | ||
|
Last edited by charleski; 10-02-2025 at 03:28 PM..
| |||
|
#18
|
||||
|
Quote:
| |||
|
Last edited by Delfofthebla; 10-10-2025 at 02:37 PM..
| ||||
|
#19
|
||||
|
Quote:
__________________
_____
Green: Feressa | |||
|
#20
|
||||
|
Quote:
Ah, so it isn't a true borderless window. Since the "borderless" resolution does not differ from the actual windowed resolution, it probably doesn't generate the issue. Damn. I tried SmartContextMenu (along with every other borderless tool under the sun) and I was unable to fix the issue when going for a true borderless experience. | |||
![]() |
|
|