iopzzza,
1) We're still in Alpha state for the Unity version, as the port took longer than expected (plus other issues ; more info in the mini-blog =>
topic11-27585.php?start=45 ).
We might get close of the v1.0 by end of May, if luck is on our side, though...
2) Unity is good, or even indispensable, for :
- Getting modern visuals ; even with the old TE2013 textures, TEM2 looks a bit better with Unity lighting, shaders & shadows
- Porting to Mac & Linux (with finally the online support for Mac)
- Porting TE4 to consoles
- Porting TEM2 to tablets (very unlikely to happen, but still, it's now a possibility )
- Its more modern animation system
- Its editor : it helps to create, prepare, organize, test & tune all the game data
- Getting access to many, many, many assets and things to ease the development (eg: the new rendering for the speed & match time boards ; the new bug reporting system ; etc.)
- Avoiding some of the issues specific to some hardware ; ie: as I couldn't test my own engine on a lot of PCs, it didn't work well on a few PCs (eg: the infamous jerking rendering issue) ; with Unity, this kind of case can still happen, but they should be more rare, as Unity has been tested and used on dozen of millions of PCs
Davide Menez,
1) You were almost right in your guess : the timing wasn't assigned to non-customizable strikes when the selected forehand wasn't the 1st one (because in that case the engine is looking for alternative volleys & smash) ; it's fixed in today's build, thanks to your report !
2) I ported ForceSunInBack to Unity in today's build
3) Did you actively chose a low rendering quality in the game launcher ? Do you have a very old PC ?
EDIT: I checked and Unity reverted the default quality setting to "Fastest" instead of "Fantastic" ; it might be the reason you got such visuals...