Fulqrum Publishing Home   |   Register   |   Today Posts   |   Members   |   UserCP   |   Calendar   |   Search   |   FAQ

Go Back   Official Fulqrum Publishing forum > Fulqrum Publishing > IL-2 Sturmovik: Cliffs of Dover > Technical threads

Technical threads All discussions about technical issues

Reply
 
Thread Tools Display Modes
  #1  
Old 05-17-2012, 10:33 AM
VO101_Tom's Avatar
VO101_Tom VO101_Tom is offline
Approved Member
 
Join Date: Jul 2010
Location: Budapest, Hungary
Posts: 799
Default

Quote:
Originally Posted by Sternjaeger II View Post
guys, I'm doing this installation for a friend of mine on his iMac with a Windows 7 64bit partition...
Hi. The problem is that the video signal is delayed by more than 2 seconds at start (with weaker cards), and the Win turn off the driver (2 sec Win default). This registry setting (thanks to easyhomewin) increases this delay to 12 seconds. I have no idea how the MAC default, and i have no clue how to increase. Maybe you should ask some MAC forums.

Explanation of the PC reg key:
Code:
TdrDelay

Specifies the number of seconds that the GPU can delay the 
preempt request from the GPU scheduler. This is effectively 
the timeout threshold. The default value is 2 seconds. 

KeyPath   : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers
KeyValue  : TdrDelay
ValueType : REG_DWORD
ValueData : Number of seconds to delay. 2 seconds is the default value.
__________________
| AFBs of CloD 2[/URL] |www.pumaszallas.hu

i7 7700K 4.8GHz, 32GB Ram 3GHz, MSI GTX 1070 8GB, 27' 1920x1080, W10/64, TrackIR 4Pro, G940
Cliffs of Dover Bugtracker site: share and vote issues here

Last edited by VO101_Tom; 05-17-2012 at 10:35 AM.
Reply With Quote
  #2  
Old 05-17-2012, 11:28 AM
Sternjaeger II Sternjaeger II is offline
Approved Member
 
Join Date: Apr 2011
Posts: 1,903
Default

Quote:
Originally Posted by VO101_Tom View Post
Hi. The problem is that the video signal is delayed by more than 2 seconds at start (with weaker cards), and the Win turn off the driver (2 sec Win default). This registry setting (thanks to easyhomewin) increases this delay to 12 seconds. I have no idea how the MAC default, and i have no clue how to increase. Maybe you should ask some MAC forums.

Explanation of the PC reg key:
Code:
TdrDelay

Specifies the number of seconds that the GPU can delay the 
preempt request from the GPU scheduler. This is effectively 
the timeout threshold. The default value is 2 seconds. 

KeyPath   : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers
KeyValue  : TdrDelay
ValueType : REG_DWORD
ValueData : Number of seconds to delay. 2 seconds is the default value.
thank for this, I'll give it another shot later. It's defo not a Mac issue per se though, since the hardware is Apple of course (with Intel processor), but is running Windows.
Reply With Quote
  #3  
Old 05-17-2012, 12:20 PM
VO101_Tom's Avatar
VO101_Tom VO101_Tom is offline
Approved Member
 
Join Date: Jul 2010
Location: Budapest, Hungary
Posts: 799
Default

Quote:
Originally Posted by Sternjaeger II View Post
... the hardware is Apple of course (with Intel processor), but is running Windows.
I understand. Then no problem, the procedure is the same, what has been written (#37).
__________________
| AFBs of CloD 2[/URL] |www.pumaszallas.hu

i7 7700K 4.8GHz, 32GB Ram 3GHz, MSI GTX 1070 8GB, 27' 1920x1080, W10/64, TrackIR 4Pro, G940
Cliffs of Dover Bugtracker site: share and vote issues here
Reply With Quote
  #4  
Old 05-17-2012, 05:40 PM
HR_Naglfar HR_Naglfar is offline
Approved Member
 
Join Date: Feb 2011
Posts: 69
Default

I've had this problem with a GeForce 9600GT. I spent a lot of time editing windows registry trying even 120 seconds delays without solving the problem.

So finally I just deactivated this fantastic TDR thing. If someone still have this problem even with greater delays, just create a new DWord in the same location (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\GraphicsDrivers), named TdrLevel, with a value of 0. And don't forget to reboot your PC before trying if it worked.

PS: It should work with just that, but for some reason I had to put this DWord also in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Gr aphicsDrivers, and HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Gr aphicsDrivers, and finally it worked.
Reply With Quote
  #5  
Old 05-17-2012, 05:50 PM
DroopSnoot DroopSnoot is offline
Approved Member
 
Join Date: Feb 2012
Posts: 211
Default

Did you use a 64bit Dword or a 32bit for those ControlSets?
Reply With Quote
  #6  
Old 05-17-2012, 06:40 PM
HR_Naglfar HR_Naglfar is offline
Approved Member
 
Join Date: Feb 2011
Posts: 69
Default

Quote:
Originally Posted by DroopSnoot View Post
Did you use a 64bit Dword or a 32bit for those ControlSets?
32 bits DWord.

I think it has nothing to do with 64 or 32 bits OS, I have W7 32 bits but still can create 64 bits QWord in the registry. Also here doesn't say anything about using QWord in 64 bits OS: http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

Anyway if it doesn't work with DWord you can try using QWord, I don't think it will break anything
Reply With Quote
  #7  
Old 05-18-2012, 07:38 AM
DroopSnoot DroopSnoot is offline
Approved Member
 
Join Date: Feb 2012
Posts: 211
Default

Well it worked for him too so thank-you but sadly his fps is 2 so its impossible to play
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 09:17 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2026, Jelsoft Enterprises Ltd.
Copyright © 2007 Fulqrum Publishing. All rights reserved.