Engine Testing - 94.1.1-693-g5717870 (13. Jul 2013)

[abma]

New testing release for preparing 95.0!

Most changes are bugfixes, only some few new features were introduced:
- add LuaIntro (allows custom loadscreens!)
- fix crash in KAIK
- improved performance
- ...

For details of changes since 94.1 look at the "95.0" section in changelog.txt.

See the Testing Release Wiki page for general info about how to obtain the release, and an archive of all testing releases since the last stable one.

If you find a bugs, please report to Mantis.

Remember to attach infolog.txt as file, if you crash!

sadly the macosx build still fails, still help needed! http://springrts.com/mantis/view.php?id=3816

Is 94.1.1-693-g5717870 better than 94.1? if so, i guess we can make a release.

[Silentwings]

Cool, testing :) Is Spring.Restart working yet? I didn't see it on changelog.

[abma]

Is Spring.Restart working yet?

no related change, sorry

[Forboding Angel]

Zoom and scrolling are still super jerky on all cameras with 250 fps which gives the illusion of lag. Rotating camera is butter smooth.

[varikonniemi]

The requested URL /dl/buildbot/default/develop/94.1.1-693-g5717870/linux64/spring_{develop}94.1.1-693-g5717870_minimal-portable-linux-static.7z was not found on this server.

PLEASE take the time to test this carefully before release. I don't think the community can take another botched release. Don't release with outstanding bugs, like Forb's jerky camera.

[abma]

oops,thanks, fixed the link.

http://springrts.com/dl/buildbot/defaul ... -static.7z

[jK]

fixed dl links

[abma]

aww, oops, thx

i'm fighting to much battles at once it seems...

[raaar]

For now it seems to be working nicely.

sadly, can't play on the official server.

The water texture seems to have changed.

EDIT: nvm, just had to change "DisableVersionCheck=0 --> 1" in springlobby.conf. Played an 1v1 and it worked fine.

[varikonniemi]

Only one problem during limited testing: the smooth scroll widget in zk svn often starts to go with full speed to bottom right when pressing mouse3. It is very annoying and makes smooth scroll impossible to use.

But it might very well be zk widget problem not engine one.

Hope the nice performance in small games translates over to big games also.

[Forboding Angel]

94.1.1-693-g5717870 Is definitely better, but the zoom/scroll jerkyness is definitely a release blocker.

I get about 250 fps in 94.1.1-693-g5717870 as opposed to the 50 I'm lucky to get in 94.1.

[Deadnight Warrior]

• {Laser, Emg}Projectile: disable all collision-testing when ttl <= 0 these projectile types could exceed their range due to fadeout and only removed themselves (deleteMe=true) when intensity or length reached 0, so without disabling coldet (checkCol=false) range-exploits were possible

This makes it impossible to increase LaserCannon/EMG weapon range in-game with LUA Spring.SetUnitWeaponState(unitID, weapNo, "range", newRange) over the weaponDef specified maximum. It also causes units to aquire their target and start shooting lasers, but projectiles can't reach them. Seems as if the TTL is calculated from weaponDef and not unit's local weaponState. The workaround would be to increase the weapon range in weaponDef_post and set it to shorter range upon unit creation, but that will have unit's tooltip show longer range than it really is.

Also range circles rendered by engine when you point an unit and hold shift over it are incorrect on the main map, but are correct on minimap, if they where changed via LUA in-game. Affects all range circles, weapon, radar, sonar, etc. This bug is present for a long time.

If you need something to test it with, try YAAG.

[azaremoth]

This makes it impossible to increase LaserCannon/EMG weapon range in-game with LUA Spring.SetUnitWeaponState(unitID, weapNo, "range", newRange) over the weaponDef specified maximum.

Yes - that causes an issue for several units in "hero auras" in the cursed. I can work around that by replacing laser cannons with different weapon types if needed.

Zoom and scrolling are still super jerky on all cameras with 250 fps which gives the illusion of lag. Rotating camera is butter smooth.

I can not reproduce this - no matter what framerate I have and what camera is used - everything was running smoothly.

[raaar]

• {Laser, Emg}Projectile: disable all collision-testing when ttl <= 0 these projectile types could exceed their range due to fadeout and only removed themselves (deleteMe=true) when intensity or length reached 0, so without disabling coldet (checkCol=false) range-exploits were possible

This makes it impossible to increase LaserCannon/EMG weapon range in-game with LUA Spring.SetUnitWeaponState(unitID, weapNo, "range", newRange) over the weaponDef specified maximum. It also causes units to aquire their target and start shooting lasers, but projectiles can't reach them. Seems as if the TTL is calculated from weaponDef and not unit's local weaponState. The workaround would be to increase the weapon range in weaponDef_post and set it to shorter range upon unit creation, but that will have unit's tooltip show longer range than it really is.

Also range circles rendered by engine when you point an unit and hold shift over it are incorrect on the main map, but are correct on minimap, if they where changed via LUA in-game. Affects all range circles, weapon, radar, sonar, etc. This bug is present for a long time.

If you need something to test it with, try YAAG.

shots fired from units without any sort of lua tweak should collide with the target. If i understood correctly this seems like a serious bug, better revert and let them collide, even if just for a bit longer.

[Deadnight Warrior]

shots fired from units without any sort of lua tweak should collide with the target. If i understood correctly this seems like a serious bug, better revert and let them collide, even if just for a bit longer.

I was refering to LaserCannon weapons who had their range increased beyond maxRange specified in weaponDefs.

[Forboding Angel]

Zoom and scrolling are still super jerky on all cameras with 250 fps which gives the illusion of lag. Rotating camera is butter smooth.

I can not reproduce this - no matter what framerate I have and what camera is used - everything was running smoothly.

http://springrts.com/mantis/view.php?id=3845

[Silentwings]

I can't reproduce it either - BA has some lua in it to help smoothness of scrolling, but with BA 7.78 + 94.1.1-693 the scrolling/zooming is smooth.

[raaar]

shots fired from units without any sort of lua tweak should collide with the target. If i understood correctly this seems like a serious bug, better revert and let them collide, even if just for a bit longer.

I was refering to LaserCannon weapons who had their range increased beyond maxRange specified in weaponDefs.

Yes, but it smelled like something that could still cause problems when firing near max range even without lua modifications. Apparently it does! (check attachment)

This should be fixed/reverted.

EDIT: the problem happens on units with lasers trying to fire at targets near max range on hills.

added another screenshot of a can, this time in xta 9.8 firing at a pulverizer on a hill, and shot going through collision box when it should be colliding.

[raaar]

There's something else.

It seems units with very low acceleration aren't being able to reach their top speed.

ex: try to get a boat with 0.01 acceleration to reach a top speed of 2.0. It won't reach that speed, maybe half.

Happens for land units too.

It's like there's some sort of drag in effect.

I don't remember having this issue before changing to the test build, but i may be wrong.

EDIT: I got around it by overriding unit acceleration in unitdefs_post.lua ( the threshold was "acceleration < maxVelocity/80" )

[abma]

new testing release:

http://springrts.com/phpbb/viewtopic.php?f=12&t=30793

sorry, when we didn't fix "minor" bugs: because of the lack of man power and time we focus on the big bugs and try to make a release with the goal, that it is better than the last one.

please mantis them if you think they are important, so they don't get lost.