Strange warning message: the object with an index of 0 has been declared twice
2 posters
Page 1 of 1
Strange warning message: the object with an index of 0 has been declared twice
In recent OpenBVE builds (1.7 and up) RouteViewer gives me an error message that I don't really understand:
The object with an index of 0 has been declared twice. The most recent declaration will be used.
It doesn't refer to a specific object. I checked everything to see if I mistakenly declared an index twice but couldn't find any errors. The route where I have this problem is here (I quickly put it inside a .7z archive):
https://drive.google.com/open?id=1EBVLGVxlTqq2WcpvRDJG9msmfRLKg1Mr
OpenBVE 1.6 and before doesn't produce this error message.
Can anyone help me figure this out?
The object with an index of 0 has been declared twice. The most recent declaration will be used.
It doesn't refer to a specific object. I checked everything to see if I mistakenly declared an index twice but couldn't find any errors. The route where I have this problem is here (I quickly put it inside a .7z archive):
https://drive.google.com/open?id=1EBVLGVxlTqq2WcpvRDJG9msmfRLKg1Mr
OpenBVE 1.6 and before doesn't produce this error message.
Can anyone help me figure this out?
Re: Strange warning message: the object with an index of 0 has been declared twice
Interesting (and harmless....)
This is being caused by the Structure.Pole declaration.
The trouble here is that openBVE has internal 'compatability' poles, which occupy indices 0 through 3.
By declaring a new pole using index 0, you're overwriting this inbuilt one and triggering the warning.
The error message needs to be made a little more specific (which specific object type for starters), and probably fine-tuned to exclude the default poles somehow, but it's valid.
This is being caused by the Structure.Pole declaration.
The trouble here is that openBVE has internal 'compatability' poles, which occupy indices 0 through 3.
By declaring a new pole using index 0, you're overwriting this inbuilt one and triggering the warning.
The error message needs to be made a little more specific (which specific object type for starters), and probably fine-tuned to exclude the default poles somehow, but it's valid.
Re: Strange warning message: the object with an index of 0 has been declared twice
Thanks. I'll just use a diferent index number then.
Similar topics
» Strange warning: The command Route.TFOXML is not supported
» error shown, object declared twice??
» should default option for object optimization mode in object viewer is low or high instead none ?
» Unable to load wavefront object in Object Viewer
» Massive *.csv object vs. composite *.animated object
» error shown, object declared twice??
» should default option for object optimization mode in object viewer is low or high instead none ?
» Unable to load wavefront object in Object Viewer
» Massive *.csv object vs. composite *.animated object
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum