PTE build 85104-pte is now live!

Are you able to get same crash in stable, or just PTE?

Then play more ranked games!

Seriously though, I get what you are saying, and I don't mean to imply harshly punishing people for inactivity. However, an inactive players' rank can't be accurately assessed over time, so a penalty makes sense for that reason. Your skills do erode if you don't play. I was thinking serious inactivity here as well, something like a month, not just one week.

Well, It has been some days I'm trying to get crashes under Linux using stable (wich I report in the support/Linux section of the forum now). So far I've only see this one in PTE. My bet is it is specific to PTE. But I'm not 100% sure.

Nope, but I'm going to make use of that now, thanks!

Well, maybe just lower place in CURRENT rank overall. But still better (inactive) players will be higher than those weaker.

But does it even matter? Inactive players are not shown on ladder, and by forcing people to play just to not fall to the hell, you are not encouraging people. IF you lost skill, and go back play some ranked, you will lose to better players anyway, and go out of your rank. It sorts itself, you dont need punishment for that.

You rather need reward for playing all the time, not punishment for not playing.

I guess I could agree with you, but how could you reward players to provide enough incentive for them to play ranked games? Maybe their level of activity could qualify them for some tournament where a prize was awarded randomly for participating (that way not just the best players would win something all the time)? That could work.

Anyway, one of the main points that I was trying to make there was that I don't like the fact that my rank improves just because other players are inactive. That just seems like a weak way to increase my standing. As I understand it, the ranking system is based on a formula (Glicko?) that is relative and independent of activity. If that is true, then activity should not be a factor, and a deadbeat player would not hinder your advancement. I could be wrong about that part though. However, removing inactive players doesn't seem to be a good mechanic. I guess Blizzard addressed this with the introduction of ranking "Seasons" (where ranks get reset from time to time)? I guess that could work too?

Points. Everyone plays for points. Make it so that when you play a lot you get a lot of points.
Pointless points. Everyone loves them.

FRP = "Frequent Ranked Play" points? Maybe you could redeem FRP points for tournament entries or put them toward the purchase of a Commander in the Armory?

No mods, up to date everything.

Arrow keys kept disabling mid game.

When a group of fabricators are selected to build something and shift keyed to build something else they leave current building in progress to start next quid building. All types and combinations of fabricators had this issue.

will keep testing.

If you even can get more than "nothing" for them that would be even better ofc.

Or "monthly commander reward", custom commander for being the best the longest.

I wonder if @godde would notice if his beast commander is repurposed

Shameless self-promotion.

Build 85104-pte - 7/31/15

This is a release candidate. Please test as much as possible and let us know if you see any issues.

Bugfix/polish:
Fix for client crash when hovering over a celestial unit while another unit is selected
Fix for missing csg biomes
Fix to allow selection of commander in GW

Been running the PTE on Windows 10 Pro 64 bit for 6 months. No issues.

>

Could the avatar factory be fixed soon? Orbital units coming out of it don't rise to the orbital layer.

I scanned through this thread for bits of knowledge about the new apis, and mades some new wiki pages. Please feel free to add anything I missed.

http://pawiki.net/wiki/WorldView_API
http://pawiki.net/wiki/Puppet_API

@pinbender
okay it does snap when I test a position close to the planet surface. However there is a second bug that prevents the snapped location from being returned, I always get the position back I put in. So I can see the result of the test changes, but the returned position is always just the position I put in.

Is there any chance the calls will be fixed within a week or two?
The snapping issue results in wrong results even when I use the planet radius for planets that have a heightmap that isn't pretty flat. For example on amplus I can't correctly find water because the water has a height of ~680 there. Trying to place a land-only thing on a height 700, so 20 above water surface, already yields an "okay".

If it can be fixed short term I'll wait. If it cant I'll probably go the slow way of using puppets first to query the terrain height, I had the hope that I can circumvent that for water, as water is pretty flat.
It would be really cool if the buildplacement test API could always return the snapped position it used for the test, even in case the test said "cant place".
That would cut down the time I need to gather data for a map by a factor of 3 to 5.

I found a bug that would cause this. It should be fixed in an upcoming update.