Aller au contenu

Photo

Toolset Settings Help


  • Veuillez vous connecter pour répondre
6 réponses à ce sujet

#1
BartjeD

BartjeD
  • Members
  • 249 messages
I accidentally changed the rendering time setting in the Toolset options to a rather large number and now the toolset crashes upon startup.

I have tried several times to reinstall but it still doesn't work.
It fails completely when the loading bar reaches "starting rendering".

Also, i've tried to remove all registry indexes with Obsidian, NWN or neverwinter as well as deleting all related files.

Nothing works so far, does anyone have any advice or ideas?

Thanks in advance!
Posted Image

#2
_Knightmare_

_Knightmare_
  • Members
  • 643 messages
Where/how did you make that change?

#3
BartjeD

BartjeD
  • Members
  • 249 messages
In the toolset options menu, unfortunately I can't acces it anymore because it crashes when it reaches 'starting rendering' upon launch.

I also strongly suspect NWN2 doesn't delete this info upon uninstallation :(

Otherwise I don't know why it keeps crashing, everything is up to date for it etc..

Modifié par BartjeD, 13 octobre 2010 - 12:54 .


#4
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
There is a forum specifically *FOR* using the Toolset:

http://social.biowar...egory/165/index




#5
I_Raps

I_Raps
  • Members
  • 1 262 messages
There are probably more settings in your system's Registry you need to edit.

Here's something similar to your problem  http://www.thieves-g...php/t-1011.html 
They think it was a Securom issue.  But they never found out.

Maybe check this out:  http://www.tweakguides.com/TGTC.html 
I'd look at the free version and see if it's likely to help.

Modifié par I_Raps, 13 octobre 2010 - 06:00 .


#6
I_Raps

I_Raps
  • Members
  • 1 262 messages
I see elsewhere you found your answer.  A lot better resolution than that other guy had, too.  Posted Image

#7
BartjeD

BartjeD
  • Members
  • 249 messages
Yeah and it worked, thanks for your reply though! :)

I'm happy I didn't have to mess with the registry again this time. It can cause some real strange things doing that.