Jump to content

DiRT Rally 2.0 - Version 1.10 VR Feedback

Recommended Posts

Steam - Deluxe version.  Oculus Rift.

Wheel: Thrustmaster TX

Key binding for "button 3" (on the wheel) is not working anymore. Have been perfectly fine until latest update.
I bind that button to a buttonbox. Actually the button is binded when I press it in the setup, but in-game it does not respond.

Edited by MongoJon [VR]

Share this post


Link to post
Share on other sites

Hello.
My real big problem is the heavy rain and heavy snow weather. When this happens in both rally and rallycross it is literally impossible to see anything if you use the cockpit camera view in VR. It is not racing it is surviving ! I have to use an external camera to play because otherwise I cant play ... I cant see anything almost outside the windshield. This is really really annoying. On top of it AI seems to be totally indifferent to the weather conditions. They always make the same times ..... You really need to curb the intensity of the snow and the rain on the windshield. I understand wanting to be "realistic" but this is WAY too much guys ....


I use the Steam Version. My specs are in the signature. Other than this huge problem with heavy weather the game works great for me.

Edited by koog2003
  • Agree 1

Share this post


Link to post
Share on other sites

Heavt rain - Night - Oculus Rift - Steam Version - Specs in the signature

Can barely see the track from the cockpit view in VR .. way too much weather effect 
 


 

Edited by koog2003

Share this post


Link to post
Share on other sites
On 11/17/2019 at 10:52 AM, koog2003 said:

On top of it AI seems to be totally indifferent to the weather conditions. They always make the same times .....

+1

With heavy rain or snow it's totally impossible to win a rally. IA must have robotic eyes!!

  • Agree 2

Share this post


Link to post
Share on other sites

Engine sounds are not where they should be, when using headset it feels like it's between your ears. 

Share this post


Link to post
Share on other sites

Smoke particles doesn't spaw how they should. If you turn head you can't see smoke particles behind car, you have to turn your car into direction where they should be to see them. Weird enough that they are drawn on mirror tho, which i don't need so much. Option to turn them off from mirror could save some gpu power.

Edited by Jeq
  • Like 1

Share this post


Link to post
Share on other sites

Pressing clutch + handbrake when car is still while at neutral Gear should recover car on track automatically, i lose lot of Time trying to find recovery Button while wearing headset

Share this post


Link to post
Share on other sites
4 hours ago, Jeq said:

Smoke particles doesn't spaw how they should. If you turn head you can't see smoke particles behind car, you have to turn your car into direction where they should be to see them. Weird enough that they are drawn on mirror tho, which i don't need so much. Option to turn them off from mirror could save some gpu power.

it is something similar to smoke coming from an engine. it's not rendered when you have are looking ahead. Once you turn the head a bit, fragments of smoke appears.

Edited by MaXyMsrpl

Share this post


Link to post
Share on other sites
On 10/31/2019 at 4:59 AM, Ialyrn said:

You can change the settings in the "hardware_setting_config_vr" file located in "Documents\My Games\DiRT Rally 2.0\hardwaresettings". In there you have options to set the window resolution, as well as to set it into windowed mode.
Options you want to look for are

"resolution width="1280" height="720" " (change the numbers to change the desktop window resolution)
"fullscreen="0" " (setting to "0" sets it to windowed mode)

Hope that helps.

@PJTierney This sort of stuff should be changable in game through the graphical options menu, expecting the whole player base to know these things can be changed in file is just plain backwards.

This is not working for me. I have tried both windowed and fullscreen. My problem is the image is stretched out as if it was an ultrawide monitor.

I have changed settings to this: resolution width="1920" height="1080" aspect="auto" fullscreen="0"

I tried forcing 16:9 by doing this but it doesn't work either: resolution width="1920" height="1080" aspect="1.78" fullscreen="0"

As you can see in the below screenshots my mirrored screen is being stretched wide. I was hoping forcing the resolution and aspect ratio would work but it changes nothing.

451933181_Screenshot(166).thumb.png.45ffea96af27e2746a0010b315bfeaf8.png

1414380369_Screenshot(167).thumb.png.250497c4f712c9120ce1c36af1e54d30.png

Share this post


Link to post
Share on other sites

Patch notes are up, nothing about the crushed black. WHY?????

Edited by kellemann

Share this post


Link to post
Share on other sites
17 minutes ago, kellemann said:

Patch notes are up, nothing about the crused black. WHY?????

Its a joke that they added each separate country comfort rating change in the patch notes to make it look like vr got some improvement..

  • Agree 3

Share this post


Link to post
Share on other sites

Oculus Quest HMD

Intel 3770 CPU

EVGA/Nvidia RTX 2060 GPU

Logitech G29 Wheel, pedals and H shifter

Running Steam Deluxe version.

