PDA

View Full Version : [Guide] EQ under wine (Fedora LINUX 14+ 32 or 64bit)


cadiz
11-20-2010, 08:02 PM
I wanted to create a separate thread for this since the other helpful guide by mgellan is targeted towards Ubuntu, this one is specific to the Fedora Linux Distribution (http://fedoraproject.org) which is what I prefer.

Just a quick breakdown, there are a few reasons why wine will not run unpatched EQ/titanium for P99:

• There is a change to directx.c which needs to be made in the wine source code which fixes a crash when you enter world
• There is a modified DLL file which is required to fix some model/texture issues

I've taken the liberty of modifying the wine source code to include the code fix needed and building Fedora packages for those interested. Using binary system packages is much cleaner and easier than compiling/maintaining your own wine source code installation - below is a guide on how to get it working.

Here are the steps for a Fedora 14+ 32bit or 64bit installation:

• This assumes a Fedora 14 or 15 (http://fedoraproject.org/en/get-fedora-options) 32 or 64bit installation. It's possible that it may work for earlier versions or other RPM distributions like OpenSuSE (http://software.opensuse.org/112/en), there are no promises.
• This assumes you do not have wine installed already, if you do you need to remove the distribution packages via yum erase wine-*
• All commands in italics should be run as your normal user in a terminal window except for the ones noted to be run as the root user (package installation)

1) Install wine dependencies (if you don't have them)
note: run this command as the root user
yum install liberation-narrow-fonts nss-mdns openldap pulseaudio-libs liberation-sans-fonts

2) Download all of the rpms listed below, placing them in the same directory (you only need the x86_64 if you're running 64bit Fedora like me) You can paste the wget links below directly into the terminal.

http://funcamp.net/w/rpm/wine-1.3.6/i386/ (32bit and 64bit required)
http://funcamp.net/w/rpm/wine-1.3.6/noarch/ (32bit and 64bit required)
http://funcamp.net/w/rpm/wine-1.3.6/x86_64/ (64bit only required)

Download paste for 32 and 64bit Installation
wget http://funcamp.net/w/rpm/wine-1.3.6/i386/{wine-1.3.6-1.fc14.i386.rpm,wine-alsa-1.3.6-1.fc14.i386.rpm,wine-capi-1.3.6-1.fc14.i386.rpm,wine-cms-1.3.6-1.fc14.i386.rpm,wine-core-1.3.6-1.fc14.i386.rpm,wine-devel-1.3.6-1.fc14.i386.rpm,wine-esd-1.3.6-1.fc14.i386.rpm,wine-jack-1.3.6-1.fc14.i386.rpm,wine-ldap-1.3.6-1.fc14.i386.rpm,wine-nas-1.3.6-1.fc14.i386.rpm,wine-openal-1.3.6-1.fc14.i386.rpm,wine-oss-1.3.6-1.fc14.i386.rpm,wine-pulseaudio-1.3.6-1.fc14.i386.rpm,wine-twain-1.3.6-1.fc14.i386.rpm,wine-wow-1.3.6-1.fc14.i386.rpm}

Download paste for 32 and 64bit Installation
wget http://funcamp.net/w/rpm/wine-1.3.6/noarch/{wine-common-1.3.6-1.fc14.noarch.rpm,wine-courier-fonts-1.3.6-1.fc14.noarch.rpm,wine-desktop-1.3.6-1.fc14.noarch.rpm,wine-fonts-1.3.6-1.fc14.noarch.rpm,wine-marlett-fonts-1.3.6-1.fc14.noarch.rpm,wine-small-fonts-1.3.6-1.fc14.noarch.rpm,wine-symbol-fonts-1.3.6-1.fc14.noarch.rpm,wine-system-fonts-1. 3.6-1.fc14.noarch.rpm}

Download paste for 64bit Installation ONLY
wget http://funcamp.net/w/rpm/wine-1.3.6/x86_64/{wine-1.3.6-1.fc14.x86_64.rpm,wine-alsa-1.3.6-1.fc14.x86_64.rpm,wine-capi-1.3.6-1.fc14.x86_64.rpm,wine-cms-1.3.6-1.fc14.x86_64.rpm,wine-core-1.3.6-1.fc14.x86_64.rpm,wine-devel-1.3.6-1.fc14.x86_64.rpm,wine-esd-1.3.6-1.fc14.x86_64.rpm,wine-jack-1.3.6-1.fc14.x86_64.rpm,wine-ldap-1.3.6-1.fc14.x86_64.rpm,wine-nas-1.3.6-1.fc14.x86_64.rpm,wine-openal-1.3.6-1.fc14.x86_64.rpm,wine-oss-1.3.6-1.fc14.x86_64.rpm,wine-pulseaudio-1.3.6-1.fc14.x86_64.rpm,wine-twain-1.3.6-1.fc14.x86_64.rpm,wine-wow-1.3.6-1.fc14.x86_64.rpm}


3) change to the directory where you downloaded the RPMs
cd <download directory>

4) Install the packages via RPM
note: run this command as the root user
rpm -ivh --nodeps *.rpm

5) Initialize wine for the first time
if you have an existing ~/.wine directory then back it up first
mv ~/.wine ~/.wine-backup

winecfg
press ok to install gecko engine and whatever else comes up
when it's finished, click the audio tab to use either pulseaudio (default) or another sound subsystem like alsa/oss.

6) Copy your everquest program files into the wine directory
let's assume it's in a directory named 'everquest'
cp -Rv everquest ~/.wine/drive_c/Program\ Files\

7) Download and copy the modified DLL file which fixes the textures issue some people experience
DLL file courtesy of angeliqe (http://www.angeliqe.com/EQ.html)

cd ~/.wine/drive_c/Program\ Files\everquest
wget http://funcamp.net/w/d3dx9_30.dll

8) Add wine to your yum.conf exclude list so the distribution updates do not replace them
echo "exclude=wine-*" >> /etc/yum.conf

9) Run the game!
wine ~/.wine/drive_c/Program\ Files\everquest/eqgame.exe patchme
disable windowing effects like compiz for best results

10) Startup (optional)

Create a script to start everquest:
cat > eq.sh << EOF
#!/bin/sh
# start everquest
cd ~/.wine/drive_c/Program\ Files/everquest ; taskset -c 0 wine eqgame.exe patchme
EOF
(hit enter)

Make the script executable
chmod +x eq.sh

Add the script to your path:
echo 'alias eq="~/eq.sh"' >> ~/.bashrc
source ~/.bashrc

You can now create a link or desktop icon pointing to eq.sh to launch the game
You can also run eq in a console to launch the game

Errors and Caveats:
Fullscreen - I've had some issues with mouse control in full screen mode but I was able to tweak the WindowedWidth and WindowedHeight settings of my eqclient.ini to closely match my desktop resolution for the same affect. This seems to be a common problem on all Linux distributions, when I find a fix I'll update the guide but don't hold your breath :)
Sound - To enable sound run winecfg and click on the audio tab, then click ok. This will enable sound if it doesn't work at first run.
Yum Warnings - This may just be because of my testing/building but I had rpmdb complain about "missing requires" for a few packages after installing the modified wine package set.
To fix this I reinstalled the complainers:
note: run this command as the root user
yum reinstall esound-libs jack-audio-connection-kit

winecfg errors out on first run
If you get the following error ::

/usr/bin/winecfg: /usr/bin/wine: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
/usr/bin/winecfg: line 29: /usr/bin/wine: Success

You are most likely running a 64bit distribution without a 32bit GLIBC
To fix ::

yum whatprovides */lib/ld-linux.so.2 | grep glib
glibc-2.13.90-9.i686 : The GNU libc libraries
arm-gp2x-linux-glibc-2.3.6-9.fc15.noarch : Cross Compiled GNU C Library targeted
glibc-2.14-5.i686 : The GNU libc libraries

Now, pick the latest version and install it
yum install glibc-2.14-5.i686

No OpenGL Error

Application tried to create a window, but no driver could be loaded.
Unknown error (127).
err:d3d_caps:WineD3D_CreateFakeGLContext Failed to create a window.
err:d3d:InitAdapters Failed to get a gl context for default adapter
Direct3D9 is not available without OpenGL.

