The forum

After DJYoshaBYD updated the install script on Terraria. I am still having issues with Terraria. It installs fine and I can run the game but when I press any key it freezes and crashes throwing a log file from WINE. I have attached both POL and WINE log files, any help will be appreciated.

Wine log filehttp://pastebin.com/mkGKp4T5
POL log file http://pastebin.com/neCU5zEW

System Specs
Brand Toshiba L650D
OS Ubuntu 12.04 LTS x64 All updates installed
HDD 640 GB
Mem Intel® Core™ i5 CPU M 460 @ 2.53GHz × 4
Graphics ATI Radeon 5650 with Proprietry AMD drivers installed.


SOLVED. USED WINE 1.7.8 and Disabled gameoverlayrenderer thanks everyone

Edited by Wlowe

Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Hmm. That is not the Steam issue, but something is for sure not working right. I noticed that all throughout the logs were .NET things being installed. These should not be installed, because this version comes with wine-mono.

'Install Terraria in Steam. Run the Terraria when Steam is installed the game. Steam install xna framework the game. Close the Steam so that the installer can continue.')" "$TITLE"

This message pops up during the install. Are you following the instructions to the fullest?

There is a chance, because of what has happened, that a patch may need to be written to support this game through Wine/Steam, or perhaps more testing on the script needs to be done to see if we can get it working correctly. Im not sure, considering it was still testing before, and now through Steam its breaking. Although, I cant say for sure that its Steam doing it, simply because we cant test the CD version.

Also, Are you using regular Ubuntu with Unity? I have seen lots of graphics problems like this through Unity.

Can you install another DE to test it? Something light like XFCE. You can simply reboot and when you log in, it will let you log into an XFCE session, and then try to reinstall and run again. I just want to rule that out, as Canonical is doing some, well, interesting things with their graphics stack on Ubuntu. lol

Just like I thought, almost for sure .NET 4 being installed by the XNA dependency, and its conflicting with wine-mono, which is installed by default.

Wait 10 minutes, uninstall Terr, and refresh, and reinstall. Im going to pull XNA out real quick, and see if wine-mono will take care of it.

Also, make sure you are doing all instructions that are presented, such as:

If the game crashes at startup, open a terminal and type:
echo 0|sudo tee /proc/sys/kernel/yama/ptrace_scope

This is known to fix crashing issues with .NET. Still would like to see how it works without XNA real quick.

I have and am using Unity with Ubuntu I just got back for lunch will reinstall clean. Will reply back. Thanks

For sure. I may not answer tonight (Im in PST), but if I dont petch might, and I will see it when I log back in. Hope it works. I know this whole steam/wine thing has been a pain for everyone lately.

Hey I have a Collectors edition install but it its 1.1.2

Alright, I will try your suggestions when I have time, hopefully today (AEST Australia)

Check this out:

http://www.winehq.org/announce/1.6.2

New stable release, fixing this bug:

32658: Certain games on Steam crash on start in xinput1_3 (in-game overlay enabled)

http://bugs.winehq.org/show_bug.cgi?id=32658

Ill bet this may yield something nice, as well. It will probably get built automatically tonight.

That is nice but wouldn't that fix be added in the 1.7 Dev versions?

Steam is probably going insane seeing all of my requests to steam guard

It depends. Im not sure. I havent gone through all of the changelogs yet.

Just reinstalled, the game doesn't even run now. My lunch break is over though and it about 6pm over there for you guys. I'll let you off. When I come back later tonight I'll try to figure out something. Also do you guys want 1.1.2 CE installs?

Its just me. Everyone else is in France. lol. Im a volunteer here and freelancer as a profession. hahaha. Technically, Im always off, except when I work. :)

Basically, Steam is running fine. The game itself crashes. We need to do one of 2 things, whichever works better.

Since Terr requires XNA, and XNA requires .NET 4.0:

1 - test a stand-alone XNA Framework install in the script, and let it install, without running the POL script, which installs .NET 4 as a requirement. The reason this "should" work, is that wine-mono is to the point to where it should be like, almost fully compatible with .NET 4. WineHQ actually recommends use of wine-mono, or else use the Windows Mono Framework in Wine, and lastly, use .NET through wine.

2 - adjust the script so that, before XNA gets installed, wine-mono is not downloaded/installed. What is bad about this, is when the virtual drive is created for these newer versions on Wine is that it automatically installs wine-mono. Normally, this isnt bad, but REMOVING it once its installed will likely cause issues. If wine-mono is not installed or is removed, then the original script should work fine by just adding statements to avoid or remove wine-mono.

Unfortunately, I dont even own the game, so I cannot test, but for sure, let us know what you find and we can figure something out.

During the install DXSetup.exe fails. I have heard of Mono but not a wine versions of mono and since I am sort of new to Ubuntu. I would try everything I can think of to feed back to this. This failed most likely to a Steam update.

Mono is an open-source implementation of .NET. .NET is a proprietary development framework by Mircrosoft, and of course, only for windows. Unfortunately, it gets used a LOT for game development, and the rest of us suffer. haha. Not speculation, but fact.

Essentially, Mono is a VERY good attempt of what .NET should be; a cross-platform language based on C#. Not saying its a bad language, but it causes a LOT of the problems with games that need it.

Mono runs on Windows, but also has a native *NIX port. So, wine-mono is specifically implemented into Wine, and Wine expects to use this, and not .NET after Wine version 1.5.6.

.NET and Mono directly conflict with each other in Wine, so they cannot be present on the same virtual drive (known to wine as a WINEPREFIX). There are a TON of files, dll's, and registry entries involved... it gets hectic. When you have any version of Wine higher than 1.5.6, wine-mono will be installed automatically, when needed. This is preferred. If that doesnt work, you can always try the Windows version of Mono, then lastly, .NET.

Yeah. I repeated myself to bring it back into context. Most of the time, you dont need to worry about it, as I have found wine-mono to be quite stable recently. That being said, this is one of those times where .NET is breaking the XNA Framework, which requires .NET, due to conflicting with wine-mono. This is what I think it is, but I may be incorrect. Im almost sure its the issue.

Essentially, one of those guys gots to go. Either .NET or wine-mono, for this script, but it needs to support the .NET 4 libraries that XNA relies on.

Some cat just posted up a possible solution. They stated that it worked:

Update by Morshu9001 on 2014-01-12 09:08:11

This has been happening for me in Age of Empires II HD in Steam. I found a solution after I saw this thread, and I hope it'll work for Terraria too.

Go to your Libraries section in the Wine config, and add "gameoverlayrenderer" as an override. Set it to "disabled". This will kill the Steam overlay ingame but will fix the problem.

Give it a shot. This shouldnt be a permanent solution, though. The overlay MAY work. I actually thought I typed it earlier, but I guess not. Basically, the Steam interface that comes up when in-game (the overlay) gets buggy with the XNA framework. Its not a Steam thing, per se, but how the game interacts with the steam overlay. I havent had any issues with the overlay, but I dont use that game. Give that a shot.

Here are the programs installed in the WINE UNINSTALLER option in POL. I did not see .NET in their but WINE-MONO is there. I also know that there is no gameoverlayrenderer in the libraries.

http://imgur.com/o2qmOHc

Go to your Libraries section in the Wine config, and add "gameoverlayrenderer" as an override. Set it to "disabled". This will kill the Steam overlay ingame but will fix the problem.

PlayOnLinux -> Configure -> select Terr virtual drive -> Wine tab -> Wine Config -> Libraries tab-> in "New override for library" enter:


gameoverlayrenderer



-> click "Add", then highlight "gameoverlayrenderer", and click "Edit". Select "Disabled". Apply, click ok, and then try it.

This is for sure the issue, though its compounded with the XNA thing. I was looking at the Wine debug output, and it traces it directly from Terr XNA call to the overlay renderer. I would make sure to post this on [url]http://appdb.winehq.org[/org] if you have the chance. Im sure a patch is going to come about, or some other fix, as the overlay is a good thing, and fantastic feature in Steam. With all the work being done lately, there has to be something in the works. Hit up winehq and post a comment regarding this in the section for Terr.

NOTE: I personally wouldnt mention using POL off the top. They always close my posts, along with others, because its only for "wine issues", though this is clearly an issue between the XNA library and Steams implementation of the overlay feature.

Valve is very Linux conscious now (SUPER sweet. I love it. haha), so I doubt this will go by like nothing. The mere fact that Steam runs (ran? lol) so well through POL/Wine should for sure wake them up a bit.

Edited by RoninDusette

Edited by RoninDusette