Some people argue that since Wine introduces an extra layer above the system a Windows application will run slowly. It is true that, in theory, Windows applications that run in Wine or are recompiled with Winelib will not be able to achieve the same performance as native Unix applications.
They admit it's another "layer" between the Windows app (the game) and the O/S.
Even more incriminating...
Now to be frank, performance is not yet a Wine priority. Getting more applications to actually work in Wine is much more important right now.
Case in point, you're probably going to get better performance with a DirectX game on Windows than you will running it in Wine on Linux. How much is debatable, and for many games it's probably going to be minor.
These are words from the Wine developers/community themselves.
On another note, and for me personally, I would still call Wine an emulator. Wine enthusiasts don't like to call it that, and it even states this on their myths page. Purists want to restrict the term "emulator" to just emulating CPUs. The definition of emulation itself, regardless of being applied to computers, still fits the bill for Linux. You're still adding a layer to emulate some components of a Windows environment on a different O/S. With that said I am a full supporter or Linux and Wine even if I'm a pragmatic PC person as well.
I've been trying to install DirectX in Wine, but I haven't been able to successfully do it yet. Assuming I am able to accomplish that, would STO in wine actually use DirectX instead of OpenGL? Is it worth the effort of attempting that?
I've never tried that myself. It would be worth a shot to test and troubleshoot since you're experiencing poor performance with STO in Wine on Linux. After all, as a Linux user, you'll be controlling and testing a lot of your own environment.
Method 1: Easiest possible install by Agrinder
In this method, it was proposed that the user would simply install Wine (the latest stable release for your distribution), acquire winetricks, and then use winetricks to install 'corefonts', 'd3dx9', and 'ie7'.
Result: This works. With a caveat or two. You have an additional blank popup box appear whenever you launch the Star Trek Online executable (my supposition on the source of this is related to the rest of the caveats in this method). In addition, the screen does not update properly for the 'Engage' and 'Patch' button. Further, it doesn't say (outside of the title bar at the top) what the progress of the patching or verification of files is. It leaves the user somewhat blind to the current state of the patching process. If you're looking for the easiest method and don't care about the caveats mentioned, this is probably the one you want.
I have just done this. The game does load, and if I use the mmdevapi override, I even get sound. In fact, I don't have the problems you mention with the launcher. Aside from the fact that my cursor disappears over the buttons, and that I actually have to click "Engage", the launcher works exactly as in Windows.
However, I still have significantly poorer performance than I do in Windows, and I can't even enable some of the higher video settings that I usually use. I'm not concerned with the high video settings, I can live without high quality shadows, etc, but I at least want my performance at mid-range video settings to match the performance I get in Windows. (I can always just boot into Windows to play it, but I'm really trying to avoid that option.)
So, my questions are as follows:
1) Would installing it the more complicated way have any effect on performance, or is it more of a stability thing? Because STO seems perfectly stable the way it is now, it's just performance that I'm concerned about.
2)
Note: Also, as mentioned by other wine contributors in this thread, UseGLSL, VertexShaderMode, and a few other options can more or less affect the stability of your STO install. In some cases, it may prevent you from working at all with the wrong options. When in doubt, try to go with the defaults and stay out of changing them unless you really need to do so. While performance can be a problem if you don't change some options, the bigger issue is that you may not be able to start the game at all (resulting in a Fatal Error screen that is vague and useless).
How exactly do I modify these options? I can't find them in any of the .reg files. Do they exist only when I do the install the long way?
3) I uninstalled wine and reinstalled it to try your two suggestions, but I didn't delete the .win folder nor my install of STO. Would that have affected my results upon following your instructions? That is, is there some benefit to actually nuking everything and starting over, or should I just be focusing on tweaking it from this point on, since the game is in fact working?
They admit it's another "layer" between the Windows app (the game) and the O/S.
Even more incriminating...
Granted, but that isn't the same as saying that performance will ALWAYS suffer. You see, I actually work in a computer shop where we advocate Linux quite heavily. And I have personally seen World of Warcraft, IL2 Sutrmovik, and several other smaller games work better on the Ubuntu side of a dual-boot system than on the Windows side. Now granted, these games aren't as graphic intensive as STO is, but they still prove that you can actually get better performance in Wine than in Windows, at least under some circumstances. So, I know it is conceivable that my STO performance would be more or less the same as in Windows. Therefore, I don't want to just fatalistically accept a significant performance drop.
I've never tried that myself. It would be worth a shot to test and troubleshoot since you're experiencing poor performance with STO in Wine on Linux. After all, as a Linux user, you'll be controlling and testing a lot of your own environment.
So, STO would in fact be using DirectX if I could get it to install? How would you suggest doing that? Winetricks, or some more complicated way?
DirectX is a proprietary library developed by Microsoft (originally developed 3rd party, then gobbled up by Microsoft, but that's beside the point). It isn't being "added" to Wine. People are installing it inside of Wine, and outside of its license. Otherwise they're forced to use OpenGL, which is a "layer" more so than DX that can talk directly to the hardware.
I'm not sure what you meant by "added" to Wine? Are you talking about 3rd party rewrites of the DX library or unlicensed installs of it?
I'm not sure how much trying to argue this with you is going to get through. So, I'll try to be as direct as possible. OpenGL is not a layer of abstraction. It is a different rendering method. It has native support within Linux (or Unix in general) if the vendor of the video card in question provides either open source or proprietary drivers, or the community at large provides their own drivers, to use within X11/xorg's infrastructure. DirectX, as you point out (and I never argued) is not natively supported within any Unix OS - hence the OpenGDI renderer I mentioned.
I think you're reading comments on the WineHQ website out of context - in much the way a search engine grabs for key words. Currently, the issue with rendering is not so much an issue with emulation (as I mentioned and you seemingly disagreed with in another post - which makes no sense as you also seemingly agree. It makes me think you are not sure of the subject matter you're reading). Native rendering support in the versions of OpenGL are generally CPU bound. DirectX isn't - and is an entirely different method.
Future versions of OpenGL (particularly discussions in the OpenGL3+ space) are trying to move in the direction of DirectX without becoming DirectX - in that they will be multi-thread aware and/or possibly take advantage of more GPU scaling and capabilities. This is also mentioned in the Tom's Hardware article I linked earlier in this thread.
At the moment, the issue is not wine itself which you seemingly suggest. It is the lack of native support provided for DirectX. I am neither an enthusiast nor detractor of wine. It is a means to an end, so I don't have an agenda or an axe to grind either way. What I'm telling you is that your interpretation of the facts could use some fine tuning before you begin to educate others. Misinformation is as bad as none.
So, STO would in fact be using DirectX if I could get it to install? How would you suggest doing that? Winetricks, or some more complicated way?
In short, the answer to your question, is no. While you'd get the DLLs and some attempt at interaction with OpenGDI rendering would occur (with regards to DirectX calls), my suggestion would be OpenGL. It would be faster even with the chance for artifacts and issues on the screen (depending on window manager and/or compositing).
What's seemingly frustrating about the whole mess is that it is still recommended (and more stable) to install DirectX libraries (DLLs) through winetricks (package name d3dx9) even if you later change your rendering method to OpenGL. It is understandable that there's some confusion on the matter - but generally by the folks who don't know or don't use it regularly.
In short, the answer to your question, is no. While you'd get the DLLs and some attempt at interaction with OpenGDI rendering would occur (with regards to DirectX calls),
Ahh, that makes much more sense. Thx for the info.
my suggestion would be OpenGL. It would be faster even with the chance for artifacts and issues on the screen (depending on window manager and/or compositing).
Might be a stupid question, but how do I go about doing that?
Might be a stupid question, but how do I go about doing that?
Through winetricks is usually the easiest method.
Mind you, this is from memory. But, it should be as simple as: winetricks rrm=opengl
In the event I am wrong, just start winetricks and scroll down to the bottom page or so. You'll see Rendering Method and one will say gdi, the other will say opengl. Just click the box next to opengl and run that.
Running winetricks without an option opens up a gui box for you to check options off instead of remembering what they are.
If I can bother you for another question, I've come across this post which suggests some performance improvements, but again it mentions adding these to the wine registry, and for some reason, I just can't figure out which file to edit and/or where they go. Any help there?
If I can bother you for another question, I've come across this post which suggests some performance improvements, but again it mentions adding these to the wine registry, and for some reason, I just can't figure out which file to edit and/or where they go. Any help there?
Since editing a registry is usually complicated for folks who aren't comfortable with doing so, much of what you could tweak is also in winetricks - or the most recent version of it anyway. The VertexShaderMode, for example, is in there, also near the bottom. Registry edits and performance tweaks are near the bottom of the gui within winetricks. Packages and software are all before those.
Since editing a registry is usually complicated for folks who aren't comfortable with doing so, much of what you could tweak is also in winetricks - or the most recent version of it anyway.
Ok, cool. Guess I should have looked before asking.
3) I uninstalled wine and reinstalled it to try your two suggestions, but I didn't delete the .win folder nor my install of STO. Would that have affected my results upon following your instructions? That is, is there some benefit to actually nuking everything and starting over, or should I just be focusing on tweaking it from this point on, since the game is in fact working?
I missed this in the thread and I apologize. I think other posts struck me before this one did.
In answer, the software wine is separate from your 'wine bottle' or your wine prefix. There are various names, but they all amount to the same thing. If you called your directory .sto or something similar, then your wine bottle or WINEPREFIX is ".sto"
Nomenclature aside, uninstalling wine won't fix a problem unless the problem is specific to that version of wine. In general, setup issues are generally registry or settings driven within the wine bottle/prefix itself. My suggestion to start on a brand new installation of Star Trek Online without affecting an existing one can take one of two forms:
One (copy existing working environment to play with):
# cd ~
# cp -pdR .sto .sto-temp
# WINEPREFIX=".sto-temp" winetricks
# ... (etc)
# WINEPREFIX=".sto-temp" wine (path to command)
In essence, you can have as many virtual windows environments as you have diskspace to accommodate. And, you can tweak settings until you're happy with the second instance without affecting the first. This is also very useful if you decide to play other games that require other settings.
In essence, you can have as many virtual windows environments as you have diskspace to accommodate. And, you can tweak settings until you're happy with the second instance without affecting the first. This is also very useful if you decide to play other games that require other settings.
Iiiinnnteresting. I have a good amount of free disk space, so I'll have to try that out. Sound pretty handy.
And if you're ever looking for a low-paying job in a run-down computer shop, I can hook you up. :P
Iiiinnnteresting. I have a good amount of free disk space, so I'll have to try that out. Sound pretty handy.
And if you're ever looking for a low-paying job in a run-down computer shop, I can hook you up. :P
I have a nice paying job in a fairly high-tech saavy company now. But, I do appreciate the offer. ;-)
(I'm a Linux Admin (who also works with Solaris and occasionally dabbles with AIX and HP-UX) and a Network Engineer. They realize these days that such a title is pretty unwieldy, so it's now "Senior Systems Engineer")
I've been trying to install DirectX in Wine, but I haven't been able to successfully do it yet. Assuming I am able to accomplish that, would STO in wine actually use DirectX instead of OpenGL? Is it worth the effort of attempting that?
What people seem to be missing here... DirectX is not available on any OS Wine runs on. Even if you install Wine and DirectX, you still do not have DirectX. Almost all graphical DirectX calls are done in Wine with OpenGL, at least by default. Making a game actually run with OpenGL instead of DirectX will run MUCH better, but that is not possible with STO, it will only use DirectX. Wine has its own implementation of DirectX inside it... if you install MS's DirectX you are just replacing Wine's version... this can help sometimes since Wine's version often has problems and much of it is not yet complete.
DirectX is a proprietary library developed by Microsoft (originally developed 3rd party, then gobbled up by Microsoft, but that's beside the point). It isn't being "added" to Wine. People are installing it inside of Wine, and outside of its license. Otherwise they're forced to use OpenGL, which is a "layer" more so than DX that can talk directly to the hardware.
I'm not sure what you meant by "added" to Wine? Are you talking about 3rd party rewrites of the DX library or unlicensed installs of it?
MS DirectX is not being added to Wine. Wine's own "DirectX" is being added to Wine, much if it already being in there. This is made from scratch, not from reverse engineering anything from MS, which is why its so slow to be developed. its not hard to look at how a .dll responds to something, and make your own .dll that responds in the same way. unlike a "real" version of DirectX, it cannot go straight to the GPU to get things done, it has to go to the OS and use OpenGL, and/or other things that can get the job done on the current system. If Wine didn't have directx compatibility.. how do you think STO could run? STO cannot use OpenGL, its coded for DirectX only. and no.. you do not have to install ANYTHING from MS DirectX in Wine to get STO to run.
On another note, and for me personally, I would still call Wine an emulator. Wine enthusiasts don't like to call it that, and it even states this on their myths page. Purists want to restrict the term "emulator" to just emulating CPUs. The definition of emulation itself, regardless of being applied to computers, still fits the bill for Linux. You're still adding a layer to emulate some components of a Windows environment on a different O/S. With that said I am a full supporter or Linux and Wine even if I'm a pragmatic PC person as well.
its not called an emulator because its not emulating.... its basically native implementations of certain libraries and APIs. By your definition running a DX9c game on WIndows with DX10 would be running under emulation... because DX10 is emulating DX9c. Or is it exactly the same but not considered emulating because the same company made both?
What people seem to be missing here... DirectX is not available on any OS Wine runs on.
After reading other posts in this thread, I am given the impression cipher_nemo is trying to be helpful but has no knowledge of the issues involved on any non-Windows platform. Unfortunately, good intentions do not solve a problem or help other folks. It would have been better served to leave the answers to the folks who understand the problem and could answer it (like you and I have). He means well.
After reading other posts in this thread, I am given the impression cipher_nemo is trying to be helpful but has no knowledge of the issues involved on any non-Windows platform. Unfortunately, good intentions do not solve a problem or help other folks. It would have been better served to leave the answers to the folks who understand the problem and could answer it (like you and I have). He means well.
I run Ubuntu and Wine on multiple PCs. I've also installed and used Gentoo, Fedora, and Debian Linux distros as well as FreeBSD and NetBSD BSD distros in the past. Please do not turn an argument into personal attacks.
I have a feeling our disagreement in based in terminology and communication between us instead of anyone being wrong. If you look at the history of OpenGL and DirectX, specifically early history and Microsoft's battle with SGI's over these you'd understand what I mean by the term 'layers'. DirectX was originally the only rendering engine to talk directly to the hardware. OpenGL can now do this as well, but not all things talk directly to the hardware in OpenGL when compared to DirectX (hence your correct comment about utilizing a little more CPU overhead for OpenGL).
You're a very knowledgeable person who has helped quite a bit in this thread and on these forums. But you recently wanted to argue with me about STO taking a performance hit in Wine on Linux. Why bother? If it runs smoothly for you, great. If it doesn't for others (even if they've tweaked settings), then so what? Wine is not a perfect solution for playing DirectX games, and everyone who's tried it can attest to that.
I was able to install both IE7 and STO using PlayonLinux. However when the game tries to load, it tells me it is opening a web page and I need to use Konqueror or some other browser. It won't use IE7, even thogh I set it as the default browser when I was asked (It can't be set in PlayOnLinux).
I was able to get it up and working on Ubuntu 10.10 yesterday using the instructions from this site: http://www.redshirtlinux.com/?p=122. Following those instructions, everything was working except the people weren't visible, the shadows where there, but no textures for the people (myself, bridge officers, other players). I read earlier that users with ATI cards should set HKEY_CURRENT_USER->Software->Wine->Direct3D->UseGLSL to disabled in the registry. As I am using an ATI Radeon HD 5700 Series, I gave this a try and it corrected that issue.
I still get the dialog for "Failed System Specs Check" but it works.
Thank you for reading my site. I have an HD 2600 and with the Catalyst 10.9 drivers I don't have to make the registry mods. You may want to try the next revision of the proprietary ATI drivers. The current version is Catalyst 10.9.
Ubuntu 10.10 comes with the Catalyst 10.9 drivers but it is hard telling what Canonical did you get them to work under the new platform.
I was able to get it up and working on Ubuntu 10.10 yesterday using the instructions from this site: http://www.redshirtlinux.com/?p=122. Following those instructions, everything was working except the people weren't visible, the shadows where there, but no textures for the people (myself, bridge officers, other players). I read earlier that users with ATI cards should set HKEY_CURRENT_USER->Software->Wine->Direct3D->UseGLSL to disabled in the registry. As I am using an ATI Radeon HD 5700 Series, I gave this a try and it corrected that issue.
I still get the dialog for "Failed System Specs Check" but it works.
Ubuntu 10.10 comes with the Catalyst 10.9 drivers but it is hard telling what Canonical did you get them to work under the new platform.
Actually Ubuntu 10.10 comes with a prerelease of Catalyst 10.10 because Catalyst 10.9 doesn't support the X.Org Server 1.9 which is in the new release.
* Kernel module build fix for x86_64 kernels with security fix for CVE-2010-3081
* Generalized kernel module build fix for CVE-2010-3081 to work on RHEL and SLED/SUSE
* Ubuntu 10.10 early-look support (Xserver 1.9 support)
* Updated packaging scripts to support Ubuntu 10.10
* openSUSE 11.3 production support
* Fixed packaging scripts for SLED/SUSE
* Updated packaging scripts
* Checks for available video memory in CCC-LE before allowing to enable memory-intensive features
* Fixed Xserver segfaults and soft hangs when VT switching back to X
* Fixed missing CCC-LE icons in the System-Preferences menu
* Fixed corruption in Xinerama mode
* Fixed CCC-LE Gamma correction applied to wrong displays on openSUSE 11.3
* Fixed text corruption in Steam games
* Added missing maverick symlink in Ubuntu packaging script directory
* Fixed X version detection problems in installer, fixes installation on Fedora 11
I am trying to get STO play on Ubuntu 10.10 since day one of the release no candy so far.
I have used the infamus video of the guy using POL to make it work evry step of the way (And it was hard to see what he was doing on the screen). i also have followed a couple of tutorials.
My luncher acsepts the log in and takes me to the pacher but the pacher dosnt start, ckliking "pach" doesnt work and i cant see the shards or the paching info (The remaining time and size) also the slider doest move. In a nutshel it wont pach
My guess is ie7 isnt installed corectly but i cant use POL helper to get ti associated with the POL prefix because if i click get winetricks it freezes and if i click run winetricks it sais something about a temp file and what ever i click (YES or NO) the Widow closes as if i never pressed "run winetricks"
I am using Ubuntu 10.10
ATI RADEON 4850
and have latest drivers
WIne 1.3.4
I had to use Plugins > POL Helper, then winetricks to install Internet Explorer 8.0 before it would begin patching for me. I used the instructions from http://www.redshirtlinux.com/?p=122 first. I am using Ubuntu 10.10 AMD64 Desktop on an AMD Athlon X2 2.1GHz + ATI Radeon HD 2600 XT 256MB PCIe - I will update once patching is complete as to what tweaks might be necessary to get the 3d rendering to work correctly.
I am trying to get STO play on Ubuntu 10.10 since day one of the release no candy so far.
I have used the infamus video of the guy using POL to make it work evry step of the way (And it was hard to see what he was doing on the screen). i also have followed a couple of tutorials.
My luncher acsepts the log in and takes me to the pacher but the pacher dosnt start, ckliking "pach" doesnt work and i cant see the shards or the paching info (The remaining time and size) also the slider doest move. In a nutshel it wont pach
My guess is ie7 isnt installed corectly but i cant use POL helper to get ti associated with the POL prefix because if i click get winetricks it freezes and if i click run winetricks it sais something about a temp file and what ever i click (YES or NO) the Widow closes as if i never pressed "run winetricks"
I am using Ubuntu 10.10
ATI RADEON 4850
and have latest drivers
WIne 1.3.4
Ok.. While that game is functioning on my computer (Ubuntu 10.10 on an HP G60 Notebook) the only issue Tend to have is with the Patcher... for some reason the graphics never load properly.. and usually have to load it 9 to 12 times to get one that will give me the failed image areas to actually select shard or click proceed. My IE 7 install also stalls when its loaded and never loads pages... Im assuming this is the reason... Any ideas on a work around?
Hello, im trying to get STO working on my Ubuntu, but it resists like the borgs. I managed to patch the game, but after that it usually hangs in the loading screen. I once managed to get to the login screen, but then it didnt access my characters.
Any idea what may be causing it ?
Edit:
Ok i solved this part, i can now log in the game. I even managed to get sound working. But now everytime i change zone the game and my whole comp is frozen and i have to do a hard restart.
Works well under Gentoo and wine-1.3.10 without any game patch.. my sound was dead but tweaking wine fixed the problem
dll overrides "mmdevapi disabled"
Comments
They admit it's another "layer" between the Windows app (the game) and the O/S.
Even more incriminating...
All from: http://www.winehq.org/myths
Case in point, you're probably going to get better performance with a DirectX game on Windows than you will running it in Wine on Linux. How much is debatable, and for many games it's probably going to be minor.
These are words from the Wine developers/community themselves.
On another note, and for me personally, I would still call Wine an emulator. Wine enthusiasts don't like to call it that, and it even states this on their myths page. Purists want to restrict the term "emulator" to just emulating CPUs. The definition of emulation itself, regardless of being applied to computers, still fits the bill for Linux. You're still adding a layer to emulate some components of a Windows environment on a different O/S. With that said I am a full supporter or Linux and Wine even if I'm a pragmatic PC person as well.
I've never tried that myself. It would be worth a shot to test and troubleshoot since you're experiencing poor performance with STO in Wine on Linux. After all, as a Linux user, you'll be controlling and testing a lot of your own environment.
However, I still have significantly poorer performance than I do in Windows, and I can't even enable some of the higher video settings that I usually use. I'm not concerned with the high video settings, I can live without high quality shadows, etc, but I at least want my performance at mid-range video settings to match the performance I get in Windows. (I can always just boot into Windows to play it, but I'm really trying to avoid that option.)
So, my questions are as follows:
1) Would installing it the more complicated way have any effect on performance, or is it more of a stability thing? Because STO seems perfectly stable the way it is now, it's just performance that I'm concerned about.
2) How exactly do I modify these options? I can't find them in any of the .reg files. Do they exist only when I do the install the long way?
3) I uninstalled wine and reinstalled it to try your two suggestions, but I didn't delete the .win folder nor my install of STO. Would that have affected my results upon following your instructions? That is, is there some benefit to actually nuking everything and starting over, or should I just be focusing on tweaking it from this point on, since the game is in fact working?
Again, thanks for your help.
So, STO would in fact be using DirectX if I could get it to install? How would you suggest doing that? Winetricks, or some more complicated way?
I'm not sure how much trying to argue this with you is going to get through. So, I'll try to be as direct as possible. OpenGL is not a layer of abstraction. It is a different rendering method. It has native support within Linux (or Unix in general) if the vendor of the video card in question provides either open source or proprietary drivers, or the community at large provides their own drivers, to use within X11/xorg's infrastructure. DirectX, as you point out (and I never argued) is not natively supported within any Unix OS - hence the OpenGDI renderer I mentioned.
I think you're reading comments on the WineHQ website out of context - in much the way a search engine grabs for key words. Currently, the issue with rendering is not so much an issue with emulation (as I mentioned and you seemingly disagreed with in another post - which makes no sense as you also seemingly agree. It makes me think you are not sure of the subject matter you're reading). Native rendering support in the versions of OpenGL are generally CPU bound. DirectX isn't - and is an entirely different method.
Future versions of OpenGL (particularly discussions in the OpenGL3+ space) are trying to move in the direction of DirectX without becoming DirectX - in that they will be multi-thread aware and/or possibly take advantage of more GPU scaling and capabilities. This is also mentioned in the Tom's Hardware article I linked earlier in this thread.
At the moment, the issue is not wine itself which you seemingly suggest. It is the lack of native support provided for DirectX. I am neither an enthusiast nor detractor of wine. It is a means to an end, so I don't have an agenda or an axe to grind either way. What I'm telling you is that your interpretation of the facts could use some fine tuning before you begin to educate others. Misinformation is as bad as none.
In short, the answer to your question, is no. While you'd get the DLLs and some attempt at interaction with OpenGDI rendering would occur (with regards to DirectX calls), my suggestion would be OpenGL. It would be faster even with the chance for artifacts and issues on the screen (depending on window manager and/or compositing).
What's seemingly frustrating about the whole mess is that it is still recommended (and more stable) to install DirectX libraries (DLLs) through winetricks (package name d3dx9) even if you later change your rendering method to OpenGL. It is understandable that there's some confusion on the matter - but generally by the folks who don't know or don't use it regularly.
Might be a stupid question, but how do I go about doing that?
Through winetricks is usually the easiest method.
Mind you, this is from memory. But, it should be as simple as: winetricks rrm=opengl
In the event I am wrong, just start winetricks and scroll down to the bottom page or so. You'll see Rendering Method and one will say gdi, the other will say opengl. Just click the box next to opengl and run that.
Running winetricks without an option opens up a gui box for you to check options off instead of remembering what they are.
If I can bother you for another question, I've come across this post which suggests some performance improvements, but again it mentions adding these to the wine registry, and for some reason, I just can't figure out which file to edit and/or where they go. Any help there?
Since editing a registry is usually complicated for folks who aren't comfortable with doing so, much of what you could tweak is also in winetricks - or the most recent version of it anyway. The VertexShaderMode, for example, is in there, also near the bottom. Registry edits and performance tweaks are near the bottom of the gui within winetricks. Packages and software are all before those.
Thanks again.
No problem. My preference is always that people ask. A question can be answered. An incorrect assumption is often hardest to dispel.
I missed this in the thread and I apologize. I think other posts struck me before this one did.
In answer, the software wine is separate from your 'wine bottle' or your wine prefix. There are various names, but they all amount to the same thing. If you called your directory .sto or something similar, then your wine bottle or WINEPREFIX is ".sto"
Nomenclature aside, uninstalling wine won't fix a problem unless the problem is specific to that version of wine. In general, setup issues are generally registry or settings driven within the wine bottle/prefix itself. My suggestion to start on a brand new installation of Star Trek Online without affecting an existing one can take one of two forms:
One (copy existing working environment to play with):
# cd ~
# cp -pdR .sto .sto-temp
# WINEPREFIX=".sto-temp" winetricks
# ... (etc)
# WINEPREFIX=".sto-temp" wine (path to command)
Two (create a new environment to play with):
# cd ~
# WINEPREFIX=".sto-new" winetricks
# ...
# WINEPREFIX=".sto-new" wine
In essence, you can have as many virtual windows environments as you have diskspace to accommodate. And, you can tweak settings until you're happy with the second instance without affecting the first. This is also very useful if you decide to play other games that require other settings.
And if you're ever looking for a low-paying job in a run-down computer shop, I can hook you up. :P
I have a nice paying job in a fairly high-tech saavy company now. But, I do appreciate the offer. ;-)
(I'm a Linux Admin (who also works with Solaris and occasionally dabbles with AIX and HP-UX) and a Network Engineer. They realize these days that such a title is pretty unwieldy, so it's now "Senior Systems Engineer")
What people seem to be missing here... DirectX is not available on any OS Wine runs on. Even if you install Wine and DirectX, you still do not have DirectX. Almost all graphical DirectX calls are done in Wine with OpenGL, at least by default. Making a game actually run with OpenGL instead of DirectX will run MUCH better, but that is not possible with STO, it will only use DirectX. Wine has its own implementation of DirectX inside it... if you install MS's DirectX you are just replacing Wine's version... this can help sometimes since Wine's version often has problems and much of it is not yet complete.
MS DirectX is not being added to Wine. Wine's own "DirectX" is being added to Wine, much if it already being in there. This is made from scratch, not from reverse engineering anything from MS, which is why its so slow to be developed. its not hard to look at how a .dll responds to something, and make your own .dll that responds in the same way. unlike a "real" version of DirectX, it cannot go straight to the GPU to get things done, it has to go to the OS and use OpenGL, and/or other things that can get the job done on the current system. If Wine didn't have directx compatibility.. how do you think STO could run? STO cannot use OpenGL, its coded for DirectX only. and no.. you do not have to install ANYTHING from MS DirectX in Wine to get STO to run.
its not called an emulator because its not emulating.... its basically native implementations of certain libraries and APIs. By your definition running a DX9c game on WIndows with DX10 would be running under emulation... because DX10 is emulating DX9c. Or is it exactly the same but not considered emulating because the same company made both?
After reading other posts in this thread, I am given the impression cipher_nemo is trying to be helpful but has no knowledge of the issues involved on any non-Windows platform. Unfortunately, good intentions do not solve a problem or help other folks. It would have been better served to leave the answers to the folks who understand the problem and could answer it (like you and I have). He means well.
I run Ubuntu and Wine on multiple PCs. I've also installed and used Gentoo, Fedora, and Debian Linux distros as well as FreeBSD and NetBSD BSD distros in the past. Please do not turn an argument into personal attacks.
I have a feeling our disagreement in based in terminology and communication between us instead of anyone being wrong. If you look at the history of OpenGL and DirectX, specifically early history and Microsoft's battle with SGI's over these you'd understand what I mean by the term 'layers'. DirectX was originally the only rendering engine to talk directly to the hardware. OpenGL can now do this as well, but not all things talk directly to the hardware in OpenGL when compared to DirectX (hence your correct comment about utilizing a little more CPU overhead for OpenGL).
You're a very knowledgeable person who has helped quite a bit in this thread and on these forums. But you recently wanted to argue with me about STO taking a performance hit in Wine on Linux. Why bother? If it runs smoothly for you, great. If it doesn't for others (even if they've tweaked settings), then so what? Wine is not a perfect solution for playing DirectX games, and everyone who's tried it can attest to that.
I was able to install both IE7 and STO using PlayonLinux. However when the game tries to load, it tells me it is opening a web page and I need to use Konqueror or some other browser. It won't use IE7, even thogh I set it as the default browser when I was asked (It can't be set in PlayOnLinux).
I still get the dialog for "Failed System Specs Check" but it works.
Thank you for reading my site. I have an HD 2600 and with the Catalyst 10.9 drivers I don't have to make the registry mods. You may want to try the next revision of the proprietary ATI drivers. The current version is Catalyst 10.9.
Ubuntu 10.10 comes with the Catalyst 10.9 drivers but it is hard telling what Canonical did you get them to work under the new platform.
Thanks,
Captain Benjamin Ward
aka Adam G. Ward
http://www.redshirtlinux.com
Actually Ubuntu 10.10 comes with a prerelease of Catalyst 10.10 because Catalyst 10.9 doesn't support the X.Org Server 1.9 which is in the new release.
I am trying to get STO play on Ubuntu 10.10 since day one of the release no candy so far.
I have used the infamus video of the guy using POL to make it work evry step of the way (And it was hard to see what he was doing on the screen). i also have followed a couple of tutorials.
My luncher acsepts the log in and takes me to the pacher but the pacher dosnt start, ckliking "pach" doesnt work and i cant see the shards or the paching info (The remaining time and size) also the slider doest move. In a nutshel it wont pach
My guess is ie7 isnt installed corectly but i cant use POL helper to get ti associated with the POL prefix because if i click get winetricks it freezes and if i click run winetricks it sais something about a temp file and what ever i click (YES or NO) the Widow closes as if i never pressed "run winetricks"
I am using Ubuntu 10.10
ATI RADEON 4850
and have latest drivers
WIne 1.3.4
Hey I would like to play WOW via Linux. How do you do that?
Any idea what may be causing it ?
Edit:
Ok i solved this part, i can now log in the game. I even managed to get sound working. But now everytime i change zone the game and my whole comp is frozen and i have to do a hard restart.
Anyone experienced/solved it ?
dll overrides "mmdevapi disabled"
Everything in the launcher works fine for me...
heres my winetricks.. http://wiki.winehq.org/winetricks
winetricks comctl32 wmp10 wininet winhttp windowscodecs vlc vcrun2005 vcrun2008 vcrun2010 vcrun6 vcrun6sp6 vb6run richtx32 msxml6 msscript mspaint msi2 mdac28 ie7 hosts gdiplus flash colorprofile comctl32 controlpad corefonts crypt32 d3dx9 divx fontfix
you may not need some of those but for me i have other apps that rely on them
Good luck
edit: seems to work better in wine under vista application preferences..