When launching in Oculus mode it tells me my headset is not recognised. Can launch in Steam VR mode OK but if it's true the Oculus mode works better I'd rather use that.

I'm hoping this is because it's looking for a specific list of supported models and because Quest link is new and in beta it's not yet included.

Or perhaps it's objecting because the rift software has a beta function enabled.

I'm new to VR but in my limited experience so far other games just see it as a rift.

Update:

If I ignore the warning it lets me continue and works fine in Oculus mode.

Feeling a bit stupid now

 

 

Edited by Smithers1968
I'm an idiot

Share this post


Link to post
Share on other sites

Valve Index

Ryzen 3700x

MSI RTX 2080ti

Logitech g29 complete rig

Steam Super Deluxe version

------------
I just noticed that: when setting refreshrate to 120Hz some objects got weird physics: for example thrown stones are levitating or falling really really slowly... and they seem to stay in the air forever sometimes (rallycross circuits are creepy with this issue: you ride through a cloud of levitating pebbles :D).

Overexposure of HDR has been mentioned like 1000times, so I am adding my +1 to this.

And what ruins my VR experience a lot is weird stones (these laying on the track) shimmering, flickering and overlight during stages with carlights switched on.

  • Agree 1

Share this post


Link to post
Share on other sites

I'm not sure if I'm the only one, but since the last couple of patches, VR play has become really unreliable for me? I'm getting crashes and freezes fairly regularly.

This wouldn't be too bad, but in community events after a crash I'm advanced to the next stage, and have time added as if I'd retired the entire rally. This has happened 3 times to me in the last few days, it makes the game impossible to play competitively. Not that I'm that competitive in terms of times mind you...!

I'd had very few crashes if any in VR mode until very recently.

One thing I did notice was that after one of the recent patches, the game wouldn't recognize my peripherals. I had previously installed the 3rd-party 'stutter' patch to reduce the stutters caused by the somewhat daft built-in USB polling, which worked well, but I wondered if this was conflicting with one of the new patches. So I completed uninstalled and re-installed from Steam, and the game recognized my wheel and handbrake fine. But since then it's been crashing repeatedly. Anyway, this means I'm in a pretty much fresh install.

I have a .dmp file from one of the recent crashes. I'd happily share it, but it is 6GB...!

Platform: Windows, Steam & Occulus modes
Headset: Oculus Rift S
PC: 2500k, 1060 6GB, 12GB RAM, RAID Sata SSDs
Deluxe Steam User
Thrustmaster TX, generic USB handbrake

Share this post


Link to post
Share on other sites

So I've had a quick go with the Windows Debugging Tools (insert "I have no idea what I'm doing" meme here) and it spat out the following. Any ideas?