You are most likely running a 64bit distribution and you need to install 32bit video drivers

yum install xorg-x11-drv-intel.i686 mesa-libGL mesa-dri-drivers.i686

eqclient.ini - It's a safe bet to make sure your eqclient.ini is set to start in windowed mode first.

[Defaults]
WindowedMode=TRUE
[VideoMode]
Width=1600
Height=900
FullscreenRefreshRate=0
FullscreenBitsPerPixel=32
WindowedWidth=1600 <--- set to horizontal desktop resolution
WindowedHeight=850 <--- set to vertical desktop resolution (i subtract -50 pixels so I can see my taskbar in XFCE)

Additional eqclient.ini settings - use these if you have texture/shading issues
[Defaults]
APVOptimizations=TRUE
DisableWestBugFix=1
Sound=TRUE
TextureQuality=1
VertexShaders=0
20PixelShaders=0
14PixelShaders=0
1xPixelShaders=0
MultiPassLighting=FALSE
UseLitBatches=FALSE
WindowedMode=TRUE
TextureCache=FALSE
DoProperTinting=FALSE


Here are some screenshots of it working. I've been running in 16:9 windowed mode so I can do other stuff when nothing is happening in the game. Tested in gameplay with my Rogue and Enchanter.

(windowed mode, testing things out)

http://funcamp.net/w/eq_p99_fedora64-sm.png


(compiz/expose feature, working on other stuff)

http://funcamp.net/w/eq_p99_fedora64-3-sm.png

mrybczyn
04-02-2011, 10:51 PM
Sweet, have to try this. Only reason I even have a windows install is for P1999 :-)

ryandward
04-17-2011, 09:31 PM
Everybody is invisible when I try this lol

ryandward
04-17-2011, 09:32 PM
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.

cadiz
04-26-2011, 01:18 AM
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.
fixme:d3d:state_wrap (WINED3DRS_WRAP0) Texture wrapping not yet supported.

Hey ryandward,

