Loading a character in the BD with -relight. In no particular order.
WARNING! Object 'spikes_01' is not closed!
WARNING! Object '_s_stairs_01' is not closed!
WARNING! Object 'spikes_02' is not closed!
WARNING! Object 'spikes_04' is not closed!
WARNING! Object 'spikes_06' is not closed!
WARNING! Object '_s_sigil_03' is not closed!
Do unclosed objects cause memory leaks?
Duplicate effect 'x_obj_spire' found!
Duplicate effect 'x_obj_quad' found!
Duplicate effect 'x_obj_star' found!
what trouble do duplicate effects cause if any?
Bad UV coordinates for polygons in this thing!
[node: world,sector(name=bdoorsin),meshobj(name=Bridge),params]
Bad UV coordinates for polygons in this thing!
[node: world,sector(name=bdoorsin),meshobj(name=Bird),params]
...
Bad UV coordinates for polygons in this thing!
[node: world,meshfact(name=watchtower),params]
...
Bad UV coordinates for polygons in this thing!
[node: world,meshfact(name=watchtower),params]Do the bad uv coordinates just affect the texture lighting or do they have other possible bad effects?
In the previous program run without the --relight I got this as well (still relighting as I post)
crystalspace.collisiondetection.opcode:
OPCODE WARNING: found 2 degenerate faces in model! Collision might report
wrong results!
Could the degenerate faces be the cause of the hole .... oh good to see the old tracker is nearly done, I'm wondering now if the new maps with the fixed ladders are out or if they are still coming, last time I went by the hole .... near the entrance pass (a couple days ago) .... it was still there, so I'm thinking not.
Is any of this useful to the devs, I cannot imagine it is never before seen by them.