Quote

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\dirtrally2.DMP]
User Mini Dump File with Full Memory: Only application data is available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Version 18363 MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Debug session time: Mon Dec  9 20:18:26.000 2019 (UTC + 0:00)
System Uptime: 0 days 0:12:57.103
Process Uptime: 0 days 0:11:21.000
................................................................
................................................................
...
Loading unloaded module list
............
For analysis of this file, run !analyze -v
ntdll!NtReleaseSemaphore+0x14:
00007ff8`6515c204 c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify checksum for dirtrally2.exe
*** WARNING: Unable to verify checksum for bink2w64.dll

KEY_VALUES_STRING: 1

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 777

    Key  : Timeline.Process.Start.DeltaSec
    Value: 681


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
    Name: <blank>
    Time: 2019-12-11T10:48:54.264Z
    Diff: 138628264 mSec

Timeline: Dump.Current
    Name: <blank>
    Time: 2019-12-09T20:18:26.0Z
    Diff: 0 mSec

Timeline: Process.Start
    Name: <blank>
    Time: 2019-12-09T20:07:05.0Z
    Diff: 681000 mSec

Timeline: OS.Boot
    Name: <blank>
    Time: 2019-12-09T20:05:29.0Z
    Diff: 777000 mSec


DUMP_CLASS: 2

DUMP_QUALIFIER: 400

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  000031cc

BUGCHECK_STR:  BREAKPOINT

DEFAULT_BUCKET_ID:  BREAKPOINT

PROCESS_NAME:  dirtrally2.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

EXCEPTION_CODE_STR:  80000003

WATSON_BKT_PROCSTAMP:  5dbaf5c1

WATSON_BKT_PROCVER:  1.10.129.2193

PROCESS_VER_PRODUCT:  DiRT Rally 2.0

WATSON_BKT_MODULE:  unknown

WATSON_BKT_MODVER:  0.0.0.0

WATSON_BKT_MODOFFSET:  0

WATSON_BKT_MODSTAMP:  bbbbbbb4

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

MODLIST_WITH_TSCHKSUM_HASH:  9680729f73683182cdece4363174825d6bbf566e

MODLIST_SHA1_HASH:  05392f178ccc7b690bbc92d43aa8247549311b06

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

PRODUCT_TYPE:  1

SUITE_MASK:  272

DUMP_FLAGS:  8000c07

DUMP_TYPE:  3

ANALYSIS_SESSION_HOST:  TREVOR

ANALYSIS_SESSION_TIME:  12-11-2019 10:48:54.0264

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

THREAD_ATTRIBUTES: 
OS_LOCALE:  ENG

PRIMARY_PROBLEM_CLASS:  BREAKPOINT

PROBLEM_CLASSES: 

    ID:     [0n321]
    Type:   [@APPLICATION_FAULT_STRING]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Omit
    Data:   Add
            String: [BREAKPOINT]
    PID:    [Unspecified]
    TID:    [Unspecified]
    Frame:  [0]

LAST_CONTROL_TRANSFER:  from 00007ff8623a817b to 00007ff86515c204

STACK_TEXT:  
000000af`64bed7b8 00007ff8`623a817b : 00000000`00000000 00000000`00cf0000 000001bb`8036d200 00000000`00000000 : ntdll!NtReleaseSemaphore+0x14
000000af`64bed7c0 00007ff6`7ea57d92 : 000001bb`902001f0 000000af`00000017 000001bb`00000000 00000000`000005e4 : KERNELBASE!ReleaseSemaphore+0xb
000000af`64bed7f0 00007ff6`7ea8425d : 0000fd97`00000000 00000000`00000000 00007ff6`7ffc1950 00000000`00000000 : dirtrally2!AK::WriteBytesMem::Count+0xe0532
000000af`64bed840 00007ff6`7ea6b751 : 000001bb`96e51510 000000af`64bed960 00000000`00000000 00007ff6`7ea3c718 : dirtrally2!AK::WriteBytesMem::Count+0x10c9fd
000000af`64bed870 00007ff6`7ea26eb3 : 000001bb`96e51510 000001bb`80383369 000001bb`96e51510 3f773761`3f848c42 : dirtrally2!AK::WriteBytesMem::Count+0xf3ef1
000000af`64bed8e0 00007ff6`7ea2cbdc : 000001bb`8036d200 000000af`00000000 000001bb`96e51510 000001bb`8036d200 : dirtrally2!AK::WriteBytesMem::Count+0xaf653
000000af`64bed9a0 00007ff6`7ed07cdf : 000000af`64bedbb0 00007ff6`00000000 000001bb`d33d5210 00007ff6`7eb0381e : dirtrally2!AK::WriteBytesMem::Count+0xb537c
000000af`64beda60 00007ff6`7e649879 : 000001bb`970de4e0 00000000`ffffffff 00000000`00000000 00000000`00000000 : dirtrally2!AK::WriteBytesMem::Count+0x39047f
000000af`64bedab0 00007ff6`7ecac1d5 : 00007ff6`7ff58000 00000000`0000000b 00000000`00000011 000001bc`32404b20 : dirtrally2!AK::MusicEngine::Term+0x160749
000000af`64bede80 00007ff6`7ecac39b : 00007ff6`7f2f0960 000000af`64bedff9 00000000`00000000 00000000`00000000 : dirtrally2!AK::WriteBytesMem::Count+0x334975
000000af`64bedf20 00007ff6`7e5658cc : 000000af`00000000 000000af`64bee350 000001bb`96e339b0 000001bb`9656c020 : dirtrally2!AK::WriteBytesMem::Count+0x334b3b
000000af`64bedf60 00007ff6`7e785ccd : 3f998aae`259de1de 3f998aae`259de1de 000001bb`ffbe0f00 00000000`00000002 : dirtrally2!AK::MusicEngine::Term+0x7c79c
000000af`64bee060 00007ff6`7f02feff : 00000000`0000000a 00000000`00000000 00000000`00000000 00000000`00000000 : dirtrally2!AK::MusicEngine::Term+0x29cb9d
000000af`64bef910 00007ff8`63f07bd4 : 00000000`00000000 00000000`00000000 00000000`00000000 00007ff8`2a280000 : dirtrally2!AK::Monitor::GetTimeStamp+0x24714f
000000af`64bef950 00007ff8`6512ced1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
000000af`64bef980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


STACK_COMMAND:  ~0s; .ecxr ; kb

THREAD_SHA1_HASH_MOD_FUNC:  4b76630949e5b51da7bb08f691c93e5b27e65a26

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d177346e36bbfa25be964f221e1573ee85042de8

THREAD_SHA1_HASH_MOD:  eb7f81468a3f0ab2bd5fd8ef745a68e2887c5e3a

