Inconsistency regarding -projectpath / -projectPath argument

[burnedikt]

Issue Checklist

• I'm using the latest u3d version
• I ran u3d --help
• I read the README
• I made sure that a similar issue doesn't exit

Issue Description

When using u3d run in conjunction with the -projectPath parameter, I've noticed that u3d's implementation of the parameter differs from Unity's implementation.

More specifically, the Unity docs explicitly state that the path to the Unity project to be loaded is to be passed via the argument -projectPath (camelCase). However, u3d's implementation of find_projectpath_in_args only looks for -projectpath (all lowercase) to identify the given project's path. As an effect, Unity is being launched with two arguments (once -projectpath which points to the current working directory and -projectPath which points to the actually provided directory in accordance with Unity's docs).

I am unsure as to why the feature has been implemented this way, but maybe an older version required the lowercased variant? In either case, find_projectpath_in_args could simply be adjusted to check for both the lowercased and camelcased variants of the parameter which would make it more failsafe.

[niezbop]

Hi and thanks for rising this. I believe that this is an issue on our side and not some kind of backwards compatibility. I'll fix this up asap.