Game plays on one machine and not another

Unity Engine
1

When I run the .exe on my machine, it works. When I try and run it on another machine, it doesn’t even load. Anyone have any idea why it loads on one and doesn’t do anyrthing at all on another?

2

Still not working. Today, I brought the entire project folder to work and tried running both a debug build as well as release build. It just won’t even load. It does something for about a second, then terminates. Works fine on my machine at home. Anyone have a clue as to what may be happening?

3

drop here your log file

4

Output log file or debug file?

5

Can anyone tell me what is the require .Net version to run a Unity app? I tried my game on my IT guy’s machine and it ran, so the difference is either a hardware or software config. Granted, he has the latest .Net and he can’t remember the last time my machine was updated, AND he has better graphics hardware. However, I don’t think graphics hardware should affect anything because Unity apps are designed to operate on lower-end machines reduced settings. Even still, graphics incompatibility wouldn’t affect the ability to even load up the graphics options screen, would it?

6

.net is not needed for unity - we use mono and have everything needed in the package
As for log - output_log.txt. For me on win it got saved in data folder

7

I’ll post the log tomorrow. I never tried running it on my work machine after my IT admin ran it successfully on his, so log looks fine/normal. I can however tell you that the log file, after I unsuccessfully tried to run it, was only two lines. They just showed the path of the file and one had mono[0] and the other had mono[1]. That was it. Just those two lines.

8

Solved it, but not sure if this is intended behavior or a bug. At work, my Desktop is on the server, not the local machine. When I tried running it from the Desktop, it would fail. However, on the advice of my IT guy, I mapped my Desktop to a local drive letter. Again, running it directly from Desktop failed, but when I opened the newly mapped drive and ran it, it worked. Can anyone explain why this happens?