Aller au contenu

Photo

Toolset error after reinstal


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

#26
rjshae

rjshae
  • Members
  • 4 478 messages

there must be a disk-checking program out there

else ... GoG

 

I've tried the various approaches suggested by Microsoft and scanned the disk multiple times for corruption, but... it didn't help any. Apparently it's a known issue with Windows 8.1 that it can cause certain app loads to fail. Another fine PoS product from Microsoft. Grr...

 

Yeah, I'll probably have to go with GoG. Ah well.



#27
andysks

andysks
  • Members
  • 1 645 messages

I had disks too, but I'm using windows 7. I just bought the GoG version too because people said it's really stable and I wanted to have it. Plus, it's really cheap for 4 games. Now, I don't know if my bugs occurred because of copy pasting, or because GoG installs somewhere else than the disks, but I'm just happy it works. I also never had, or played the MoW, so it was one more motivation to buy it from GoG. 



#28
rjshae

rjshae
  • Members
  • 4 478 messages

Buying it from GoG reminds me of Kay's line from Men in Black: "guess I'll have to buy the White Album again...". This will be the fourth time. Ah well.



#29
andysks

andysks
  • Members
  • 1 645 messages

I guess problems are not over yet. Opening a module was only step 1. I'm glad it got solved, but there is more to it. I was going to work on it today, and I opened an area. I can also open scripts and placing blueprints works well. Conversations are not behaving though. I get various errors. When I double click on one to open, it doesn't and toolset hangs. I try to press alt+tab, and the moment I press alt I get the error. Different one for each conversation, however somehow similar. Here are 3 examples.

 

2015-09-08%2012_29_41-NWN2%20-%20Toolset

 

2015-09-08%2012_30_44-NWN2%20-%20Toolset

 

2015-09-08%2012_30_11-NWN2%20-%20Toolset

 

Any ideas on this one?



#30
kevL

kevL
  • Members
  • 4 052 messages
