Author Topic: Issues with The Division: Game Crashes and FPS dips  (Read 11054 times)

darkpower

  • Noob
  • *
  • Posts: 13
Issues with The Division: Game Crashes and FPS dips
« on: March 14, 2016, 04:46:11 pm »
Trying to record Let's Play for The Division, and I've been experiencing game crashes to desktop after about 30 mins to an hour into a session, and sometimes, the game will dip down to about 45 FPS or so randomly. This is something that might be a bit connected to the type of hard drive that I have been using (and the pain that has been trying to find a place to store everything). However, I'm trying to find out if there is any other reason for this (someone else on Ubisoft's forums said they, too, were experiencing game crashes when Dxtory is hooked to the game.

Not sure if I can get a log for you since there was no log that I could grab, but apparently, Dxtory and The Division isn't being nice to each other, and not sure why or how to fix it.

I've been using the following settings

UTVideo YUV420 BT.709 VCM Codec Jan 2016 version (have also tried Magic YUV, 1.2 with same results)
Sync Video FPS off
135MB/sec 7200 RPM 2TB Hard Drive
Multi GPU Stable Processing
All CPU Processors checked (Normal priority)(i have a Intel Core i7-4930K Processor)
Sync Surface Lock and Wait for Available Buffer both checked

Force CPU Processing, Multi Device Processing, and Force Down Sampling I've toggled on and off to test. No change happened at any point.

The issue, for me, might also be the amount of threads I'm telling Dxtory to use. For whatever reason, it's showing me 11 threads I can check, even though I have a 6 core processor (pretty solid processor, even when I bought it 2 years ago). Is this correct, or is this just the standard for Dxtory?

Is it a possible issue with how the game and Dxtory treat each other, the game being a hardware hog, or is it settings I'm not setting right? Or is it something else altogether?







Tyler Serafin

  • Noob
  • *
  • Posts: 48
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #1 on: March 14, 2016, 10:15:23 pm »
It's a brand new game man, you gotta give it time. Dxtory isn't making it crash.

Takedown

  • Monster
  • ****
  • Posts: 274
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #2 on: March 15, 2016, 06:46:52 pm »
Post the log files if you can
http://forum.exkode.com/index.php?topic=2.0


You generally do not want to turn on things in the Advanced tab unless you have a specific reason to do so, such as SLI / Crossfire.  Did you enable them for a reason or because a guide recommended it ?

Which copy do you have ? Steam , Origin or just Uplay ?   Do you have multiple overlays running at the same time ? 
If so, it would be best to disable or close any that you can and also try the delay hook option in advanced settings.
http://images.akamai.steamusercontent.com/ugc/26239834581781873/C4633A2F6ADBBFC018A9949BC3FB03CC3BBB5D46/
« Last Edit: March 15, 2016, 06:54:28 pm by Takedown »
Using Windows 10 ?  Try the latest version first http://exkode.com/dxtory-downloads-en.html

Tyler Serafin

  • Noob
  • *
  • Posts: 48
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #3 on: March 15, 2016, 10:17:41 pm »
It isn't dxtory making it crash,  I mean go head post your shit man but trust me, I get crashes too, not every time and sometimes Dxtory isn't even open and its after a fresh restart. It's a brand new game, give it time.

ClassifyLP

  • Veteran
  • ***
  • Posts: 241
    • ClassifyLP on YouTube
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #4 on: March 16, 2016, 05:36:13 am »
It isn't dxtory making it crash,  I mean go head post your shit man but trust me, I get crashes too, not every time and sometimes Dxtory isn't even open and its after a fresh restart. It's a brand new game, give it time.

I concour, the game isn't perfectly stable, don't think Dxtory has anything to do with it.

darkpower

  • Noob
  • *
  • Posts: 13
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #5 on: March 16, 2016, 07:17:42 am »
It isn't dxtory making it crash,  I mean go head post your shit man but trust me, I get crashes too, not every time and sometimes Dxtory isn't even open and its after a fresh restart. It's a brand new game, give it time.

I concour, the game isn't perfectly stable, don't think Dxtory has anything to do with it.

First of all, to Tyler, I don't know what is actually causing it. I just saw one other person on the Ubi forums stating that they were using Dxtory at the times of the game crashes. I don't know if it's a direct result, and it might be a coincidence, but it's worth pointing out. Yeah, it's a new game, and Ubisoft games are known to have their issues, but it does seem like these problems start the second I hit record on Dxtory, and go away the second I stop.

