安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
335 
檢舉此篇文章
at the topic:
to me it seems more and more like some kind of performance issue. just a feeling.
so if you guys could try out to maybe vaync on. lower graphics, lower taks priority..
just curiosity...
I had a private conversation with an Annapurna dev in regards to this issue months ago. From what was told to me, I expected to see a fix in the near future, and since I haven't played it since then, I expected that it had been fixed.
I'm not sure if they are still actively working on this issue, but I'll try to contact the dev again to follow up on our last conversation.
Additionally, it doesn't appear to be performance related. I monitored my hardware utilization during multiple tests on this bug, and it showed no significant changes during the issue. For context, I have a 2080Ti and an i9-9900K overclocked to 5.1GHz (an entire spec list can be found on my profile). I will be getting a 3090 soon, and will update you if the change in GPU has any affect on it.
(Screenshots of the conversation below)
https://puu.sh/GTh7v/656dacb796.png
https://puu.sh/GTh81/2d63c1aa25.png
https://puu.sh/GTh7R/cd06463c14.png
https://puu.sh/GTh7I/142d209b91.png
i think my feeling goes towards:
journey was optimised for a console. everyone is (almost) the same configuration.
so maybe your especially good performance on utlrasuperduper settings causes some bugs and having actually lags in game (maybe not recognised) cause other bugs....
original journey worked with 30 fps for example.
still curious: your tests, what did you test?
ahhh good old nathanG. some of the community talked with him too. and one guy helped them so much, that they could fix some connection problems :o
i really hope they make another update. the RT button crash really needs to be fixed. thats a constant for everyone afaik.
personally: i once had the problem to get it to start. found a fix and since then everything is fine... thats why i wonder so much whats the diffeerence between "you and me".
i play on a TV, via a gaming laptop (~2 years old). with a controller (dunno if keyboard/mouse could cause issues).
since long i wanted to write anna, for some things.. i really should do, but also .. that wiki :( so much work
I don't remember all of the tests that I did, but I can tell you the configurations and alternative methods that I used in testing different varieties of the same issue.
Configuration Changes (these didn't change the result):
>Tried with KB&M, PS4 controller running DS4 tool and also without, and Xbox controller
>Tried running it through VorpX (VR translation program, that turns the game into a VR experience) to see if the game's rendering system was changed at all due to the program, and if it affected the crash.
>Tried multiple frame limiters, on my monitor (240hz Acer monitor), all the way from 240fps to 30fps
>I tried it on another PC that was configured almost the exact same as mine (the other PC did not experience the same bug as me)
>Checked reliability report crash logs to see if there was any noticeable change or reason
>Tried pretty much every possible permutation of graphics settings
>Tried at least 30 different approaches to the situation (Some worked, as annotated in my earlier possible temp solutions. However I don't count it as a definitive change, considering that it was not reproducible 100% of the time)
>Tried at least 30 different camera angles and configurations (Same thing as above)
>Tried a different monitor
>Tried without an overclock
>Tried with different Vcore
There are probably a few other tests I'm forgetting, but that's most of them
wow. thats quite a list and no fix in sight :(
i cant reply with many words now, but most interesting points are
"the other pc, which is mostly like the bug-pc, doesnt crash" - whats the difference then :D there MUST be something.. *crazylooks*
FPS monitor limiting: does that affects the game? like does the monitor then tell the game to produce less FPS? i know people use external programs to actually go to like 10 fps to cause certain things in journey (they are exmperimenting with it, for fun)
"not consistent", from my experiment, many things in journey are not consistent. though its simple looks it seems to be rather complex. like many sound triggers, camera triggers, even a companion changes the music and stuff...
i mean, it might be just very hard, to reproduce a certain thing 100 %
lets just all, as community keep an eye on it.
guys, report directly to annapurna or to that nathanG guy!! (sry i am lacking links atm
we can help them, to help us!!!
for some time i had some machine bugs more often then normal too, but no crashes. and for no apparent reason, it works better now..
i still got the feeling it might be something obscure like screen resolution or that the game doesnt trigger or triggers too early something, gets confused and quits...
pardon my childish language.
i d beg for another 2 tests:
journey and steam with admin rights
higher or lower taks priority
just to make sure. and dont try both at the same time, so we can see what did what...
There was an AVX offset requirement for your boost clock?
b) what boost clock?
my only problems with steam journey where: first i couldnt start it, because some background programm was misisng. sometimes the machines are invisible (which is also possible on ps3 and 4, just the places where they are invisible were differnent; "new to me").