Christopher Lees

I think the build from today will fix this, issue with the original wavefront parser only. Assimp works OK with your test object. Note that the scale is completely out...

Scale handling added too. https://vps.bvecornwall.co.uk/OpenBVE/Builds/OpenBVE-2020-11-28.zip From the looks of things, there are some other funky scaled files, but I need actual examples of these to play with if they come...

 Definitely works here, just tried it with a freshly downloaded copy of the build from today. (Note that your object at correct scale is now too small to see...

Interesting. I think assimp must be applying unwanted alpha from that pic.

https://stackoverflow.com/questions/5585368/problems-using-wavefront-objs-texture-coordinates-in-android-opengl-es/5605027#5605027 Inverting the texture co-ordinates may well be right for all files, but I need to try a few more samples. (I'm sure I tested it as OK when I...

Fixed the transparency issue, and added a Sketchup specific hack for the minute. If using *anything* exported from Sketchup, I'd suggest the new renderer. Those files are a mess internally.

I get the horrible suspicion that we're heading into implementation specific territory again with the d value. Will add tr, and see what I can do with assimp. Reversing the...

Some progress on curves:  This now generates curved objects for the repeaters and adds them to the route. Can definitely be optimised (this now just creates a cloned /...

 That's better. For the moment, this has just performed a standard railtype transform on the newly generated curved object. No correction for the secondary track radii at the minute,...

Misplaced objects aren't present in the old branch https://github.com/leezer3/OpenBVE/pull/154 Must have made a typo somewhere.....