Which includes the random and sudden FPS drops. This is the main thing (and even if the crashes aren't related, I'm pretty sure the FPS drops have to be since this only happens when I try to record). I have tried a lot of things, and though sometimes it can stay at 60, there are times where it will, for no reason whatsoever, go to 45 FPS or so. Near the main hub, I stay at 60 or above throughout...until I hit record, then it does a sudden drop for reasons I cannot explain in the exact same area. Again, this could be because of my hard drives, but I don't know that for sure.

I do have SLI enabled on Dxtory because I have two 970's in SLI on my computer. Here's the EnviroLog (since it's the only log I have of anything at the moment):

[Dxtory]
Version: 2.0.133
UID: 9ffc389f-956b-445d-8541-ebbb747443e5

[Dxtory Files]
InstallPath: C:\Program Files (x86)\ExKode\Dxtory2.0
amd_ags.dll Size: 271,872 bytes Ver:  SHA1: 44ab4f74637e23ca586580c6d746974e86da98e6
AppNames.txt Size: 1,047 bytes SHA1: 40cd39ab435dbcb3d44eba72b737a05b9a14410b
AudioStreamSplitter.exe Size: 38,432 bytes Ver: 2.0.0.2 SHA1: 5195bb906a508f9e7175f3c9c7d62c6c76f8217c
AudioStreamSplitter_ja.txt Size: 134 bytes SHA1: 489a5264d73a47edcce7c92edb131cf63e5e5709
AVIFix.exe Size: 72,192 bytes Ver: 2.0.0.131 SHA1: 8743067b975002d014008cfb0db363dfb606c375
AVIFix_ja.txt Size: 288 bytes SHA1: 9cab20780686687b84f604c77c73aaae3fd8126d
AVIMux.exe Size: 166,432 bytes Ver: 2.0.0.131 SHA1: 434d85edc5d4bb77c64ca703f9790062cc87a117
AVIMuxCore.dll Size: 199,200 bytes Ver: 2.0.0.130 SHA1: 53661b27f6f6f9f3e8316dca872fd4b01da93e49
AVIMux_ja.txt Size: 1,701 bytes SHA1: fa240715d701f450bb95377aa8517a252329b619
CryptData.pup Size: 84 bytes SHA1: cf9d724807f965d372da4d168bebd78c5258d6ae
Dxtory.exe Size: 589,888 bytes Ver: 2.0.0.133 SHA1: 112e0c6136d3455e32c9cc047b2d55840ef79d95
Dxtory64.exe Size: 130,112 bytes Ver: 2.0.0.132 SHA1: 4cce60b896a04515767435c7fd29feefed3c1aac
DxtoryCore.dll Size: 7,156,768 bytes Ver: 2.0.0.133 SHA1: 8c4bcb0235aa424005894a469cdb2f7ac20f2948
DxtoryCore64.dll Size: 6,827,584 bytes Ver: 2.0.0.133 SHA1: df973ccbcaa8139218bbd38d1390aafa18aec562
DxtoryHK.dll Size: 197,184 bytes Ver: 2.0.0.133 SHA1: 76a78fb0c1ef0e058318a2228f4be4b5c17250da
DxtoryHK64.dll Size: 216,640 bytes Ver: 2.0.0.133 SHA1: 37518914336dc43e9a9b85dab0a639ea12318990
DxtoryMM.dll Size: 1,125,952 bytes Ver: 2.0.0.132 SHA1: b0b6fcc47b6b3f326de582975b269d57c2dd0594
DxtoryMM64.dll Size: 1,139,776 bytes Ver: 2.0.0.132 SHA1: 4cc91746487d863e2eea7a572c498c7eddf83817
DxtoryVideo.dll Size: 434,720 bytes Ver: 2.0.0.130 SHA1: 8d1393e8ce7cfd4b5e2a3481308b8410c3730ab7
DxtoryVideo64.dll Size: 473,120 bytes Ver: 2.0.0.130 SHA1: f2c63192dfe94db290be10a9d8b66c7a04949ae3
DxtoryVideo64_Install.bat Size: 28 bytes SHA1: 308ae1e37b5e28ff7134beb319faad48280068b0
DxtoryVideo64_Uninstall.bat Size: 31 bytes SHA1: 3fbf8d3c3a5b375eda07e47a64534b91c8df5139
DxtoryVideoSetting.exe Size: 129,568 bytes Ver: 2.0.0.130 SHA1: ee440e846cfeec2acb4a88f81f589e00c34e825e
DxtoryVideoSetting_ja.txt Size: 1,675 bytes SHA1: e532f36bd5ac6255659d240180637484661f0c83
DxtoryVideo_Install.bat Size: 26 bytes SHA1: b00e69772cc1cae9e86fe2b70ca290c488723fd7
DxtoryVideo_Uninstall.bat Size: 29 bytes SHA1: 0b0202cbc7fba373f42e1a6916fc2ad01edaa627
Dxtory_ja.txt Size: 18,461 bytes SHA1: 093689676cf8ca51b99c97253e5187ded508838a
EULA_en.txt Size: 1,356 bytes SHA1: 340c6b3425ab78d83c6a8bd344b6cc58d152ce8f
EULA_ja.txt Size: 1,814 bytes SHA1: cded0d38ec6a1cb0e86bc264496deaa28082cb51
filelist.txt Size: 279 bytes SHA1: 922bf7faeb7b7dbdd5b64ab4b5bb9a069333b106
filelist64.txt Size: 289 bytes SHA1: 29fc32a01a6aa2edc4d4cb45dbc977e3b27172ca
ignore_module_list.txt Size: 1,130 bytes SHA1: 4907c6da467802a3b42a48f3716e9a88cd5cb920
LicReg.dat Size: 10,605 bytes SHA1: 6a350b39bf5dbd6560d2d0438bddad41b6455e3b
LicReg.exe Size: 96,816 bytes Ver: 2.0.0.4 SHA1: 0d236ac1394a97d35a67c63ec15e45a80f87db5b
LicReg_ja.txt Size: 707 bytes SHA1: 981af64897276c22867952f4972d9c29c6ee35e7
RawCapConv.exe Size: 208,928 bytes Ver: 2.0.0.131 SHA1: 32b6ec5d2f6649df4a47aedc476965433a8bdec4
RawCapConv_ja.txt Size: 1,869 bytes SHA1: 12086976f07abfc8d435abeee6c450c3cb2b07cd
RCStream.dll Size: 164,352 bytes Ver: 1.0.0.76 SHA1: 31266452f142cd7c856384945ffc410b2c9c8be9
readme.txt Size: 1,322 bytes SHA1: f8b7e31de7927309f7f3e03936374837906a94d9
Src16x10_Dest4x3.png Size: 40,081 bytes SHA1: 3b4f6332b8b3129ee351a9c96a9c4ac7f6f7a4cd
Src16x9_Dest4x3.png Size: 40,179 bytes SHA1: fcec824f4e95f7becf65bbabcc1a99c1470b99a1
unins000.dat Size: 88,148 bytes SHA1: b302f05525b137235aa65c52e8aed29bc1ec275e
unins000.exe Size: 1,199,680 bytes Ver: 51.1052.0.0 SHA1: b70fa30df88c1c4ab987a772615e9ca44d59376f
unins000.msg Size: 22,701 bytes SHA1: ab7961d64f8b22503c9c7ca4b335fa539b0278a3
UpdateChecker.exe Size: 93,696 bytes Ver: 2.0.0.0 SHA1: 221bd3663f4393b368ebf74d1a892f9379ddbe44
UpdateChecker.ini Size: 238 bytes SHA1: 796da23b4a505bf2ef370dc271d1a80585dff6e2
UpdateChecker_ja.txt Size: 190 bytes SHA1: 969913786a3497f3e448572f7810ee9814314928
UWPHelper.dll Size: 132,672 bytes Ver: 1.0.0.0 SHA1: 73adada2bf2e13b10e775e4e5fb64bb0144869b9
UWPHelper64.dll Size: 157,760 bytes Ver: 1.0.0.0 SHA1: 9e058ebd49070c9e826f954afb9a0994d4729a09
DxtoryCodec.dll 64bit Size: 2,606,144 bytes Ver: 2.0.0.132 SHA1: 7ef69696fe270d8bf353ead32bd58681ee61e5fe
DxtoryCodec.dll 32bit Size: 2,499,648 bytes Ver: 2.0.0.132 SHA1: cd610194e3ddceefa04bc0f28a5f2139fee0d615

[System Information]
CPU:        Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz
CPU Instruction Set: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AES
OS: Microsoft Windows 10 Pro x64
OSVersion: 10.0.10240
OSLanguage: 1033
ServicePack:
Memory0: ChannelA 8,589,934,592 bytes
Memory1: ChannelB 8,589,934,592 bytes
TotalMemory: 17,179,869,184 bytes
Total Physical Memory: 17,115,533,312 bytes
Available Physical Memory: 8,189,808,640 bytes
Total Page File: 20,759,187,456 bytes
Available Page File: 3,825,319,936 bytes
Total Virtual Memory: 2,147,352,576 bytes
Available Virtual Memory: 1,669,582,848 bytes
PerformanceCounterFrequency: 3322213 (0x32B165)
VideoCard: NVIDIA GeForce GTX 970 Memory: 4,293,918,720 Processor: NVxx DriverVer: 10.18.13.6451 DriverDate: 2016-03-06 19-00-00
VideoCard: NVIDIA GeForce GTX 970 Memory: 4,293,918,720 Processor: GeForce GTX 970 DriverVer: 10.18.13.6451 DriverDate: 2016-03-06 19-00-00
Display0: 1920x1080 32bits 60Hz
Display1: 1920x1080 32bits 60Hz
SoundDevice: HD Webcam C615 Manufacturer: Logitech
SoundDevice: NVIDIA High Definition Audio Manufacturer: NVIDIA
SoundDevice: NVIDIA Virtual Audio Device (Wave Extensible) (WDM) Manufacturer: NVIDIA
SoundDevice: Logitech G930 Gaming Headset Manufacturer: Logitech Headset G series
SoundDevice: USB Audio Device Manufacturer: (Generic USB Audio)
SoundDevice: Realtek High Definition Audio Manufacturer: Realtek
SoundDevice: NVIDIA High Definition Audio Manufacturer: NVIDIA
SoundDevice: XSplit  Stream  Audio  Renderer Manufacturer: SplitmediaLabs Limited
SoundDevice: VB-Audio VoiceMeeter VAIO Manufacturer: VB-Audio Software
SoundDevice: VB-Audio Virtual Cable Manufacturer: VB-Audio Software
SoundDevice: ManyCam Virtual Microphone Manufacturer: Visicom Media Inc.

[NVIDIA Info]
NVDriver: 364.51 r364_44
SLI Enabled
GPU0: GeForce GTX 970 Memory: 4096MB MemoryClock: 3505MHz BaseClock: 1114MHz BoostClock: 1253MHz
GPU1: GeForce GTX 970 Memory: 4096MB MemoryClock: 3505MHz BaseClock: 1114MHz BoostClock: 1253MHz

[Audio Device]
Speakers (XSplit  Stream  Audio  Renderer) - CoreAudioOut
Speakers (VB-Audio VoiceMeeter VAIO) - CoreAudioOut
Speakers (Yeti Stereo Microphone) - CoreAudioOut
Speakers (VB-Audio Virtual Cable) - CoreAudioOut
Realtek Digital Output(Optical) (Realtek High Definition Audio) - CoreAudioOut
Headset Earphone (Logitech G930 Gaming Headset) - CoreAudioOut
Speakers (Realtek High Definition Audio) - CoreAudioOut
Realtek Digital Output (Realtek High Definition Audio) - CoreAudioOut
Blue Yeti Microphone (Yeti Stereo Microphone) - CoreAudioIn, Volume 59
Microphone (ManyCam Virtual Microphone) - CoreAudioIn, Volume 53
Headset Microphone (Logitech G930 Gaming Headset) - CoreAudioIn, Volume 78
VoiceMeeter Output (VB-Audio VoiceMeeter VAIO) - CoreAudioIn, Volume 99
CABLE Output (VB-Audio Virtual Cable) - CoreAudioIn, Volume 100

[Video Codec 64bit]
FICV Codec FCC:ficv
Intel IYUV codec FCC:iyuv
Lagarith Lossless Codec FCC:lags
MagicYUV lossless v1.2rev0 (64 bit) FCC:magy
Microsoft RLE FCC:mrle
Microsoft Video 1 FCC:msvc
UtVideo Pro YUV422 10bit VCM FCC:uqy2
UtVideo RGB VCM FCC:ulrg
UtVideo RGBA VCM FCC:ulra
UtVideo YUV420 BT.601 VCM FCC:uly0
UtVideo YUV420 BT.709 VCM FCC:ulh0
UtVideo YUV422 BT.601 VCM FCC:uly2
UtVideo YUV422 BT.709 VCM FCC:ulh2
x264vfw - H.264/MPEG-4 AVC codec FCC:x264

[Video Codec 32bit]
Cinepak Codec by Radius FCC:cvid
FICV Codec FCC:ficv
Intel IYUV codec FCC:iyuv
Lagarith Lossless Codec FCC:lags
Logitech Video (I420) FCC:i420
MagicYUV lossless v1.2rev0 (32 bit) FCC:magy
Microsoft RLE FCC:mrle
Microsoft Video 1 FCC:msvc
UtVideo Pro YUV422 10bit VCM FCC:uqy2
UtVideo RGB VCM FCC:ulrg
UtVideo RGBA VCM FCC:ulra
UtVideo YUV420 BT.601 VCM FCC:uly0
UtVideo YUV420 BT.709 VCM FCC:ulh0
UtVideo YUV422 BT.601 VCM FCC:uly2
UtVideo YUV422 BT.709 VCM FCC:ulh2
VP60® Simple Profile  FCC:vp60
VP61® Advanced Profile FCC:vp61
x264vfw - H.264/MPEG-4 AVC codec FCC:x264

[Audio Codec]
Microsoft IMA ADPCM
MS-ADPCM
Microsoft CCITT G.711
Microsoft GSM 6.10
PCM
IEEE Float

[License Information]
License: Registered
Expire: Unlimited
LicVerify: 5543de4862dfddc02e58fb1c9ae1d1f81359c70f

[Additional Information]
Dxtory_log.txt: Available Size=3438
ErrorLog.txt: Empty

[Global Setting]
OptionFlag=

[Ignore List]
C:\Program Files (x86)\OBS\OBS.exe
C:\Program Files\OBS\OBS.exe

======================================================================

[Profile]
Name: Default
Path:

[Overlay]
Option: Left Bottom VidoeFPS WriteFileFPS RecordState
Color: Sleep FF00FF00, Active FFFFBC00, Movie  FF00FF00, ScreenShot FF00FF00

[Folder]
x D:  Speed: 131MB/sec  Free: 972,986,789,888 Total: 2,000,396,742,656 Format: NTFS
  C:\Users\darkp_000\Videos  Speed: 429MB/sec  Free: 23,780,048,896 Total: 240,054,693,888 Format: NTFS
  E:  Speed: 81MB/sec  Free: 15,942,094,848 Total: 250,057,060,352 Format: NTFS
  F:  Speed: 78MB/sec  Free: 42,643,431,424 Total: 1,000,202,039,296 Format: NTFS
SSFolder:

[HotKey]
MovieCapture: F10 (0x00000044)
PushToTalk: ` (0x00000029)
ScreenShotSingle: None
ScreenShotRepeat: None
ScreenShotAuto: None
ToggleStatus: None
MovieCaptureFrame: None
ScreenShotCaptureFrame: None

[Movie]
Clipping:
ClipMargin: 0,0,0,0
ClipSize: 0,0
Scaling: Percent 100% 0x0
Codec: UtVideo YUV420 BT.709 VCM, Quality 10000, KeyFrameRate 15, DataRate 0, 64bit
FrameRate: 60
Output: File AVI
Option: IncludeCursor

[Audio0]
Enabled: True
PushToTalk: False
Device: Headset Earphone (Logitech G930 Gaming Headset)
Codec: PCM
Format: PCM 48000 Hz, 16 bit, Stereo

[Audio1]
Enabled: True
PushToTalk: False
Device: Blue Yeti Microphone (Yeti Stereo Microphone)
Codec: PCM
Format: PCM 48000 Hz, 16 bit, Mono

[ScreenShot]
Clipping:
ClipMargin: 0,0,0,0
ClipSize: 0,0
Scaling: Percent 100% 0x0
HighSpeedLimit: 0
RepeatInterval: 1000
Format: PNG
JpegQuality: 97
Option:

[Advanced]
DataProcessingOption: SyncLock WaitForBuffer
HookOption:
ThreadCount: 4
ThreadMask: 0000000000000000
LimitedFPS: False
FPSLimit: 60
DelayHook: True
DelayHookTime: 5

======================================================================

[Profile]
Name: Tom Clancy's The Division
Path: F:\Steam\steamapps\common\Tom Clancy's The Division\TheDivision.exe

[Movie]
Clipping:
ClipMargin: 0,0,0,0
ClipSize: 0,0
Scaling: Percent 100% 0x0
Codec: UtVideo YUV422 BT.709 VCM, Quality 10000, KeyFrameRate 15, DataRate 0, 64bit
FrameRate: 60
Output: File AVI
Option: IncludeCursor SyncFPS

[Advanced]
DataProcessingOption: StableProcessing ForceCPUProcessing SyncLock
HookOption:
ThreadCount: 4
ThreadMask: 0000000000000FFF
LimitedFPS: False
FPSLimit: 60
DelayHook: True
DelayHookTime: 10

[LastUsingInformation]
DateTime: 2016/03/15 17:58:38
Version: 2.0.133
64bit Process
DeviceType: DX11
View0.Type=DX11
View0.CreateFlag=0
View0.FeatureLevel=D3D_FEATURE_LEVEL_11_1
View0.Format=DXGI_FORMAT_R8G8B8A8_UNORM
View0.GPUInfo=SLI
View0.Size=1920x1080
View0.HWND=0x0008046C
View0.WindowTitle=Tom Clancy's The Division
View0.ClassName=Tom Clancy's The DivisionClass

======================================================================
VerifyHash: ed2795468b6f48a4b8824a569a893726ca2fa575
« Last Edit: March 16, 2016, 07:23:03 am by darkpower »

Takedown

  • Monster
  • ****
  • Posts: 274
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #6 on: March 16, 2016, 12:57:52 pm »
If you want to see if it is the hard drive, you can record with x264vfw and set it to ultrafast :
http://www.bandicam.com/faqs/vfw-x264-xvid-divx-h264-codec/best-x264-codec-setting-recording.gif

That will ensure low cpu usage and low file size.  Don't bother turning on the zero latency setting as it isn't needed.  If that fixes the fps issue, then it is most likely the hard drive write speed.

Also, in Dxtory under Advanced settings turn on *only* these items :
- Enabled Multi Device Processing
- Delay hook  ( if you have game overlays )
- Limit Video FPS ( optional , on or off is your choice )


Finally, if nothing changes you can try the fix from this thread :
http://forum.exkode.com/index.php?topic=1927.0
« Last Edit: March 16, 2016, 01:03:54 pm by Takedown »
Using Windows 10 ?  Try the latest version first http://exkode.com/dxtory-downloads-en.html

Goth667

  • Noob
  • *
  • Posts: 1
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #7 on: March 18, 2016, 04:54:20 am »
Well "The Division" crashes for me as well if I have Dxtory running after some time without recording or anything.
If I close it down I wont crash anymore.
Also no entry in Windows Event Log when it crashes.

darkpower

  • Noob
  • *
  • Posts: 13
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #8 on: March 23, 2016, 02:22:04 am »
If you want to see if it is the hard drive, you can record with x264vfw and set it to ultrafast :
http://www.bandicam.com/faqs/vfw-x264-xvid-divx-h264-codec/best-x264-codec-setting-recording.gif

That will ensure low cpu usage and low file size.  Don't bother turning on the zero latency setting as it isn't needed.  If that fixes the fps issue, then it is most likely the hard drive write speed.

Also, in Dxtory under Advanced settings turn on *only* these items :
- Enabled Multi Device Processing
- Delay hook  ( if you have game overlays )
- Limit Video FPS ( optional , on or off is your choice )


Finally, if nothing changes you can try the fix from this thread :
http://forum.exkode.com/index.php?topic=1927.0

Did everything that was said here. And the game STILL is not running at a completely smooth 60FPS when Dxtory is recording. Not sure what this could be, but everything that has been told to do in the quoted post (including what to do about the 3D processing in the Nvidia CP) has been done now. No change. And the game STILL crashes, but ONLY when Dxtory is hooked to the game. Even disabling the Steam and Uplay overlays have no effect.

First, the drops. Mostly, they seem to be in the outside environment, and it's mostly right at the JTF base (where you go to upgrade all the wings). For whatever reason, Dxtory HATES this one street and absolutely refuses to record this at a consistent frame rate. The first attachment here is when Dxtory is not recording. It goes to near 120FPS. This is because I turned vsync off to see if that made any difference, and it does...until I hit record (the second attachment). It's 60FPS right then and there. What I would want, right?

But then comes the traveling on this street, and I sprinted to give an indication of what happens on this very street (and to some extent, the outside environment, but it's this street that you really see it happen). The third attachment shows the FPS dipping, and at times, it goes below 50. Last night, it dipped to 30FPS, but that might be because I had a four person team and one of them seemed to be Chinese (which meant ping rates might've played a role there). The fourth screenshot is showing that the game is indeed crashing. I'm trying to find where in uPlay it would have an error log to show what is causing the crash, but so far, I haven't been able to find the file that would show that information (which is kind of lazy on Ubisoft's part to not log that info; it might be in the Steam logs if uPlay doesn't have them).

I could try to see if any other recording software experiences the same issues as Dxtory does with this game. If it does not, then I might be able to safely confirm that The Division isn't playing nice with Dxtory. Not sure why it's this one street that it shows itself the most, and it's not to say that other areas of the game isn't having these same drops (this is just where I know for a fact that it does occur consistently enough to where I can show it).

Keep in mind, too, that I've went back and tried different codecs, settings, and even increased the recording FPS limit to 120 just to see if it fixed anything. It did in small doses, but that damn street again! Dxtory hates Penn Plaza, for some reason.

ClassifyLP

  • Veteran
  • ***
  • Posts: 241
    • ClassifyLP on YouTube
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #9 on: March 23, 2016, 07:40:07 am »
Have you tried to set everything to minimal and see if the dip still occurs? It might just be that the load is high in that area, causing the lower framerate. It's clearly not the harddrive, since that doesn't affect game fps.

Takedown

  • Monster
  • ****
  • Posts: 274
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #10 on: March 23, 2016, 12:29:39 pm »
Division got a patch today,  but I don't think it will solve this issue.  I've also seen posts on the Ubisoft forum that point to both the game or Dxtory as the problem, so it's hard to say who is at fault.   Given all that you've tried, I would keep / start using an alternative to capture Division for now.
« Last Edit: March 23, 2016, 12:31:53 pm by Takedown »
Using Windows 10 ?  Try the latest version first http://exkode.com/dxtory-downloads-en.html

darkpower

  • Noob
  • *
  • Posts: 13
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #11 on: March 24, 2016, 03:17:47 pm »
Have you tried to set everything to minimal and see if the dip still occurs? It might just be that the load is high in that area, causing the lower framerate. It's clearly not the harddrive, since that doesn't affect game fps.

Division got a patch today,  but I don't think it will solve this issue.  I've also seen posts on the Ubisoft forum that point to both the game or Dxtory as the problem, so it's hard to say who is at fault.   Given all that you've tried, I would keep / start using an alternative to capture Division for now.

These two do go together because I did try to record the game using Fraps in that very area, and sure enough, it dipped there, too. Though with Fraps, it's unclear whether the video itself took a hit or did just the in game FPS took a hit (I know both did in Dxtory, though, so I'm confident that Fraps didn't fair much, if any, better). This is not dipping below 50, but it's to 54, same as what Dxtory was doing in that area. To be fair, I'm not sure what codec Fraps uses, and I'm not sure if the codec is having anything to do with it (noticed that some other codecs were doing worse damage to the video FPS than UTV, what I usually use here). But it might be whatever the game is doing there. I did try OBS to see what it would do, but I don't have a FPS counter there to show if there are indeed any dips.

And as a final bit of fairness, these aren't terrible FPS drops. This is not like it's taking a nose dive to where it's making the game unplayable or anything like that (though I did say the other night that the game did dip to 30 FPS when I was recording, and I was blaming the PING issues from having someone from possibly the other side of the world in my team that night). However, it dipping to 50 is not something I was expecting this game to do, especially when I want the final product to run as smooth as possible. The crashes are indeed something that has to be addressed, but as we have no clue what's actually causing the crash to happen to begin with, there's no way to know if there is a connection. Though three people saying that Dxtory was at least running (recording more than likely) when the game seems to crash, and it happens to them on a consistent basis with it running, might be a sign that there could be some sort of conflict between the two, and it's unclear which program is at fault.

However, I'm going to try something. The HDD my game is currently on is running at 5200RPM (the recording drive is 7200RPM, for the record). I have a SSD that can go a ton faster (can't remember the exact RPMs, but it is my C drive, which Ubisoft is recommending you install the game on). I can reinstall the game on the SSD and see if that changes anything at all.

ClassifyLP

  • Veteran
  • ***
  • Posts: 241
    • ClassifyLP on YouTube
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #12 on: March 24, 2016, 04:48:03 pm »
I did try OBS to see what it would do, but I don't have a FPS counter there to show if there are indeed any dips.

There seems to be an option in Uplay for that: https://www.reddit.com/r/thedivision/comments/439dgf/show_fps/

(though I did say the other night that the game did dip to 30 FPS when I was recording, and I was blaming the PING issues from having someone from possibly the other side of the world in my team that night).

I don't know that much about netcode, but generally, the ping of another player should not affect your performance in any way.

I have a SSD that can go a ton faster (can't remember the exact RPMs, but it is my C drive, which Ubisoft is recommending you install the game on). I can reinstall the game on the SSD and see if that changes anything at all.

SSDs don't spin, they don't have an RPM metric. To really compare storage, you can use data throughput (various settings) and latency.

chronosek

  • Soldier
  • **
  • Posts: 54
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #13 on: March 24, 2016, 09:44:08 pm »
It is only speculation, but ... - If you have large framerate drop, but still record full fps i could guess that game is cpu intensive and it is a cpu problem, first i would try set 2-3 core in UTVideo codec , and set manually lower proiority of dxtory in process manager. Usually if game is not good optimized then main loop would use only 1 core, and becuase you have cpu with ht - if all cores are used (UTVideo default use all cores) then main loop can use only 70% of core (that HT of cpu works) and that 70% is used for dxtory too, so main loop could use only like 40% , that why you could have only 40% of framerate when dxtory is used (and thats why sometimes i5 are better than i7) You could try assign game and dxtory to different pair of cores too to check that. But it is only a speculation, maybe you have SLI and it is driver problem (disable SLI and check it)
« Last Edit: March 24, 2016, 09:49:02 pm by chronosek »
Old Comp Spec: Zalman T4 Mini Tower, Chieftec 750W PS, Gigabyte GA-Z97M-D3H mobo, Intel i7-4790k @4.8GHz proc, Corsair h80i cooler, GoodRam 32GB PC3-12800 ddr3, Gigabyte Geforce 980 GTX 4GB gddr5, 2x 512GB Samsung SSD 840 pro, SoundBlaster ZxR sound, beyerdynamic 990DT pro, Windows 10 Pro x64

darkpower

  • Noob
  • *
  • Posts: 13
Re: Issues with The Division: Game Crashes and FPS dips
« Reply #14 on: March 25, 2016, 12:42:42 am »
It is only speculation, but ... - If you have large framerate drop, but still record full fps i could guess that game is cpu intensive and it is a cpu problem, first i would try set 2-3 core in UTVideo codec , and set manually lower proiority of dxtory in process manager. Usually if game is not good optimized then main loop would use only 1 core, and becuase you have cpu with ht - if all cores are used (UTVideo default use all cores) then main loop can use only 70% of core (that HT of cpu works) and that 70% is used for dxtory too, so main loop could use only like 40% , that why you could have only 40% of framerate when dxtory is used (and thats why sometimes i5 are better than i7) You could try assign game and dxtory to different pair of cores too to check that. But it is only a speculation, maybe you have SLI and it is driver problem (disable SLI and check it)

For the record, I did try the SSD, and it didn't provide THAT much of a difference. I could see a slight improvement, but it was only that, and very slight (maybe even unseen) difference. Also, until that night, I didn't even know you could have more than three members in a team for The Division. That was a shock to me, too.

But I could try to limit the cores that this codec uses. I could also see if I can grab a program that will tell me what the game is doing to each of my computer components (TotalBiscuit uses something for his Port Reports, but I'm not sure what the program is, if any, he's using) and see what could be done based on that. I do have SLI going (two 970s), so that could be a thing, too. Ubisoft is known for not being nice to SLI machines.

I had watched TB's video on the game (https://youtu.be/V8Vgl448Ccg), and from the numbers he was displaying and what he was saying it was doing, the games engine, Snowdrop, has a way to display the textures it does in the FPS it does, which is to spread core usage to all the cores you have. In other words, if you had 4 cores, it would use all 4 cores, and if you had 6 cores, it would use all 6 cores. It's just how the engine is designed to work. It'll use all the cores available to it. Which could be causing the conflict: Dxtory wants to use a specific amount of cores for it, but the game is trying to take the core for its own purposes because that's just what it's being told to do by the engine. The one way I could see to fix this is to have the game only use a set amount of cores, but I don't know how to get the game be tricked into only using 4 out of the 6 cores (or however many amount of cores you have: I currently have 6 cores and 12 logical processors), if that's even possible, or if that's even necessary.

I can try your suggestions later (don't have time right this second) to see if anything changes.