Genma Saotome, on 01 June 2011 - 01:45 PM, said:
First, the bounding box is ....
Second, not all objects deserve to be bounced away from ...
Third, assuming a one-bounce-for-all is ....
Fourth, the suggestion was made about object classes ...
Fifth, it seems to me it's better to let the designer ...
Dave, you've done a great job on the "what", but haven't addressed the "why". My view on the "why" is that it's not a important feature to include, in any form, for the following reasons:
First, this issue really applies mainly to the #2 camera, and maybe the #6 camera. Does not having those cameras NOT respect solid object definitions detract from the game experience? My judgement is no. There isn't an issue with seeing into, through solid objects for a train sim, unlike a first person shooter game. There may even be advantages when spotting a cut of cars inside a large building to zoom inside to see the actual position of the cars. Nor do I believe this is a big issue as many users position the #2 camera above likely solid obstructions (bridges, etc) of their view of the train when just running.
Second, by allowing the camera to go wherever the player want it to be, Open Rails is providing a consistent experience and NOT imposing anyone else's idea (devs, route designer or modeller) of what should or should not viewed from the camera. Having the camera respect some kinds of objects and not others will only create questions and confusion as to what, how, the feature works or doesn't work.
Third, the community has not clamored for this feature. I interpret that as being satisfied with the behavior of the the cameras as they presently are and consistent with MSTS #2 camera behavior.
Just my 2 cents.