Upper overhead wire: yes or no?
#21
Posted 11 May 2013 - 12:47 AM
Thanks.
#22
Posted 11 May 2013 - 11:43 AM
#23
Posted 16 May 2013 - 10:58 PM
Csantucci, on 11 May 2013 - 11:43 AM, said:
I haven't had time to look at your patch yet and I don't know if anyone else has.
Yes, of course we want Open Rails to support a variety of overhead wires although, speaking just for myself, I would prefer a tidier solution than yet another checkbox in the menu.
All this talk of a project fork to create Open Rails ITA seems very hasty. It's your right under the license, of course, but it would be better for OR and less work for you if we can find a good solution without a fork.
So I'm asking you to give us time to look at the options and perhaps help us to trial a solution before deciding to branch out on your own.
#24
Posted 17 May 2013 - 01:09 AM
Following your post above I will try to propose the last simple idea I have: within the ORTS options there is already a checkbox named "Overhead wire": could maybe this checkbox become a 3-options thing (no overhead wire, 1 overhead wire, 2 overhead wires)? I hope you can agree on this solution. Else I hope that you can provide an idea on how to make this available now to everyone.
#25
Posted 17 May 2013 - 02:12 AM
What I don't like much though, is already creating one ORTS appart from the versions available on the "official site". Because it will get as confusing as lots of versions like on the Open TTD community, and then there's some really cool versions that then aren't able to have some different add-ons because of the different versions and such... a huge confusion in my point of view.
#26
Posted 17 May 2013 - 08:50 AM
My reasoning is that none of these three things cost performance (unlike the other options, especially dynamic shadows), so there isn't much point having them as options, and that - just for the moment - we want to keep non-MSTS behaviour/features as 'experimental'. (Once we sort out of own content system, that will have all the abilities we can give it to specify what overhead wire to use, etc., so no option should ever been needed for typical use.)
#27
Posted 17 May 2013 - 09:24 AM
#28
Posted 17 May 2013 - 09:26 AM
I'd also be curious how many people would be willing to part with requiring 100% compatibility with the MSTS way of doing things.
Has anyone in the OR leadership team considered doing a community survey to help figure out what the priorities should be?...
#29
Posted 17 May 2013 - 10:45 AM
eolesen, on 17 May 2013 - 09:26 AM, said:
I have trouble understanding what you mean here.
OR has achieved a surprising degree of compatibility with MSTS content and MSTS features which work today will continue to work in the future. This backwards-compatibility is part of our mission.
Hope that helps,
#30
Posted 18 May 2013 - 01:05 PM
eolesen, on 17 May 2013 - 09:26 AM, said:
It varies by feature, really; some are enhancements (like 2-wire) and some are actually experimental (like DM, superelevation, max LOD). I'd say it's somewhere between experimental, advanced and miscellaneous.
eolesen, on 17 May 2013 - 09:26 AM, said:
Firstly, we're not requiring 100% compatibility with the MSTS way of doing things. However, when dealing with MSTS content, we are aiming to replicate as much of the functionality and playability as we can. Things will never be exactly the same and some things will forever be different but, when we can match MSTS, we should.