วีดีโอ

I found that it really depends on the car VDC cars are terrible with any setting I've tried. DWG feels smooth with 70% power on r9 here are my pithouse settings(make sure everything is up to date, both firmware and pithouse)- try them out { "": 0, "appFirmwareVersion": "1.2.1.32", "controllerType": "motor", "driftMode": false, "equalizerGain1": 200, "equalizerGain2": 240, "equalizerGain3": 300, "equalizerGain4": 300, "equalizerGain5": 300, "equalizerGain6": 0, "forceFeedbackMaping": "\u0000\u0000\u0014\u0014((<<PP\u0000d", "gameForceFeedbackFilter": 50, "gameForceFeedbackReversal": false, "gameForceFeedbackStrength": 70, "hardwareVersion": "RS21-D01-HW BM-CU-V21", "initialSpeedDependentDamping": 0, "maximumGameSteeringAngle": 450, "maximumSteeringAngle": 450, "maximumSteeringSpeed": 100, "maximumTorque": 70, "mechanicalDamper": 20, "mechanicalFriction": 20, "mechanicalSpringStrength": 0, "name": "gandzior settings", "naturalInertia": 150, "presetMode": "Drift", "safeDrivingEnabled": false, "softLimitGameForceStrength": 0, "softLimitStiffness": 100, "softLimitStrength": 78, "speedDependentDamping": 0, "steeringWheelInertiaRatio": 2800, "temperatureControlStrategy": 0, "version": "1.0" } heres AC CM FFB settings make sure that u have 900% angle in both pithouse and CM acstuff.ru/s/0iRKrS

That's just a standard kunos drift supra with 100% turbo and 1L of fuel in the tank :) Just that on the supra and it's perfect for me. Ahh almost forgot, the tyre wear is switched off, I would have went through the rear tyres by the time I got half way the track or end up in the green because of no grip :D

I managed to tone it down with just the moza pithouse settings and tweak in the content manager and it works okay. The oscilation only happen during fast drifts otherwise there's close to none

Try reduce force feedback gain in content manager

seems like D4 still crashes with no overclock and the visual ++ redist - the next thing I've tried is to cap my wide monitor to 60hz to match the other monitors I use so that all of them are at 60hz seems to work - also got the latest nvidia drivers which support D4

@@patryk199530 was about to try this but after the hotfix from 2day i didn’t crash anymore and manage to complete that main quest

@@joblotrep even after the hotfix I still crash sometimes but it isn't nearly as bad as it was :)

after installing d4 i noticed same issues started occuring in other games such as warzone 2.0. however there the error was more specific - it was to do with overclock of my gpu and also visual ++ redist update done that and problem solved too so it should technically work for d4 - no overclock - all in one visual ++ redist 2023 installed

@@patryk199530 Yes, fully agree, MW2 crashes the same way that's why I knew I had to try that. It returns a DirectX error. Could really be an unstability of the RAM/MOBO combination since most of the RAM sticks are sold for 3600MHz with OC (!).

seems like D4 still crashes with no overclock and the visual ++ redist - the next thing I've tried is to cap my wide monitor to 60hz to match the other monitors I use so that all of them are at 60hz seems to work - also got the latest nvidia drivers

