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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
When I launch the game in Steam VR using my CV1 the game won't pick up the platform.
Very odd...
Copy and paste your "motion platform" to "motion platform " data from your original game hardware config file into the VR config file.
With the update to 1.8 came the problem that a new "hardware_settings_ config_vr.xml" came into play. These, since the motion platform manager is not yet known, the V3 does not work unless you can see the lines from the "hardware_settings_config.xml following.
<Motion_platform>
<udp ip = "127.0.0.1" delay = "1" extradata = "3" port = "10011" enabled = "true" />
<custom_udp ip = "127.0.0.1" delay = "1" port = "20777" enabled = "false" filename = "packet_data.xml" />
<fanatec pedalVibrationScale = "1.0" enabled = "true" wheelVibrationScale = "1.0" ledTrueForGearsFalseForSpeed = "true" />
</ Motion_platform>
Copy and paste at the appropriate place in the new "hardware_settings_ config_vr.xml", or overwrite the existing entries!
If you now want to start with the Next Level V3 Dirt Rally 2.0 in VR, it hangs and it comes to an error message. To fix them, you have to remove the check mark for "Allow for motion compensation in games and applications" under "VR Integration" in the Next Level Platform Manager.
Now it starts in a very modest VR with the Oculus Rift CV1, you can of course get it playable by some settings, it looks and feels much worse than the 4 years older Dirt Rally.
Sorry, it was not my intention to beat you! I just want to share my opinion with a few details.
Codemasters stuffed up big time when they let go of Paul Coleman as he was the brains behind why it was so good back then. Plus his co-driver calls were also miles better and clearer to listen to. What a shame they lost him else we would have a proper VR version, especially on Rift.
I have just woken up here in London and feel cheered to find your replies. I shall have a go later today at trying to locate the appropriate place (again how do I get there? I’m not sure...) to paste this new code and report back with my results.
Fingers crossed!
It'll be in My PC > Documents > My Documents > My Games > Dirt Rally 2.0 > Hardware Settings > (You'll see the Config files.) Right click and open with the "Notepad" Application.
You'll see coding that has this sort of writing.
<Motion_platform>
(Everything between, paste over in the VR file from your original game hardware config)
<Motion_platform >
Usually found like this, it may vary from system to system.
<Motion_platform>
<udp ip = "127.0.0.1" delay = "1" extradata = "3" port = "10011" enabled = "true" />
<custom_udp ip = "127.0.0.1" delay = "1" port = "20777" enabled = "false" filename = "packet_data.xml" />
<fanatec pedalVibrationScale = "1.0" enabled = "true" wheelVibrationScale = "1.0" ledTrueForGearsFalseForSpeed = "true" />
</ Motion_platform>
Sorry if it's confusing. Not the best at explaining in writing for PC related tasks.
Do I have to completely wipe the text/coding in the notepad at "hardware_settings_config_vr" and replace it with all of:
<Motion_platform>
<udp ip = "127.0.0.1" delay = "1" extradata = "3" port = "10011" enabled = "true" />
<custom_udp ip = "127.0.0.1" delay = "1" port = "20777" enabled = "false" filename = "packet_data.xml" />
<fanatec pedalVibrationScale = "1.0" enabled = "true" wheelVibrationScale = "1.0" ledTrueForGearsFalseForSpeed = "true" />
</ Motion_platform>
Or just the code between the first and last <Motion platform>?
Are you saying this port number on this code "20777" may be wrong and needs matching up to the port number in the screen mode hardware file?