ZOMBO: ještě žhavý z rendereru..
koukám že ten ddos furt trvá..
a evženovo info k posunutí exp releasu, vlastně dobrý info - když něco shazuje klienta, tak to bude nějaká core věc v engine - me gusta:-)
Current blockers for internal build include :
Memory crash (client crashes about hour of running)
Couple client crashes with no solid repro
Invisible crew for cars (due to refactor of certain optimizations)
Swap item duplication (due to same reasons)
Issues with binarization of data for map because of changes made to support increase number of objects on the map 2million - 8million.
And more of course.
However its development so we are working on it.
EDIT : The thing about sharing everyday progress is, that some things might not be true in few hours, while others persist. You want to try different approaches to find the best possible. Now were aiming for a more stable experimental releases and much more polish done on them.
a jak mergovali kód, který nemohli hned otestovat v QA:-)
The build didn't get pushed solely for the HDD PSU failure of the core Jenkins server. It was cascade of events that happened over couple days. We lost time because we couldn't test stuff properly. And before all the things got in place (binarization issues, svn issues, hardware issues, data structure). We lost 5 days fixing all of it. Even though devs haven't stopped. The fixes could not get tested accordingly so the bugs that appeared after we got the build for the QA engineers they were behind on schedule.