FOLLOWUP_IP: 
dirtrally2!AK::WriteBytesMem::Count+e0532
00007ff6`7ea57d92 85c0            test    eax,eax

FAULT_INSTR_CODE:  850fc085

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dirtrally2!AK::WriteBytesMem::Count+e0532

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dirtrally2

IMAGE_NAME:  dirtrally2.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5dbaf5c1

BUCKET_ID:  BREAKPOINT_dirtrally2!AK::WriteBytesMem::Count+e0532

FAILURE_EXCEPTION_CODE:  80000003

FAILURE_IMAGE_NAME:  dirtrally2.exe

BUCKET_ID_IMAGE_STR:  dirtrally2.exe

FAILURE_MODULE_NAME:  dirtrally2

BUCKET_ID_MODULE_STR:  dirtrally2

FAILURE_FUNCTION_NAME:  AK::WriteBytesMem::Count

BUCKET_ID_FUNCTION_STR:  AK::WriteBytesMem::Count

BUCKET_ID_OFFSET:  e0532

BUCKET_ID_MODTIMEDATESTAMP:  5dbaf5c1

BUCKET_ID_MODCHECKSUM:  0

BUCKET_ID_MODVER_STR:  1.10.129.2193

BUCKET_ID_PREFIX_STR:  BREAKPOINT_

FAILURE_PROBLEM_CLASS:  BREAKPOINT

FAILURE_SYMBOL_NAME:  dirtrally2.exe!AK::WriteBytesMem::Count

FAILURE_BUCKET_ID:  BREAKPOINT_80000003_dirtrally2.exe!AK::WriteBytesMem::Count

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/dirtrally2.exe/1.10.129.2193/5dbaf5c1/unknown/0.0.0.0/bbbbbbb4/80000003/00000000.htm?Retriage=1

TARGET_TIME:  2019-12-09T20:18:26.000Z

OSBUILD:  18363

OSSERVICEPACK:  329

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  91cd

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:breakpoint_80000003_dirtrally2.exe!ak::writebytesmem::count

FAILURE_ID_HASH:  {daf03286-8b0a-511d-b36b-792801c4e069}

Followup:     MachineOwner
---------
 

 

Share this post


Link to post
Share on other sites
On 12/5/2019 at 4:47 PM, somethingthing said:

Its a joke that they added each separate country comfort rating change in the patch notes to make it look like vr got some improvement..

Codemasters has no shame 😞

There are a lot of bugs in VR, some of there very important and commented many times on this forum...

It's sad

  • Agree 1

Share this post


Link to post
Share on other sites

16GB -Patch 1.11 and the game is still the same for me...

 

👎

Edited by Flens07
  • Sad 1

Share this post


Link to post
Share on other sites
On 12/11/2019 at 2:39 AM, piphil said:

I'm not sure if I'm the only one, but since the last couple of patches, VR play has become really unreliable for me? I'm getting crashes and freezes fairly regularly.

This wouldn't be too bad, but in community events after a crash I'm advanced to the next stage, and have time added as if I'd retired the entire rally. This has happened 3 times to me in the last few days, it makes the game impossible to play competitively. Not that I'm that competitive in terms of times mind you...!

I'd had very few crashes if any in VR mode until very recently.

One thing I did notice was that after one of the recent patches, the game wouldn't recognize my peripherals. I had previously installed the 3rd-party 'stutter' patch to reduce the stutters caused by the somewhat daft built-in USB polling, which worked well, but I wondered if this was conflicting with one of the new patches. So I completed uninstalled and re-installed from Steam, and the game recognized my wheel and handbrake fine. But since then it's been crashing repeatedly. Anyway, this means I'm in a pretty much fresh install.

I have a .dmp file from one of the recent crashes. I'd happily share it, but it is 6GB...!

Platform: Windows, Steam & Occulus modes
Headset: Oculus Rift S
PC: 2500k, 1060 6GB, 12GB RAM, RAID Sata SSDs
Deluxe Steam User
Thrustmaster TX, generic USB handbrake

You are not the only one by far.  I am lucky to get three tracks in a row without this joy.

 DR2crash.thumb.jpg.58809a03129aacf1a7f7afad60e38dcf.jpg

Share this post


Link to post
Share on other sites
15 minutes ago, NateFink said:

You are not the only one by far.  I am lucky to get three tracks in a row without this joy.

 DR2crash.thumb.jpg.58809a03129aacf1a7f7afad60e38dcf.jpg

Ah, that's useful, because now my crashes are mostly like this, rather than freezes where I had to ctrl-alt-delete out. 

What's happening Codies? Are you getting our crash reports? I've submitted the last couple...

 

Share this post


Link to post
Share on other sites

v1.11 menus and non-stereo screens have got a lot more alias artifacts. Has AA been disabled on these maybe?

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×