Hey there,
Not sure what happened - I'm using the latest CentrED, and when I try to open up my map files to edit them I receive a message "Invalid Bit Index: 16471"
Which tells me it might corrupt data to continue, or cancel to quit.
I can work on my map with older versions of CentrED, and I can move freely about on my map -- it's something that this new version just doesn't like.
Anyone know what could be causing this?
When and where exactly does this error come? Do you mean CentrED or cedserver? At what stage (when loading, when connecting, ...)? Which operating system (Linux, Windows)?
sorry!
I'm using the win32 client. Server seems to perform as if nothing were wrong. The error occurs when I try to view anything but water. If I set the coordinates to 1,1 (somewhere in the ocean) I can move just fine. But if I view any landmass, it gives me the invalid bit index error. Version 0.4.1 works just fine. Only with the newest version does it have issues.
You may have different files than the server. Apparently the map contains statics >= $4000 but your client only knows about statics < $4000. You probably don't have the correct tiledata, animdata and/or art files.
I figured it out by process of elimination - the animdata.mul had, somehow, been replaced with a blank one. This was causing the bit index error -- not sure why! I replaced the animdata with the default.
Wham, bam, thank you ma'am. It works!
I should probably add some more validation there to give better error messages. I'll add it to the bug tracker.
Thanks for reporting (and happy that you could solve it :-)).
Hi!
(At first, sorry - my english is not the very best. :/)
I have a similar problem (Windows 7). With the older version 0.6 there isn't the error, but here the Virtual Layer doesn't work (Access violation . Press ok... press cancel..) and this is why I prefer 0.6.1.
The bug says (at Centred, not the ced-server): "Invalid bit index: 37024 (I had another numbers here, too, for example: 36896, 36992,36982,...). Press ok to ignore and risk data corruption. Press cancel to kill the program."
Ok = Nothing works, but I can choose another point of the map - if I do so, a restart begins at another area. The error comes back, if I switch to the error-area.
Cancel = The program shuts, but with a restart the error is still there.
I had this bug several times at completely diffrent regions of my map (iceland, orcland, dungeon,...).
The Invalid bit index numbers changes with every error-region. One time I finessed the problem. It was at the said Iceland. A almost clean area, only snow, no buildings, very few decoration - I start my 0.6 Centred and analyzied the problem-area. I found something strange: ~10 staticed animations of hair (Don't know how they came there - they were never seen on the gameserver).
I removed the things and look: The error wasn't there anymore with 0.6.1.
The other areas with the error are too crowded with decoration and buildings to find anything.
I hope this problem can be solved.
Greetung, Neferu
€: My animdata is ok!