安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
I have ESET NOD32.
A NullReferenceException happens when a developer has written code that tries to access a member on a variable of a reference type that doesn't actually hold an active instance, i.e. on a variable that holds a null reference.
In this particular case with FF9, the NullReferenceException originates from (wrapper managed-to-native) UnityEngine.Behaviour:set_enabled (bool) which, judging from the format of the method signature, is written in managed C++ and is used to bridge the game's C# code to the (unmanaged) C++ of the core Unity engine.
The set_enabled format is the mangled name for a setter function for an Enabled property. Probably the developer is trying to set that property at a moment where some part of the engine's internal state is not consistent (i.e. some value on which it depends is null).
I'm fairly sure this has nothing to do with 'hiccuping on compiling MSIL'.
GC is not about unloading files. It's about tracking objects that still reside in memory but to which no further reference exists in the running program and which are thus safe to be collected and purged, reclaiming the freed memory for re-use.
Silicon Studio built the game in Unity using C# code, which means it runs on the build of Mono included with Unity and that it uses Mono's garbage collector. While it's an older release of Mono where the garbage collector has performance issues, the collector does work correctly.
If the Mono GC were to actually collect objects 'too soon', that would make Mono entirely unusable and unfit for any purpose, which is simply ludicrous.
Has nothing to do with the OS version.
I've been running the game for almost 6 hours straight now on Win7 Ultimate 64Bit, on a GTX 960, i5-4670 without a single crash, I'm up to Burmecia now.
And for record, I've been alt-tabbing a ♥♥♥♥♥♥♥♥ of time as well.
Also, people saying it's solely a bug in the game are wrong, if it was, this bug would be hitting 100% of the people out there, which is doesn't. This doesn't mean it isn't a bug within the game per say, but it's more of a combination of things that produces it. Either Hardware, Drivers, In Memory processes, etc.
If it crashes when running a FMV, it could very well be a 3rd party codec pack messing things up, happened in the past. Could be a very specific GPU driver version messing things up (most recent drivers are not always bug free, as we saw with the more recent NVidia ones), as a note, I'm running on version 361.43 right now.
as I said, if it was solely a bug in the game, everyone would be affected. It's a combination of the game and something else.
Furthernote, who having the crashes uses the Steam Beta Client? (I'm not) for all we know, the beta client messes things up. Happened with Disgaea PC where the Steam Beta would massively ♥♥♥♥ up the framerate, reverting to the non beta would fix that.
What Zantagor said.
Also, one of the most interesting external factors to test that comes to mind is the Steam overlay. If you get crashes and have the overlay enabled, try switching off the overlay.
Wouldn't be the first time the buggy overlay would cause problems...
Iirc K-Lite includes FFDShow and if it's not correctly configured, FFDShow would definitely try to play back OGG video. Also FFDShow has a lo----ng history of causing crashes with video playback in games.
Ya, as a note though, I'm running with the overlay myself, since I wanted to see the FPS counter. But I am not running the beta client (not since the Disgaea PC mess)
Finally, after more than 1 hour playing, I had no crashes, I think the DEP thing fixes it, I disabled it totally and it works atm.
For Windows 7 and 10 users, you have to open as administrator the cmd, then paste there this:
bcdedit.exe /set {current} nx AlwaysOff
If you want to enable it again just change the "Off" to "On"
Then, restar your PC, and that's all. Anyway I did the "verify intrgrity files cache" in properties of the game in Steam, to download again the "broken" file.
For Windows 8/8.1 users I think it's a different command, but I don't know what it's atm.
So, thank you so much for this fix, I hope I have no crashes again. ;)
I'll PM you.
I'm using K-Lite, and my Version I used was pretty old the Update told me. Before I looked here again, I installed a new Version of K-Lite. But if I don't use K-Lite, I can't play a Video anymore. I rely on these stupid Codec-Packs since years and there wasn't a problem, not even a single time.
Also, I'm, using Windows Firewall and Windows Defender. Should I turn them off while playing Final Fantasy IX?
Bah, this is ♥♥♥♥♥♥♥♥. This Game should playback as smooth as the skin of a Baby. It's pretty hard to find a solution here. The K-Lite thing is, what bugs me the most. I will now try again the Game from the Start, and turining off the Firewall and starting the Game with a brand new K-Lite Codec-Pack.
Anyway! I'm glad I created this Thread. Many thanks to all of you.
These days, unless you're into video creating/editing/encoding you shouldn't need K-Lite or CCCP anymore. Video players like Media Classic comes preloaded with any codecs you'd need, and it's not going to mess up with DirectPlay at all, which K-Lite is known to do for many games.