Game wouldn't start for me to, but after i once started it via POL with wine 1.6.2 it start fine with my system wine (1.9.20-staging) but now i end up with all this nice red crosses and a lot of vertex shader and pixel shader errors. Tried some directx overwrites but nothing helped :-(
Game wouldn't start for me to, but after i once started it via POL with wine 1.6.2 it start fine with my system wine (1.9.20-staging) but now i end up with all this nice red crosses and a lot of vertex shader and pixel shader errors. Tried some directx overwrites but nothing helped :-(
Having ran into the exact same problem I continued my tests and recompiled Wine 1.9.20 with OSMesa (--with-osmesa) support and now the missing textures are back. DX11 still results in a crash but DX9Ex now seems to work as before the big patch (it's late so I won't actually play the game until tomorrow). Those of you who don't have the knowledge to recompile Wine yourselves would have to ask the maintainer of your distribution if OSMesa support can be added.
EDIT: Just noticed that if I increase render quality to medium (I've been running on low) the red crosses and shader compilation errors return so OSMesa might not be the only magic needed to make this work.
EDIT2: I'm beginning to believe that OSMesa is unrelated and that running the game with Wine 1.6 allowed the game to compile the shaders necessary for my current graphics settings so that 1.9.20 could use them. I'd have to reinstall 1.6 tomorrow and switch to higher graphics settings to verify that hypothesis.
Further testing today confirms that OSMesa support was a blind track. I apologize for the noise. I once again reinstalled Wine 1.6.2, went to areas with previously missing textures and pulled the quality slider back and forth a couple of times. Then I reinstalled Wine 1.9.20 and went to the same places and it was much better. There are still a few textures missing running it with the highest render quality but the game is playable again. Since there's no CSMT patches for 1.6 I prefer to stay with the 1.9 version for performance reasons.
FYI everyone:
After patch 10/17/16 i loaded the game with Wine Engine 1.6.2 and everything looked/worked fine.
On a whim I tried using the Wine 1.9.20 Engine and all is good.
I can confirm that, under linux, wine 1.6.2 worked for me too. Thx!
I am trying to update Wineskin 1.6 and I don't see a 1.9.10 option. It looks like there is a new version called 2.6.2 Is that the version I need to download? Hope you you update from 1.6 to 2.6.2?
It's also my experience that Wine Engine 1.6.2 will compile the things necessary to get rid of the graphical red X 'errors'.
I spent a day using the 1.6.2 Engine and hit just about everything in game while playing.
I have switched back to Wine Engine 1.9.20 to continue playing and red 'X' are gone.
Well as I said I would I tried it again after todays patch, still doesn't work.
I'm tired of trying to find work-arounds or just plain hoping that someone else will be kind enough to share one.
I'm tired of half-a$$ed, unfinished, abandoned or just flat out ignored content and gameplay.
I mean how badly do you have to scr3w up the graphics code for this game that barely 15 minutes of run time will make my cooling fans scream and the screen be too hot to even touch?
BTW that's with all the graphics settings on low or off.
I can play WoW, with maxed graphics settings, for over 15 - 18 HOURS without the cooling fans being audible and the screen lukewarm.
So I'm done and finished.
Goodbye fair ladies of spain... only joking
For reals -
Live long and Prosper
Qa'pla!
Fly safe people
And finally... may whatever Gods you believe in stand between you and harm during your travels.
Edit: Problem seems solved when using Wine 1.6 (reportedly everything from 1.9.15 or below is fine.)
I had to go back to 1.6.2 after the Nov 3 patch as well. Too many texture issues (red crosses) on 1.9.x that seemed to be ok for the most part after using 1.6 to get up and running after the Oct 25 patch.
After a patch I run the game first through 1.6.2, and then switch to 1.9.20-staging.
I managed to make my ships look right by loading them on the loading screen with 1.6.2, and now they're fine on 1.9.20. I can't do that with any other crosses in other places, because if I try to log into a character on 1.6.2, I crash immediately after logging in even to sector space. Not enough video memory. Wine 1.6 and 1.6.2 have terrible handle of video memory resources, so I'm stuck with crosses, unless they fix that.
There was a suggestion on Reddit by Tumerboy (Art Department) to do a Force Verify and Safe mode, and it seems to work for at least one PlayOnLinux user.
On my WINE 1.7.40 install, which has no red x issues and loads fine (though running DX9), I get the message 'Tessellation not supported. skipping domain shader compilation.' while the splash screen is up. I wonder if the 'domain shader compilation' might be the issue (partial implementation?) and going 1.6 makes it skip that for you all, and then 1.9 is peachy without those. Just a thought if Force Verify doesn't work.
When loading the game or while playing? A fair number of folks are playing on Mac right now, myself included. A crash while loading can usually be worked around by starting in safe mode. You will get the odd crash while playing. There's also another thread on Macs in the support section here.
I can confirm that you can get around the problem by copying the missing dll
Go the live server directory - ~/.wine/drive_c/Program Files/Cryptic Studios/Star Trek Online/Live
copy D3DCompiler_42.dll to D3DCompiler_47.dll and restar the game and it runs.
cd ~/.wine/drive_c/Program Files/Cryptic Studios/Star Trek Online/Live
cp D3DCompiler_42.dll D3DCompiler_47.dll
Does the lightning system work for you guys? Any idea how to make it work on wine?
Im running on 1.6 engine.
You need the 1.9 series of WIne for DX11 support. As of version 1.9.22, 13% of the DX11 APIs are implemented but several games are reported to work. https://www.winehq.org/winapi_stats
Personally I only get crashes when trying DX11 on STO.
I can confirm that you can get around the problem by copying the missing dll
Go the live server directory - ~/.wine/drive_c/Program Files/Cryptic Studios/Star Trek Online/Live
copy D3DCompiler_42.dll to D3DCompiler_47.dll and restar the game and it runs.
cd ~/.wine/drive_c/Program Files/Cryptic Studios/Star Trek Online/Live
cp D3DCompiler_42.dll D3DCompiler_47.dll
^This^ is a great find to help explain the Red-X problem. I went one step further and got an actual D3DCompiler_47.dll and installed it into the same location. Started up using Engine 1.6.2 and things look good.
My wife also got a real _47 version of the file and installed it on her Mac. It seemed to work okay, and may even have fixed the *long* wait at the splash screen when starting up the game after Cryptic has put out a new patch.
> @jansall said: > I can confirm that you can get around the problem by copying the missing dll > Go the live server directory - ~/.wine/drive_c/Program Files/Cryptic Studios/Star Trek Online/Live > copy D3DCompiler_42.dll to D3DCompiler_47.dll and restar the game and it runs. cd ~/.wine/drive_c/Program Files/Cryptic Studios/Star Trek Online/Live cp D3DCompiler_42.dll D3DCompiler_47.dll
It works fine. Thank you very much. I run STO on PlayOnLinux (with Wine 1.9.24) it still works with 1.9.20-staging and 23-staging I can't notice any red crosses or to be precise any pixel shader compilation failure.
With the low costs of win10 laptops wouldn't it be easier to just go to walmart or best buy and buy a cheap a$$ win10 laptop just for PC gaming. I mean really you can pick up a system for under 200 bucks these days that will run STO with no problems. Seriously no need to mess around with third party software and settings or editing directories you just turn it on install arc then click the icon to play and you are running STO with no drama. Just putting this out as an easy solution.
Wow just go to walmart buy a cheap a$$ win10 laptop just for gaming. I mean really you can pick up a system for under 200 bucks these days that will run STO with no problems. I bet your cell phone costs more for goodness sake. Seriously it's not rocket science no need to mess around with third party software and settings or editing directories you just turn it on install arc then click the icon to play and gee whiz you are running STO with no drama.
Love you think people have a disposable income. Also there are some people who do not like windows and or prefer to play on Linux. A laptop that cost 200$ may run STO but not well not well at all.
JJ Connie > TOS Connie
Lag denied your Heal
What happened to my Halon consoles
Poni?
Wow just go to walmart buy a cheap a$$ win10 laptop just for gaming. I mean really you can pick up a system for under 200 bucks these days that will run STO with no problems. I bet your cell phone costs more for goodness sake. Seriously it's not rocket science no need to mess around with third party software and settings or editing directories you just turn it on install arc then click the icon to play and gee whiz you are running STO with no drama.
Love you think people have a disposable income. Also there are some people who do not like windows and or prefer to play on Linux. A laptop that cost 200$ may run STO but not well not well at all.
Yet these same folks put up with having to edit directories and jump through hoops and then grumble when they can't play it anymore that is what I don't get. Ok you don't like Windows I get it but asfik you can dual boot a PC (been a while since I had to do it). And well you talk about disposable income I will put dollars to doughnuts that a lot of the folks grumbling rush out when Apple releases a new phone just for the sake of having it and ignore the cost. Like I said I'm just putting that out there as a solution. I am glad that there is a community of folks that do take the time and efffort to force another OS into running a Win based piece of software but there are times that it is just as easy if not easier to pick up a system to use for software dedicated to a specfic OS. Heck there are folks who have several diffetent devices to game from Smartphones to PS4's and Nintendo DS's for different games this isn't much different to be honest. Depends on what you call well by the way. Interesting article here about the human eye and gaming and film. 100fps.com goes into the whole framrate deal.
STO is the last app that I put up with not having a native mac or linux client. With their engine on PS4 I think it would be the best time to port it to macos and linux.
Anyways sometimes STO frustrates me so much that I just load up torchlight2 and play that instead heh. It has native linux client.
wine 2.0rc5 (downloaded from POL, i.e. not running with the wine version installed by POL and wine set to windows 8) works with directx 11 in my hands (nvidia gtx960m), providing the *42.dll compiler is copied to 47.dll as described above.
It's sluggish, close zoom on ships shows hashed structures, but it is definitely playable.
Comments
EDIT: Just noticed that if I increase render quality to medium (I've been running on low) the red crosses and shader compilation errors return so OSMesa might not be the only magic needed to make this work.
EDIT2: I'm beginning to believe that OSMesa is unrelated and that running the game with Wine 1.6 allowed the game to compile the shaders necessary for my current graphics settings so that 1.9.20 could use them. I'd have to reinstall 1.6 tomorrow and switch to higher graphics settings to verify that hypothesis.
"-Grind is good!" --Gordon Geko
Accolades checklist: https://bit.ly/FLUFFYS
"-Grind is good!" --Gordon Geko
Accolades checklist: https://bit.ly/FLUFFYS
I can confirm that, under linux, wine 1.6.2 worked for me too. Thx!
@protoneous has a guide in this thread.
"-Grind is good!" --Gordon Geko
Accolades checklist: https://bit.ly/FLUFFYS
I spent a day using the 1.6.2 Engine and hit just about everything in game while playing.
I have switched back to Wine Engine 1.9.20 to continue playing and red 'X' are gone.
I'm tired of trying to find work-arounds or just plain hoping that someone else will be kind enough to share one.
I'm tired of half-a$$ed, unfinished, abandoned or just flat out ignored content and gameplay.
I mean how badly do you have to scr3w up the graphics code for this game that barely 15 minutes of run time will make my cooling fans scream and the screen be too hot to even touch?
BTW that's with all the graphics settings on low or off.
I can play WoW, with maxed graphics settings, for over 15 - 18 HOURS without the cooling fans being audible and the screen lukewarm.
So I'm done and finished.
Goodbye fair ladies of spain... only joking
For reals -
Live long and Prosper
Qa'pla!
Fly safe people
And finally... may whatever Gods you believe in stand between you and harm during your travels.
See you guys around some where
https://i.ytimg.com/vi/5pOxlazS3zs/maxresdefault.jpg
I managed to make my ships look right by loading them on the loading screen with 1.6.2, and now they're fine on 1.9.20. I can't do that with any other crosses in other places, because if I try to log into a character on 1.6.2, I crash immediately after logging in even to sector space. Not enough video memory. Wine 1.6 and 1.6.2 have terrible handle of video memory resources, so I'm stuck with crosses, unless they fix that.
On my WINE 1.7.40 install, which has no red x issues and loads fine (though running DX9), I get the message 'Tessellation not supported. skipping domain shader compilation.' while the splash screen is up. I wonder if the 'domain shader compilation' might be the issue (partial implementation?) and going 1.6 makes it skip that for you all, and then 1.9 is peachy without those. Just a thought if Force Verify doesn't work.
Go the live server directory - ~/.wine/drive_c/Program Files/Cryptic Studios/Star Trek Online/Live
copy D3DCompiler_42.dll to D3DCompiler_47.dll and restar the game and it runs.
Im running on 1.6 engine.
You need the 1.9 series of WIne for DX11 support. As of version 1.9.22, 13% of the DX11 APIs are implemented but several games are reported to work. https://www.winehq.org/winapi_stats
Personally I only get crashes when trying DX11 on STO.
"-Grind is good!" --Gordon Geko
Accolades checklist: https://bit.ly/FLUFFYS
^This^ is a great find to help explain the Red-X problem. I went one step further and got an actual D3DCompiler_47.dll and installed it into the same location. Started up using Engine 1.6.2 and things look good.
My wife also got a real _47 version of the file and installed it on her Mac. It seemed to work okay, and may even have fixed the *long* wait at the splash screen when starting up the game after Cryptic has put out a new patch.
> I can confirm that you can get around the problem by copying the missing dll
> Go the live server directory - ~/.wine/drive_c/Program Files/Cryptic Studios/Star Trek Online/Live
> copy D3DCompiler_42.dll to D3DCompiler_47.dll and restar the game and it runs. cd ~/.wine/drive_c/Program Files/Cryptic Studios/Star Trek Online/Live cp D3DCompiler_42.dll D3DCompiler_47.dll
It works fine. Thank you very much.
I run STO on PlayOnLinux (with Wine 1.9.24) it still works with 1.9.20-staging and 23-staging
I can't notice any red crosses or to be precise any pixel shader compilation failure.
Love you think people have a disposable income. Also there are some people who do not like windows and or prefer to play on Linux. A laptop that cost 200$ may run STO but not well not well at all.
Lag denied your Heal
What happened to my Halon consoles
Poni?
Yet these same folks put up with having to edit directories and jump through hoops and then grumble when they can't play it anymore that is what I don't get. Ok you don't like Windows I get it but asfik you can dual boot a PC (been a while since I had to do it). And well you talk about disposable income I will put dollars to doughnuts that a lot of the folks grumbling rush out when Apple releases a new phone just for the sake of having it and ignore the cost. Like I said I'm just putting that out there as a solution. I am glad that there is a community of folks that do take the time and efffort to force another OS into running a Win based piece of software but there are times that it is just as easy if not easier to pick up a system to use for software dedicated to a specfic OS. Heck there are folks who have several diffetent devices to game from Smartphones to PS4's and Nintendo DS's for different games this isn't much different to be honest. Depends on what you call well by the way. Interesting article here about the human eye and gaming and film. 100fps.com goes into the whole framrate deal.
Anyways sometimes STO frustrates me so much that I just load up torchlight2 and play that instead heh. It has native linux client.
It's sluggish, close zoom on ships shows hashed structures, but it is definitely playable.