might be .NET installation (doubt it)
could be Toolset installation (maybe - rule out by opening dialogs in other modules, with & without their own custom.Tlk's)

or perhaps your custom.Tlk references in conversations got mismatched somehow -- i think the likely suspect is custom.Tlk, although the problem might be in the conversation files themselves, that reference custom.Tlk


in any case, looks like low-level stuff, that might require de-installing/cleaning-out & re-installing something or other.

#31
andysks

andysks
  • Members
  • 1 645 messages

It was 2da again. For whatever reason, the 2da files in my campaign folder keep getting corrupted. I replace them with my healthy backups, and everything works. After a day or so, problems again. This time, it was the stringtokens.2da which was preventing the convos from opening.

 

I'm starting to think it could be campaign folder size related?



#32
kevL

kevL
  • Members
  • 4 052 messages
here's an idea

select all .2da's in the Campaign folder and mark them read only

#33
andysks

andysks
  • Members
  • 1 645 messages

I did it on one that was giving an "unknown file type" on tlk edit, and it still does when it's set to read only. Or you meant do it on the healthy ones so that it might not happen again :).



#34
kevL

kevL
  • Members
  • 4 052 messages
try this when everything is *working properly*, that is you've refreshed any maladjusted .2da's from your backup etc. -- so no errors show and dialogs open fine.

... close the toolset ... in Windows Explorer, select all 2da's in the campaign folder (those are the ones that go south?) and right-click, change their Properties to "Read Only".

Then act like everything is normal (remember you can't edit the .2da's though). Assumedly the toolset is going to try to change a 2da file, which *would* necessitate another revert-to-backup. But since they're all marked "Read Only" I suspect your computer is going to launch all missiles throw an error about being unable to change the file.

Exactly when/if that happens, could be a clue ....

#35
andysks

andysks
  • Members
  • 1 645 messages

Further clue:

 

As I selected all of them, the ready only was blue, meaning that some are already ready only. So I checked them one by one. Some, spells.2da, tiles.2da, placeables.2da and one more which I forgot now, are blocked by security. "This file came from another computer and might be blocked to help protect this computer". And, here is the most interesting, stringtokens.2da is already set to ready only... I don't remember ever setting this, and why would I. Even my backuped one is not ready only. Anyway, I unchecked it and the problem was still there though.

 

One more clue (.NET maybe related?): I cannot rescale placeables, not even with my healthy 2das. Instead of 1:1:1, I see 1,1,1. If I change it, it just reverts to 1,1,1 (without an error).

 

What you suggested: All 2das read only, same thing happens. Error on opening conversation.



#36
kevL

kevL
  • Members
  • 4 052 messages
well, might as well select all files and uncheck read-only. Sounds like Windows Big Brother edition is half the culprit.

One more clue (.NET maybe related?): I cannot rescale placeables, not even with my healthy 2das. Instead of 1:1:1, I see 1,1,1. If I change it, it just reverts to 1,1,1 (without an error).


if you open some other module is it the same? You might want to find some sort of .NET checker, plus download and run CCleaner's registry checker.

#37
andysks

andysks
  • Members
  • 1 645 messages

Alright. This is what I got from a .net checker software.

 

Spoiler

 
No idea what that means, but I see that I got 4.0, and 3.5 SP. I thought, 3.5 SP might not be what I want, so I went ahead and tried to install this https://www.microsof...tion.aspx?id=21
However, the install wouldn't run after the "I accept blah, blah".
 
I read that windows 7 come with 3.5, and perhaps this is the reason. Is this true?

 

Edit: Yes, the scale thing is happening on all modules.



#38
Tchos

Tchos
  • Members
  • 5 030 messages

I cannot rescale placeables, not even with my healthy 2das. Instead of 1:1:1, I see 1,1,1. If I change it, it just reverts to 1,1,1 (without an error).

 

Mine always uses commas for values like those.  It has never shown 1:1:1 for me.



#39
andysks

andysks
  • Members
  • 1 645 messages

Ah, ok then false alarm on that front. Do you rescale by changing the numbers though Tchos, or the comma version uses another way I don't know?



#40
Tchos

Tchos
  • Members
  • 5 030 messages

Yes, I can rescale by changing the numbers, including cut and paste numbers with commas, or I can type a whole new set with commas.  Another way to rescale is to hold Ctrl and use the mouse wheel while the object is selected.



#41
kamal_

kamal_
  • Members
  • 5 238 messages
For what it's worth I ran into those types of errors with Path of Evil. Never resolved them, they're still there if you open the modules in the toolset. It didn't affect anything I could determine, though there has to be some sort of effect.

#42
andysks

andysks
  • Members
  • 1 645 messages

kamal, I'm close to making this decision myself and close this thread. I don't think I will modify any more 2da files so far into the work, and they break one more time, I just replace them again so that I can work. It's not a solution, but I think there's only so much one can do. Perhaps later I figure it out. The rescaling is bothering me though.

 

Edit: Rescaling works. Miracle? What's going on B) !?



#43
rjshae

rjshae
  • Members
  • 4 478 messages

I've had issues with scaling placeables, but it seems to be related to Windows 8/8.1 and/or my graphics card. I'll apply a new scale, and... nothing happens. Usually when I close and re-open the area, the scaling has been properly applied. Other times the scaling will suddenly work spontaneously. There's a similar issue with tinting. I was wondering if there was some type of caching going on.



#44
kevL

kevL
  • Members
  • 4 052 messages

Alright. This is what I got from a .net checker software.


.net 2.0 or (better) 3.5 is the correct one for the Toolset.

#45
andysks

andysks
  • Members
  • 1 645 messages

One last time writing here, to say that everything seems normal now. I think the conversation problem was due to the stringtokens.2da. So when at first I found out that the a module was not opening because of the tiles.2da, I replaced only them. Then, when I wanted to write a convo, it showed more problems. So replacing all 2da files with the backup ones solved all problems. Now, whether it was corruption caused by the copy paste, or the format or a campaign link different after the format, I don't know. But the corruption seemed to be exclusive to 2da files. 

 

Thanks for the help :). Back to building.