Join The Community
TNM Discord
@tnm7sim
tnm7sim
TNM 3:16 Forums
FORUM HOME > TNM > Help
Problem with Vizualizer
| Jazz | Posted on 08/29/05 at 04:46:42 Hi there. For some reason, two pictures which I've assigned to wrestlers won't show up in the visualizer window during a wrestling match. The others work fine. One of the two pictures in question used to work, now it won't. Any advice? |
| Jazz | Posted on 08/29/05 at 07:56:49 Further to my earlier post, some other (unassigned)pictures don't appear in the visualizer wizard, depite being in the correct folder. Both of these problems have occurred since I upgraded to TNM7SE Build 4 Beta 1d. |
| Oliver Copp | Posted on 08/29/05 at 12:45:21 I suspect there might be a problem with the INDEX.DAT file in the MEDIA folder. Have you ever edited it manually? If you want, you can send it my way and I'll check it out. |
| Zedja | Posted on 08/29/05 at 13:51:45 My guess about the unassigned pictures not showing up is that you've assigned the pictures to one wrestler and then renamed that wrestler. This way the picture is still taken up by the old name, despite it no longer being in the database. Or that the picture isn't a jpg. If I remember correctly it only works with jpg. |
| Tommy Brownell | Posted on 08/29/05 at 17:51:10 I'd say there's a chance it's something other than that. I've noticed that several of the pictures I've added after a certain point seem to only show up from time to time, and tag team pictures almost never show up for me now. When I DID crack into the index.dat, I noticed that there were several gaps in the listings, plus severan entries repeated. I figured it was the result of TNM crashes and having to close Visualizer manually a lot. Cleaning it up (deleting dupes and gaps) HELPED...but not dramatically. |
| Oliver Copp | Posted on 08/29/05 at 22:28:50 See - that is the funny part: only the Visualizer Image Wizard *writes* to the INDEX.DAT file, and it always does it in line pairs: - first line: entity name - second line: image names In every case of a corrupt INDEX.DAT I've seen, there have either been single entity lines, single image name lines or single blank lines. This technically can't be TNM's fault because it *always* writes lines to the file in pairs of two. Is there anybody out there who has *never* manually touched the INDEX.DAT file who has been having this trouble? |
| Tommy Brownell | Posted on 08/29/05 at 22:56:17 What I'm suggesting isn't that TNM's writing the info incorrectly...but that the index.dat is being corrupted when ctrl+alt+delete is having to be used to shut TNMGS.exe whenever TNM doesn't close right. Incidentally, I *seem* to have fixed the problem. Most everyone who wasn't showing up, were either in a batch of data with their names in lower case, or were added after those were. Well, when I changed all the wrestlers names back to uppercase first letters in their names and saved it, viola...wrestlers were appearing on the visualizer again. |
| Zedja | Posted on 08/29/05 at 23:06:20 The Vizualizer can actually screw things up on it's own. Especially if you don't have a wrestler checked but are on one of the letters and accidently double click a picture. What happens is that the picture disappears from the available list, but is assigned to a nothing. This also writes a single line in the Index.dat. Or should I say three. As it added a blank row before and after.. Yes I've been inside the file with notepad. As long as you don't save anything, the file won't get corrupted. But I have removed all the info from the file on multiple occations when something has just gone wrong with it. Mainly while I was trying to get the hijinks out of it or when I renamed a wrestler while forgetting to remove the picture first. |
| Snabbit888 | Posted on 08/30/05 at 01:58:49On 08/29/05 at 22:28:50, Oliver Copp wrote:See - that is the funny part: only the Visualizer Image Wizard *writes* to the INDEX.DAT file, and it always does it in line pairs:I haven't used the Visualizer much in awhile until recently, but I had that problem awhile back when I used it. I remember it was working funny for Rob Conway, but that's all I remember. And I don't mess with the files... I've screwed up many a circuit that way. :) |
| Oliver Copp | Posted on 08/30/05 at 09:41:17 Zedja - thank you for this piece of info. I wasn't aware of that. However, I just tried and what it does is put a blank line where normally the wrestler name is... still two lines for the record. What I did was first select a letter, then double-click a stray image. Then I selected Hardcore Holly, added an image to his record and exited. The INDEX.DAT file got the following four new lines: " 7a.jpeg Hardcore Holly aaniknew.jpeg " Can you reproduce it actually putting THREE lines in there? If so, how? The only way this could happen is if either the wrestler name added or the image added had a newline character inside (which would then show up in the file as taking up two lines). The code that actually writes to the file writes two lines -one with the name variable and one with the images. Like I said, that's a fact and only defective data as outlined above could cause a third line to be added. Even doing some more shenanigans gave me the following lines in INDEX.DAT: " 7a.jpeg|aanduke2.jpeg|benoit.jpg|arena17.jpeg|bookert.jpg Hardcore Holly aaniknew.jpeg and aanfnitr.jpeg " Read that: - 7a.jpg et al assigned to (no name) - aaniknew.jpeg assigned to Hardcore Holly - aanfnitr.jpeg assigned to a tag team consisting of two non-existing wrestlers Still, that doesn't explain the screwing up you mentioned, Zedja. I'll post a new version of the Visualizer Image Wizard by the time you read this which won't allow assigning of a stray image to anything but a selected entity. Thanks for that tip! Tommy - I'll reiterate my point: the file can't get screwed up, even by a crash, because the Visualizer itself only READS from the file and doesn't WRITE to it. The only program that WRITES to it is the Visualizer Image Wizard. A file open for READING can't be OVERWRITTEN on a crash. It simply isn't possible. |
| Zedja | Posted on 08/30/05 at 10:11:12 Then my recollection of it may be scewered since that happened a while ago. Also is there a way to make it so that if you change the name of the wrestler, the picture of said wrestler either follows over to the new name or are freed since the old name isn't in the database anymore? This has also been a reason for going into the index.dat in the past. EDIT: I just remembered something.. I don't think I had anything assigned at all. I exited a letter-menu by pressing the "minus" and then accidently doubleclicked. What happened then was that the picture actually went to the TOP of the list, and not the bottom as it usually does. |
| Oliver Copp | Posted on 08/30/05 at 10:25:18 Just tried that with the version - and it doesn't add the image at all anymore. Thanks for helping find that bug... now if we only knew how the blank single lines get in there :). From the program, it is completely illogical. |
| Jazz | Posted on 08/30/05 at 23:41:47 The pictures that don't show up in the visualizer wizard are all of stables. Yesterday I assigned some more pictures to stables and when I checked later they had vanished without trace. |
| Jazz | Posted on 08/31/05 at 02:24:03 This morning I imported a wrestler with the ame name as a stable with a missing picture. The picture miraculously resurfaced, assigned to the wrestler, who is not part of the stable. I have renamed the wrestler, which caused the picture to vanish again and have assigned him a picture of him. It appears that the stables part of the Visualizer Image Wizard is not recognizing pictures once they've been assigned to stables. I've upgraded to TNM7SE Build 4 beta 1e, but the two pictures that won't show up in the visualizer window still won't show up. |
| Jazz | Posted on 08/31/05 at 03:36:16 I'm now also having problems with pictures unassigning themselves from wrestlers in the Vizualizer Image wizard. I had this problem a while ago, but it seemed to sort itself out, now it's reared its ugly head again. Also, one picture has started jumping from where I assigned it to a different wrestler. I'm sending you a copy of my index.dat file, Oliver, so you can check it out. |
| Zedja | Posted on 08/31/05 at 07:55:22 Even if you change the name of a wrestler, the picture are still used on it's old name, despite it no longer being in the database. Also, make sure the pictures are JPG's. |
| Jazz | Posted on 09/03/05 at 05:04:29 Thank you very much Oliver - those two pictures that weren't showing up in the vizualizer before are showing up now that my index.dat file has been fixed, and pictures appear to have stopped unassigning themselves. Unfortunately pictures of stables are still vanishing without trace after being assigned. Zedja, I've found that bmp (bitmap) images work just as well as jpgs. I don't know about GIFs - I don't have any. |
| Zedja | Posted on 09/03/05 at 10:12:19 Ah, I have never tried them since I think they take up too much space. |
| Jazz | Posted on 09/09/05 at 01:06:30 I've found that If I unassign a picture from a wrestler etc and don't assign a new one to them the data in the index.dat file gets screwed up. It appears that becacause there is no picture between this wrestler and the next one the file thinks the next wrestler is the picture for the first wrestler and accordingly the first letter of it and subsequent names become lowercase. Still no luck with pictures of stables vanishing after being assigned. Any suggestions? |
| triad4evr | Posted on 09/12/05 at 05:40:54 Just to respond to an earlier question, Oliver, I have _never_ even so much as opened up the Images.DAT file and early this year (I think) I had the same problem these guys are listing- images wandering off, inability of newly assigned images to "stick" to the guy I assign them to, etc. You told me back then to delete Images.DAT and start over (I think that was you, I can't remember for sure) and I did. I reassigned everyone from scratch and its never appeared since. But it _did_ happen back then, and I never meddled with the DAT file. Just FYI. |
| Oliver Copp | Posted on 10/01/05 at 12:38:41 Thanks, Jeff! |