I found a bug regarding this and missing textures here (http://bugs.winehq.org/show_bug.cgi?id=8176), - it's marked as fixed in the 1.1.x release quite a while ago but it may still affect some video cards (nvidia perhaps).

I'm assuming you have up to date spell file but try removing your spells_us.txt file completely anyways, I've seen Wine cache it.
Once you do that so you're sure you are starting clean please help answer the following:

• What video card do you have?
• What version of Fedora are you using (or other distribution if you're using my RPMs).
• Are you using fullscreen mode or windowed mode with a resolution set?
• What does your eqclient.ini file look like? You can use a tool like pastebin (http://pastebin.com/) and set the lifetime to "forever" and I'd be happy to take a look.

You can find my eqclient.ini file here (http://funcamp.net/w/eqclient-repo.ini) .. perhaps compare some of the options I've set there and see what works for you.

There's a good chance that you're probably just calling a shading or texture option not allowed in Wine.

Right away, I'd suggest changing these settings in your eqclient.ini first, that work really well for me in windowed mode (but setting the resolution to match my desktop display).
Try just copying and pasting these two sections into a new eqclient.ini file (backup up your old one first) - if it works then you know what is causing it.

[Defaults]
APVOptimizations=TRUE
DisableWestBugFix=1
Sound=TRUE
TextureQuality=1
VertexShaders=0
20PixelShaders=0
14PixelShaders=0
1xPixelShaders=0
MultiPassLighting=FALSE
UseLitBatches=FALSE
WindowedMode=TRUE
TextureCache=FALSE
DoProperTinting=FALSE


[VideoMode]
Width=1600
Height=900
FullscreenRefreshRate=0
FullscreenBitsPerPixel=32
WindowedWidth=1600 <--- set to horizontal desktop resolution
WindowedHeight=850 <--- set to vertical desktop resolution (i subtract -50 pixels so I can see my taskbar in XFCE)

miethos
08-04-2011, 03:34 PM
This is awesome! Will definitely try this out. Also, only reason I have a pesky win xp install.

Maladorm
09-17-2011, 07:31 PM
I've been trying to get p99 to work on my laptop which is currently running Fedora 15 32 bit. Followed the guide posted, but i keep getting an error after running the start-up command: wine ~/.wine/drive_c/Program\ Files/P99/eqgame.exe patchme


fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:advapi:SetSecurityInfo stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32ebc4,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32eed0,0x00000000), stub!
FINAL Couldn't open or read UIFiles\default\EQLSUI.xml
FINAL Couldn't open or read UIFiles\default\EQLSUI.xml
err:d3d:IWineD3DDeviceImpl_Reset Cannot change the back buffer format yet

was wondering if anyone else ran into this problem or if anyone had any idea on what I maybe doing wrong. :confused:

thanks in advance

cadiz
09-18-2011, 01:52 PM
This post (http://www.eqemulator.org/forums/showthread.php?t=24333) might help you, this is a common error that folks experience if they copy any sort of directory structure from and old/live EQ installation. Are you starting clean with a Titanium installation & only P99 spellfiles?
You want to start with a clean "UIFiles" directory and use something like the Velious UI listed in the getting started guide (http://www.project1999.org/files/veliousuiv3.zip)

You will also want to make sure your permissions are happy.. you need to make sure the local user also owns the EQ directories you just copied over.
(open a terminal)

chown -Rv `whoami`.`whoami` /path/to/eq/files

If this does not fix it and you are running clean I would recommend trying to run the 'eqgame.exe' while in the current working directory.

For example...

(open a terminal.. substituting my paths for yours..)

cd ~/.wine/drive_c/Program\ Files/eq_p99/
taskset -c 0 wine eqgame.exe patchme

See what happens there, the benefit of running in the terminal is you get all the verbose feedback.. the "warning:" type messages you can ignore.

Maladorm
09-18-2011, 02:03 PM
thanks for the help, running it out of the directory worked out.

It was indeed a clean install copied over from my windows machine. I may have copied over a different copy mistakenly though now that i think about it. I'll go through and do another install when i get some free time but for now this works. Thanks for the quick reply.

cadiz
09-18-2011, 02:07 PM
thanks for the help, running it out of the directory worked out.

It was indeed a clean install copied over from my windows machine. I may have copied over a different copy mistakenly though now that i think about it. I'll go through and do another install when i get some free time but for now this works. Thanks for the quick reply.

Sure, no problem. Happy to help.

If this works no need to do a clean install just make a script to CD to the current working directory and you're good.

Example ::

#!/bin/sh
# start everquest
cd ~/.wine/drive_c/Program\ Files/eq_p99 ; taskset -c 0 wine eqgame.exe patchme

Copy and paste that into a file called "eq.sh"

chmod +x eq.sh (wherever it is)

Now in your window manager of choice just create a launcher for it and you're good.

PS: If you're using GNOME or KDE I'd suggest turning off all 'Desktop Effects" - it really affects the performance. I run EQ in XFCE (F15 has a really good version/install of it .. just "yum groupinstall XFCE" to install it and at your login it will be available).

cadiz
10-01-2011, 09:35 PM
As an update, I've tested these RPM packages with a fresh, updated x86_64 Fedora 15 install (new thinkpad T420s with intel integrated video) and verified it works fine. If you have issues be sure to see the caveats section at the bottom.

Zordana
10-05-2011, 03:14 AM
the most awesome thing about this is your computer name: meatsweats :D

username17
11-23-2011, 10:11 PM
Having an issue on Step 5.
After installing all x86_64 RPMs I run wine as my user and it says command not found.

I'm running Fedora 16 x86_64 on a Toshiba Satellite C655D.
I've Tried the x86_64 and noarch RPMs. No change.

I noticed that the prereq RPMs such as Liberation fonts were installed as noarch.
But Pulseaudio-libs was installed as x86_64.

Could the conflict have to do with the mashup of noarch and 64 rpms?

I just removed all Wine related RPMs so that 'rpm -qa | grep wine' has 0 results
Reinstalling from fresh RPMs now.

cadiz
01-10-2012, 04:36 PM
Having an issue on Step 5.
After installing all x86_64 RPMs I run wine as my user and it says command not found.

I'm running Fedora 16 x86_64 on a Toshiba Satellite C655D.
I've Tried the x86_64 and noarch RPMs. No change.

I noticed that the prereq RPMs such as Liberation fonts were installed as noarch.
But Pulseaudio-libs was installed as x86_64.

Could the conflict have to do with the mashup of noarch and 64 rpms?

I just removed all Wine related RPMs so that 'rpm -qa | grep wine' has 0 results
Reinstalling from fresh RPMs now.

You need to also make sure you install the i386 RPMs as well if you're running 64bit. Wine will actually call the 32bit libraries for 32bit games like P99
and you need 32bit RPM's for compatibility reasons anyway.

If it's installed correctly a simple "which wine" should show the right path

(repo@meatsweats) - (15:35) - (~)
-=>>which wine
/usr/bin/wine

Arek
06-12-2012, 04:21 PM
Just an FYI: With wine-1.5.4 (on Linux Mint, which uses the Ubuntu wine packages), you no longer have to patch Wine. You DO have to run in Windowed Mode and turn off Vertex Shaders (VertexShaders=FALSE in eqclient.ini), but it works otherwise. For those of you who play on other servers as well, this also applies to newer clients (like UF).

Just a heads-up to anyone still playing (or wanting to play) on Linux. :-)

--Arek

Pep
06-13-2012, 07:37 AM
Is it Linux Mint 13 Maya? 32 or 64 bit distribution?

Hope your answer helps me and others get a solution working out of the box.

cadiz
06-20-2012, 04:00 PM
Thanks for the update on Linux Mint. Fedora 17 (latest release) version of wine is 1.5.2.
I will try it there and see if it works without patching.

Do you know if the right click 180 degree mouselook bug (http://www.project1999.org/forums/showthread.php?t=67919) is still present?

D3Vena
06-29-2012, 05:37 AM
Thanks for the update on Linux Mint. Fedora 17 (latest release) version of wine is 1.5.2.
I will try it there and see if it works without patching.

Do you know if the right click 180 degree mouselook bug (http://www.project1999.org/forums/showthread.php?t=67919) is still present?

was going to ask if anyone tried it for fedora 17 yet. I'm running latest fedora as well. Have been playing eq1 still on my windows but would like to switch over fully to my linux

D3Vena
06-30-2012, 04:41 AM
Having an issue with the wget paste in step 2. Seems like it may be broken. Will try again later. Too tired right now to even focus.

cadiz
07-01-2012, 08:20 PM
Having an issue with the wget paste in step 2. Seems like it may be broken. Will try again later. Too tired right now to even focus.

Hey D3Vena, I noticed there was an unneeded space in the 64bit-only wget paste line.
Please try it again and it should work for you.

kemendil
07-04-2012, 04:12 PM
Fedora 17 runs Titanium fine for me without messing around with anything other than eqclient.ini

I only had to set

TextureCache=FALSE
VertexShaders=FALSE

To fix the mouselook problem go into winecfg. Under the graphics tab check "Emulate a Virtual Desktop" and make the desktop size the same as your EQ resolution.

Note: You can turn VertexShaders back on in-game (Options->Display->Advanced). You just need to change it back to false before running it again

cadiz
02-02-2013, 09:55 AM
Fedora 17 runs Titanium fine for me without messing around with anything other than eqclient.ini

I only had to set

TextureCache=FALSE
VertexShaders=FALSE

To fix the mouselook problem go into winecfg. Under the graphics tab check "Emulate a Virtual Desktop" and make the desktop size the same as your EQ resolution.

Note: You can turn VertexShaders back on in-game (Options->Display->Advanced). You just need to change it back to false before running it again

Excellent feedback, thanks for posting this. I can verify the same, Fedora 17 and above play eqgame.exe just fine without any need to modify the source or build custom wine RPMs.

cadiz
07-19-2013, 04:13 AM
Hey folks, as an update - Fedora 19 (https://fedoraproject.org/en/get-fedora-options) which is recently released works out of the box for this. It also contains the latest Wine-1.6.x (http://tech.slashdot.org/story/13/07/18/190202/wine-16-released-with-10000-changes)

The only issue I ran into was this error:
fixme:service:scmdatabase_autostart_services Auto-start service L"vpnagent" failed to start: 2
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
libGL error: failed to load driver: i965
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your OpenGL drivers haven't been installed correctly (using GL renderer "Mesa DRI Intel(R) Sandybridge Mobile ", version "1.4 (3.0 Mesa 9.2.0-devel)").
err:d3d:test_arb_vs_offset_limit Failed to create an ARB offset limit test program
err:d3d:test_arb_vs_offset_limit >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from ARB vp offset limit test cleanup @ directx.c / 478
err:d3d:match_fbo_tex_update >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glFramebufferTexture2D @ directx.c / 725
err:d3d:match_fbo_tex_update FBO status 0
-- snip--

To solve this simply install the mesa 32bit library:

yum install mesa-dri-drivers.i686

RadiumOne
09-14-2013, 02:43 AM
Hey I'm on Fedora 19, trying to get the EqEmuLauncher.exe to run so that I can patch and go to the login server etc... This is my first time trying to run Project 1999. The EqEmuLauncher.exe starts up and says that it is looking for servers or something along those lines. Any help would be greatly appreciated. I'm using wine 1.7.x

RadiumOne
09-14-2013, 05:55 AM
Now I am having an error after log in / server select. I select project 1999 server and i get this error

X Error of failed request: GLXUnsupportedPrivateRequest
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 16 (X_GLXVendorPrivate)
Serial number of failed request: 357862
Current serial number in output stream: 357863

cadiz
09-18-2013, 07:34 AM
Hey I'm on Fedora 19, trying to get the EqEmuLauncher.exe to run so that I can patch and go to the login server etc... This is my first time trying to run Project 1999. The EqEmuLauncher.exe starts up and says that it is looking for servers or something along those lines. Any help would be greatly appreciated. I'm using wine 1.7.x

Hey Radium, I've not tested running the EqEmuLauncher - the Linux guide(s) are based around extracting the latest patch file manually, this seems to work well.

Have you tried this without using the launcher?

cadiz
09-18-2013, 07:35 AM
Now I am having an error after log in / server select. I select project 1999 server and i get this error

Just checking, have you obtained the custom DLL file required by wine like below?


cd ~/.wine/drive_c/Program\ Files\everquest
wget http://funcamp.net/w/d3dx9_30.dll

This goes wherever you have your main Everquest directory.

jarinaEQ1
11-11-2013, 02:40 PM
1st run crash at char selection after new copy of installation, updating eqclient.ini :

Same issue i've already encournter under ubuntu : no servers in servers selection list :s

(http://www.project1999.org/forums/showthread.php?t=14125&page=13)

fzzzt
09-05-2014, 09:13 AM
The empty server selection is a strange/complex problem. My friend has an EQ install on Linux Mint 17 XFCE that brings up the servers almost all the time at home, but never at work (a group of us play at work together after hours). However, the rest of us have no problems on Windows at the exact same time...

The problem he's having is his character selection always says he has an outdated spell list, when he doesn't. I've watched him extract the latest one and the files are there, so something else is wrong there...

It's a shame this is so difficult.

mrquincy
12-07-2017, 12:14 PM
Hi fzzzzt,

One problem I experienced on my Debian installation was, apparently, due to long server lists that exceeded the developers expectations. Zaela produced a filter app that forwards only the server entries which begin "Project 1999". I have 100% success connecting after adding this to my EQ startup workflow:

https://github.com/Zaela/p99-login-middlemand

mrquincy
12-07-2017, 12:21 PM
The MGellan guide seemed to indicate that NVIDIA drivers are required to run P99 on Linux distros.

Can someone here confirm that they were able to get a P99 working with intel graphics?

I just purchased a Lenovo T470 to replace my T420s, and unfortunately the new computer uses integrated Intel graphics rather than an NVIDIA GPU...

cadiz
10-23-2018, 12:12 PM
The MGellan guide seemed to indicate that NVIDIA drivers are required to run P99 on Linux distros.

Can someone here confirm that they were able to get a P99 working with intel graphics?

I just purchased a Lenovo T470 to replace my T420s, and unfortunately the new computer uses integrated Intel graphics rather than an NVIDIA GPU...

Yes, intel graphics work just fine. There's a few eqclient.ini settings you'll want to change if things don't look right in this thread but other than that the Intel integrated graphics work fine.

I've played on a number of Lenovo/Thinkpads (currently using an x270).

loramin
10-23-2018, 01:47 PM
I'm on Linux Mint, and I have both an Nvidia card and built-in Intel graphics. I stopped running on the Intel graphics card because it couldn't handle three monitors AND EverQuest without EQ lagging ... but honestly if I'd just gone down to one or two monitors it probably would have been fine.

Seanysean
02-02-2019, 06:07 PM
Hey guys I am new to Fedora 29. I was able to get through the install ok, however I am running into issues running the game without it trying to patch itself. When I run eqgame.exe it will error and say "please run everquest.exe" I am not seeing any option in properties to run it with patchme. If i try to run the wine command in term I just get the unable to find eqgame.exe

cadiz
02-02-2019, 10:02 PM
Hey guys I am new to Fedora 29. I was able to get through the install ok, however I am running into issues running the game without it trying to patch itself. When I run eqgame.exe it will error and say "please run everquest.exe" I am not seeing any option in properties to run it with patchme. If i try to run the wine command in term I just get the unable to find eqgame.exe

Heya, I've been meaning to just write an updated blog post on how to get this working but I think you just need to pass patchme to your wine command you're using to run Everquest via Wine.

You want to run this in a terminal then you can make a script to run it later and associate the equivalent of a Linux desktop shortcut which I'll explain farther down in this post. With Wine you need to manually pass options since you're calling the Windows executable with it.

To test that first go to where eqgame.exe is located, open a terminal and run:

wine eqgame.exe patchme

Here's what I use as a script (this is on Fedora 28) - it cd's into the directory where EQ is installed and runs, adjust accordingly.

#!/bin/sh
# start everquest
cd /home/repo/.wine/drive_c/Program\ Files\ \(x86\)/EverQuest/ ; taskset -c 0 /usr/bin/wine eqgame.exe patchme



You can save this to a file, call it something like start-everquest.sh. Modify it to match the path where your game is installed and use it to launch the game. taskset -c just forces it to run on one CPU core, Everquest is single-threaded and there's known issues on some older multi-core systems so it's more of a precaution.


Further, you can make a .desktop file so the Everquest program is searchable in whatever desktop environment you're using (XFCE here) but I would first get things working via a script or command line before further customizing for convenience. Again, adjust paths and the name of your script accordingly.

Pasting this into a terminal would create the appropriate .desktop entry.

cat > /home/repo/.local/share/applications/everquest.desktop <<EOF
[Desktop Entry]
Name=Everquest
Comment=Everquest
Exec=sh /home/repo/scripts/start-eq.sh
Icon=/home/repo/.wine/drive_c/Program Files/EverQuest/Everquest.ico
Terminal=false
Type=Application
Encoding=UTF-8
Categories=Games;
Path=
EOF

I hope this helps.

xaix1999
01-06-2020, 08:37 PM
wine version 5.0+ rc1-4 are causing eq to lock up at the sound manager

unless you have a cpu with a low base freq
taskset -c 0 will hinder you by only running the game on "core zero"

Voljub
12-04-2021, 12:30 PM
Hello, I'm looking to get back into the game and have since swapped over to Felora Linux (currently version 35, 64bit) while I was away. Are the steps in this guide still current?
I installed the CDs and patch files via Lutris, after a successful install I switched the runner to use the "launch titanium" file. The wine virtual box then displays a black desktop with an Everquest icon in the corner for a few moments, then goes completely black.

loramin
12-04-2021, 01:03 PM
I'd play with the settings in winecfg.

Voljub
12-04-2021, 02:03 PM
I'd play with the settings in winecfg.

I think I got it, under "Runner Options" I switched the Wine version from the default to "lutris-5.7-11-x86_64"
tyty