search

thegooglecodearchive / wowmodelviewer

Automatically exported from code.google.com/p/wowmodelviewer
0 stars 0 forks source link

Failed to read TOC number #261

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Worked fine a while ago, then suddenly it "Failed to read TOC number".
Same result in r614 as r636. Doesn't load either live WoW patch or PTR 4.3 for 
me.

Original issue reported on code.google.com by holmberg.simon@gmail.com on 25 Oct 2011 at 3:09

Attachments:

GoogleCodeExporter commented 9 years ago 
Woah! What's this
16:59:52: Opening enGB\wow-update-enGB-13914 - Copy.MPQ (Partial)
doing there?

Did you (or anyone else) modify this MPQ file?

Remove it (you can just put it in a new directory or just delete it) and try 
again.

Original comment by sephirot...@gmail.com on 25 Oct 2011 at 8:27

GoogleCodeExporter commented 9 years ago 
Yeah I noticed. Happened when I tried removing that file after some tiresome 
googling.
No difference.

Original comment by holmberg.simon@gmail.com on 25 Oct 2011 at 9:55

GoogleCodeExporter commented 9 years ago 
Same issue here, and this is my first time loading the program on a new WoW and 
Windows install.

Original comment by alexmohr...@gmail.com on 5 Nov 2011 at 3:46

GoogleCodeExporter commented 9 years ago 
alexmohr1990, lways provide us log.txt in order to give us more information 
about problem.
holmberg.simon, can you please provide us your new log.txt file after cpied mpq 
suppress ??

Original comment by jeromn...@gmail.com on 5 Nov 2011 at 9:04

GoogleCodeExporter commented 9 years ago 
Yeah, well it randomly works now. Haven't done anything since.
When the error happened "Loaded Content TOC:" contains random gibberish, like 
in the log I posted above: "Loaded Content TOC: vt.ch._m".
When I had the problem I tried removing all the mpq's but one, but no matter 
which one I loaded there was the same error.

Original comment by holmberg.simon@gmail.com on 5 Nov 2011 at 10:21

GoogleCodeExporter commented 9 years ago 
If you don't find what could be causing this, it would be nice if there was 
some way to manually input which version to use. After seeing the error 
message, another dialog comes up which asks something like "Are you sure you 
want to cancel? (yes/no)", but it doesn't matter what you choose, it just gives 
up.

Original comment by holmberg.simon@gmail.com on 5 Nov 2011 at 10:24

GoogleCodeExporter commented 9 years ago 
It's a general problem in current WMV architecture, it's difficult to use 
something else than latest up to date wow client version. We are currently 
working on doing this in a better way (in v0.8.0.0 we have planed to manage 
several WoW version - latest + ptr for example - direclty inside WMV interface).

Original comment by jeromn...@gmail.com on 7 Nov 2011 at 11:06

GoogleCodeExporter commented 9 years ago 
This demand can be followed here now : 
http://apoklipse.org:8080/browse/WMV-99

feel free to let us up to date with this problem (still occurs with latest 
version, etc.)

Original comment by jeromn...@gmail.com on 22 Nov 2011 at 4:06