Large .ANIMATED object disappear on the new Renderer.
2 posters
Page 1 of 1
Large .ANIMATED object disappear on the new Renderer.
Hello, I've used .ANIMATED files to create the basis for stations for a while now. This was an effective method, as long as Objectvisibility was set to 1 in the route. However, now on the new tenderer, these objects disappear depending on the angle that my camera is facing. Is there a reason for this?
Inamak17- Posts : 9
Join date : 2020-04-01
Re: Large .ANIMATED object disappear on the new Renderer.
Have you got an example at all?
I'm not aware of anything that's broken in that regard at the minute.
Please also confirm you're using 1.7.1.3
(This is faster, and fixes some glitches with the new renderer)
It's incredibly difficult to find every edge case though, so if I can reproduce this will get fixed.
I'm not aware of anything that's broken in that regard at the minute.
Please also confirm you're using 1.7.1.3
(This is faster, and fixes some glitches with the new renderer)
It's incredibly difficult to find every edge case though, so if I can reproduce this will get fixed.
Re: Large .ANIMATED object disappear on the new Renderer.
leezer3 wrote:Have you got an example at all?
I'm not aware of anything that's broken in that regard at the minute.
Please also confirm you're using 1.7.1.3
(This is faster, and fixes some glitches with the new renderer)
It's incredibly difficult to find every edge case though, so if I can reproduce this will get fixed.
Sure, here's an object that it does it to.
And I can confirm that i'm using the 1.7.1.3
- Attachments
Inamak17- Posts : 9
Join date : 2020-04-01
Re: Large .ANIMATED object disappear on the new Renderer.
OK, issue found; was accidentally introduced in 1.7.1.3
Marginally unrelated thing also:
If you're only using a single state file and no functions, this is better:
[Include]
object.b3d
Position = 0,0,0
This specifically allows the backend to perform some more optimisations which it won't necessarily do if it thinks you're using a mixed object.
Will be fixed from this build onwards:
https://vps.bvecornwall.co.uk/OpenBVE/Builds/OpenBVE-2020-04-02.zip
Marginally unrelated thing also:
If you're only using a single state file and no functions, this is better:
[Include]
object.b3d
Position = 0,0,0
This specifically allows the backend to perform some more optimisations which it won't necessarily do if it thinks you're using a mixed object.
Will be fixed from this build onwards:
https://vps.bvecornwall.co.uk/OpenBVE/Builds/OpenBVE-2020-04-02.zip
Re: Large .ANIMATED object disappear on the new Renderer.
Thank you! For the fix, and the advice
Inamak17- Posts : 9
Join date : 2020-04-01
Similar topics
» object using new renderer in object viewer not blend texture correctly than using old renderer
» Objects in an animated container disappear in Routeviewer and OpenBVE after the insertion point of the .animated file
» Object Viewer crashes when new variables are used in .animated files
» "Fade in" in animated object
» Unable to load wavefront object in Object Viewer
» Objects in an animated container disappear in Routeviewer and OpenBVE after the insertion point of the .animated file
» Object Viewer crashes when new variables are used in .animated files
» "Fade in" in animated object
» Unable to load wavefront object in Object Viewer
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum