Building in Windows (Instead of Mono) causes traps to just not work
tysonstrange opened this issue · 24 comments
When you use VS To build in windows, it will build but no traps will trigger.
Seems teleporters and shit still work though, so its not all mechanics.
That's very, very weird.
This issue has been around for a while. We never figured out the cause. Fortunately Travis builds with Mono
Tell me about it....
Ask Tyler and see what he thinks about it... hahahahahahaha
Yeah, that
Well, orion will probably take care of that, along with countless other issues.
not a big deal.
It's not Windows specific. I build and run with Mono (xbuild) on Linux and traps don't work.
Same here. I tried to build in Mono using Linux and xbuild and it still doesn't work. I have tried Xamarin Studio as well in Windows to try and build Mono, with the same results.
Hopefully this does get fixed.
What version of Mono?
On Mon, Nov 23, 2015 at 12:26 AM Gotest notifications@github.com wrote:
Same here. I tried to build in Mono using Linux and xbuild and it still
doesn't work. I have tried Xamarin Studio as well in Windows to try and
build Mono, with the same results.
Hopefully this does get fixed.—
Reply to this email directly or view it on GitHub
#43 (comment)
.
I would assume the latest since I used the install guide for linux on mono-project.com. (http://www.mono-project.com/docs/getting-started/install/linux/) But if you need me to check, I can.
EDIT: Linux is using Mono JIT Compiler version 4.2.1.102
Using Ubuntu 14.04 and Mono 4.0.5, traps work when the project is compiled with xbuild
Linux is using Mono JIT Compiler version 4.2.1.102
Thanks. This is important because it gives us something to look at, particularly the diffs between 4.2.1 and 4.0.5. Now that the .NET CLR and the BCL is open source, mono have continuously been adopting MS implementations in lieu of their own in the interest of binary compatibility. It could be something in these references that are causing this.
I still don't have anything concrete to go on, but its a start.
Compiling with Mono 4.0.5 worked! Thank you guys so much!
Here's to me hoping you guys can figure out what's going on here! Best of luck to you!
According to http://www.mono-project.com/docs/about-mono/releases/4.2.1/, it replaces some ~500 types with Microsoft's implementation.
This is going to be a pain.
I would like to note this also fixes Training Dummies, and invisible Bombs/Dynamite.
Although Campfires still seem to disappear when trying to disable them (right click.)
Holy. Fucking. Shit.
Invis bombs are fixed? Gimme.
Hmm, the build server is on 4.0.2.0. Invisible bombs happen in the latest
official build?
On Tue, Nov 24, 2015 at 6:03 PM tysonstrange notifications@github.com
wrote:
Holy. Fucking. Shit.
Invis bombs are fixed? Gimme.
—
Reply to this email directly or view it on GitHub
#43 (comment)
.
Hmm, the build server is on 4.0.2.0. Invisible bombs happen in the latest
official build?
Yeah, pretty sure its still an issue here
Okay, so the invisible bombs aren't 100% fixed but they're working almost 80% of the time now instead of never working at all.
Okay, so the invisible bombs aren't 100% fixed but they're working almost 80% of the time now instead of never working at all
Thats how it's always been...
It's never been so bad that they're invisible 100% of the time.
On my mono-4.2.1 instance, I am able to trigger a super dart trap with a lever once, and only once if the solution is compiled in release mode with xbuild /p:Configuration=Release.
I was able to trigger dart traps, spear traps, and flame traps continuously using a switch with a 4.2.1 instance
More info? I should be able to trigger a super dart trap from a wire and a lever, right? Doesn't have to be in a certain biome or at night? Any other variables? Platform? Did you compile it or run stock?
Mono-4.0 binaries from our CI has always worked. This doesn't work when I compile the image using >= mono-4.0.2 or windows
👍👍👍😘😘😘
On Wed, Nov 25, 2015 at 7:33 AM Tyler Watson notifications@github.com
wrote:
Closed #43 #43
via 89f0d08
89f0d08
.—
Reply to this email directly or view it on GitHub
#43 (comment)
.