Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
Phenom II 1090T user here, same thing. Already emailed you.
Edit: Might add, original release worked just fine. Something changed when it updated.
Unity loads with a red exclamation mark but the progress bar never finishes then it closes brings up please wait then crash
i've googled the error and people are saying it is cheat programs running but i'm not using any cheats,
my PC loads minimum system items on start up, bare bones start up win 10, also am only running games as its my dedicated game machine, so no office or anything like that
i've updated my OS via windows update, double checked my dx11 install, was going to see if there was an update patch for unity itself to see if i can get unity running
Oops - I just saw you mentioned you are running Windows 10. There are some compatibility mode settings. I forget what they are. Anyway .. get me all the info you can about your machine and I'll see if I can get it to repeat.
PS Have you tried un-installing and re-installing?
Best wishes! - Ken W
We may have spoke Ken and I certainly will!
All of these produced the Unity errors mentioned. I tried several game versions on each, not exhaustively each of them but most. Reboots were conducted for 1/2 of these, registry settings remained. (Issue does not seem to be there.) Only New Game was tested.
Ultimately all produced the crashes. I am sending the details in an email. I am suspecting that of the possibilities it could be a processor-specific issue with a Windows update but I will have look into if I have more time to pull the updates back since the game was installed. (There are about 5 and the system is a newish install (New Year's appx) on an SSD, running fine otherwise.)
Launched the VR version, same issue.
It may not have anything to do with it but I have done some research and found that this series of processors lacks SSE 4.2, up to the series penultimate which is the 1100T (one model up from mine.)
Oculus Link, therefore, would not load for me. (It would pass the check on the 1100T model. So I found this:
https://www.reddit.com/r/OculusQuest/comments/fq05jf/how_to_bypass_the_sse_42_check_during_oculus/
The Intel emulation worked to install it. Then I tried it on the game (regular version.)
No frickin' way. What do ya know... it launched. No error.
Well there you have it folks. SSE 4.2 may or may not be the breaking point, and it worked before a couple RX 580 (AMD Graphics) and Windows 10 Pro updates ago. The processor hasn't changed. I can confirm I got it launch using Intel's emulator though. And I'll create a guide for Steam shortly on how to shortcut this for those not wanting to follow the Reddit article instructions. It did work though, and I'll fiddle around with it later in the VR version, using Steam command line options to ensure it works there.
I'm looking forward to this
Thanks Ken. I feel I'm at a bit of an impasse reproducing it however. The version I got to work- important clarification: Is a non-Steam version. I was working my way to that anticipating difficulties. I was right. Steam overlay doesn't seem to want to play well with the emulator. I even disabled the Overlay and SteamVR options in Steam's properties menu for the game. It does generate a system crash (non-fatal) instead of the Unity crash upon New Game start. So that's new, but not a fix.
Here is the workaround:
I can confirm the GOG version will launch play-ably by extracting the contents of sde-external-8.69.1-2021-07-18-win.tar to the game directory: [Slider Button]>Manage Installation>Show Folder
Drop them in there, ensuring the files themselves go in the Colossal Cave folder, not in the same-named folder of the TAR file WITHIN the Colossal cave folder (i.e. Sde.exe must reside in Colossal Cave folder itself.) then use this to launch:
From a DOS/Cmd/Command.com window in that folder. It should also work launched from a Shortcut using the same. Confirmed that now myself.
This shortcut will launch the game nicely from a GOG installation without issues, and enters the New Game just fine:
Target:
Start in:
Run: Minimized.
You can also earn Achievements on GOG even running via sde/emulation. So that's a complete work-around. Not on the Steam platform, albeit, and I do like Valve's product here, but integrations are never wholly seamless across software (really rarely.) GOG's light touch has permitted this workaround to function 100%. It is a little laggy on object pick-up I noticed but it should be fully playable.
I suppose I am going to play it over there for the meanwhile.
I will revisit this in the nearish future. I'm an IT guy and have no problem reinstalling Windows to get to the bottom of why I had a functioning game for the first month only to experience Unity etc crashes thereafter. Everything else has been looked at, and some Windows updates do stick impossibly. Looking in that direction.
Hope this helps those who want to play, have a similar processor series and/or the same failure behavior regardless. GOG version + sde emulation is a working solution.