try running the game in full screen. in Your documents create Diablo IV folder and in that folder create LocalPrefs.txt file This is maxed out graphics. if you pc can't run it well maybe at least you'll be able to get past play button and adjust the graphic settings accordingly. In that file paste LocalPreferencesVersion "2" SkipIntroMovie "1" FirstTimeFlowCompleted "1" DisplayModeFlags "0" DisplayModeWindowMode "0" DisplayModeWinLeft "0" DisplayModeWinTop "0" DisplayModeUIOptWidth "1920" DisplayModeUIOptHeight "1080" DisplayModeWidth "1920" DisplayModeHeight "1080" DisplayModeRefreshRate "60" DisplayModeColorSpace "0" DisplayModeMSAALevel "1" Monitor "0" HDRBlackPoint "0.001000" HDRWhitePoint "1000.000000" HDRBrightness "250.000000" SDRBrightness "1.000000" SDRLinearThreshold "0.500000" SDRHuePreserveRatio "0.660000" SDRExposureFactor "1.000000" Vsync "1" GpuCrashReportingMode "0" Adapter "0" DisableChromaEffects "0" LockCursorInFullscreenWindowed "0" LimitForegroundFPS "1" MaxForegroundFPS "150" LimitBackgroundFPS "1" MaxBackgroundFPS "8" Sharpen "0.300000" HardwareClass "5" PCIVendor "4318" PCIDevice "6918" flSafeZoneLeft "0.000000" flSafeZoneTop "0.000000" FontScale "1" ColorBlindFilter "0" ColorBlindIntensity "1.000000" CursorScale "0" QualityPreset "2" TextureQuality "2" TextureFilterQuality "4" ShadowQuality "3" FogQuality "2" PhysicsQuality "1" ParticlesQuality "1.000000" ClutterQuality "4" FurQuality "2" SSAOQuality "2" AntialiasingQuality "1" WaterSimQuality "1" ShaderQuality "2" ReflectionQuality "1" GeoComplexity "2" HeightFieldGeometryDetail "1" LowFX "0" Reflections "1" DynamicShadows "1" SoftShadows "1" Raytracing "0" RaytracedShadowsQuality "0" RaytracedReflectionsQuality "0" Distortion "1" DLSS "0" FSR "0" FSR2 "0" XeSS "0" RenderResolutionScale "1.000000" RenderCheckerboarded "0" MipBias "-0.000000" DisableTrilinearFiltering "0" MasterVolume "0.200000" EffectVolume "1.000000" MusicVolume "1.000000" NarrationVolume "1.000000" AmbientVolume "1.000000" SoundDriver "0" AudioDevice "0" SpeakerMode "0" QuestSubtitlesEnabled "1" CinematicsSubtitlesMode "1" PlayInBackground "0" MuteSound "0" MuteEffects "0" MuteAmbient "0" MuteVoice "0" MuteMusic "0" ItemDropSoundMaster "1" ItemDropSoundWeapons "1" ItemDropSoundArmor "1" ItemDropSoundJewelry "1" ItemDropSoundSocketable "1" ItemDropSoundOther "1" ItemDropSoundMinQuality "0" ItemAmbientSoundMaster "0" ItemAmbientSoundWeapons "0" ItemAmbientSoundArmor "0" ItemAmbientSoundJewelry "0" ItemAmbientSoundSocketable "0" ItemAmbientSoundOther "0" ItemAmbientSoundMinQuality "0" ItemDropHoverSound "0" ChatAudioDucking "1" ChatAudioDuckingEnergy "0.000000" TextLocale "2" SoundLocale "2" PushToTalk1 "1" PushToTalk2 "1" VoiceAutoJoin1 "0" VoiceAutoJoin2 "0" VoiceOutputVolume1 "1.000000" VoiceOutputVolume2 "1.000000" MicVolume1 "1.000000" MicVolume2 "1.000000" VoiceOutputDevice1 "0" VoiceOutputDevice2 "0" MicDevice1 "0" MicDevice2 "0" PlayerErrorAudioMode "0" UseScreenReader "0" TranscribeVoiceChat "0" ScreenReaderPlaybackSpeed "0.000000" ScreenReaderVolume "1.000000" ScreenReaderVoice "0" UseThirdPartyReader "0" SubtitleSize "0.000000" SubtitleColorIndex "0" BackgroundOpacity "0.000000" UseTextToSpeech "0" TTSVoiceId "0" TTSPlaybackSpeed "1" EnableTTSChannelLocal "1" EnableTTSChannelParty "1" EnableTTSChannelTrade "1" EnableTTSChannelClan "1" EnableTTSChannelWhisper "1" EnableTTSLineBreaks "1" EnableTTSCharacterName "1" EnableTTSChannelName "1" EnableTTSItemName "1" FilterFlags "-1"

@@patryk199530 thanks man! i super appreciate this. it still didnt work but oh wells. im not getting angry about it

@@snakehachi R.I.P :/

Mine crashed as well but after an hour, they certainly did something but it han't fix the issue :D

same here

@@lukejuke2385 delete the Diablo 4 folder in documents as @Troy Muni said it solves it, but don't put the game full screen because the problem via return leaves full screen (windowed mode)

I'll try that

Thank you, this worked. Shame the queue is 145mins now :)

it worked, but when messing with the graphics putting full screen, I pressed alt+tab and the game crashed

niceeeeee

@@leonardoinhoqui Yeah it happened to me one more time after that, but that was it. They were stress testing as well, so that may have contributed to the situation. It was pretty stable after Friday

Read the description. The video presents the problem and the "solution" is in the description, although I just crashed again after a longer while so it doesn't get rid of the problem....

I've noticed that they have huge memory leaks - i have 32 gigs of ram and a good gpu this game takes it all ...

haha that was my plan too but I noticed that it's doable to do the quests this way or at least it shows that you can get out of the crash zone if you find yourself stuck in the crashing loop of death :D.

do you have wide screen or multiple screens ? if yes are they this same resolution ?

maybe the wide screen is somehow the cause of it. I'll make sure to attach that video to a bug report along with all the crash reports that been generated by fenris system.

@@patryk199530 I tried to play with my 16:9 monitor and didn't work, crashed again while I was in a dungeon.

@@justinhess4535 I've got standard 1080p monitor and it didn't work so yeah. Seems like in dungeons something goes wrong for us. I've noticed that my whole pc freezes when that happens and there are awful memory leaks. The game resource usage climbs up to 22gb of ram and my whole gpu power I don't think it's that demanding...

just checked, it seems like wide screen is the issue. Unplugged every screen apart from standard 21 inch 1080p monitor and I could do couple of dungeons without a crash - plugged in the wide screen only and it crashed within minute.