![]() You might also want to make sure that "ONShowOptions" is set to "false/" with the ending slash, since I didn't confirm that before.Īs near as I can tell, the only things Oni does before writing to startup.txt are: Secondly, since Oni ran successfully at one point, can you look at the preferences in once more and make sure that there is no "RetailInstallationPath" setting now? If set incorrectly, it could be pointing Oni to the wrong directory. I meant to ask this one before: have you performed the ad-hoc signing of Oni that is described in the read-me "How to run Oni.rtf"? I think you must have, in order to run the game at all, right? Probably the two problems are totally different but I wanted to to mention it just in case it can help.Īll right, I'm back with a couple more ideas. Apparently it was a known issue with the fusion drive. It reminds me a little of another problem I had with Office, when starting it some days he was asking me to enter the licence key as if it was newly installed, some day it was working fine, randomly. I tried to start Oni right after start of the computer as the first app, but the problem was the same. As you said maybe something in the OS environnement is causing this. So the "crash" should really be early.Įven if Oni has been starting a few times yesterday, it seems it was really by luck. I have have no external monitor, only the iMac screenĪfter checking the startup.txt and debugger.txt files, I can confirm that they were not modified at all after any of the failed launches. staring Oni as the first app, but the result is the same adding the -debugdisplay, but nothing appear in the console using -nosparkle in the launch_args.txt => The result is similar as last time, it seems the launching stopped even earlier than without the -nosparkle argument You might have already checked, but I need to make sure they don't have something new in them from Oni's last failed launch, since they are the most useful files in determining why Oni won't run. Every launch of Oni should overwrite those files with new contents, even if Oni is crashing at launch (unless it's crashing really early). Since Oni ran successfully before, those files must have been generated, but the question is whether they are being written to when you attempt to launch Oni now. Have you tried restarting the Mac and running Oni as the first app after restart, to make sure that some other app you use isn't preventing Oni from working? That doesn't seem likely to me, but since Oni was running for a little while, I am wondering if something else in the OS environment is changing.įinally, just a reminder to check for startup.txt and debugger.txt again. If -nosparkle doesn't get Oni running, can you add the argument -debugdisplay and check Console again for messages from Oni? (Adding -novideos and -noswitch may help too, or at least they shouldn't hurt.) By the way, do you have a multiple-monitor setup, or just one monitor? Have you tried using -nosparkle again? I think that Sparkle may have been part of the problem, even if there's more. Note that I have tried to install Oni 1.2.1 on my old MacBook under Macos 10.6 and it works fine, but I would rather having it installed on the iMac ! ![]() « .NET, which is required to use this tool, is not installed on this machine. I have downloaded and installed the Mono package, but when starting the AE installer I keep getting the message: When launching the app just nothing happens, I have the Oni app menu bar on top, no window, nothing, I can just quit normally (no crash). I started by downloading the Oni 1.2.1 app at /taxonomy/term/6. Fusion drive (maybe not relevant, but this has caused me issues with some softwares). Unfortunately I am facing several difficulties to make it work: After having enjoyed playing ONI many years ago, I am quite happy to see that thanks to the effort of the fans an update is available to play it on Macos X.
0 Comments
Leave a Reply. |