Update on Developer Preview 3 Progress - Saturday 29 March 2008 (21:51)
Hello, its been a while since the last update. You may have seen some
of the bug fixes (a big thank you to those who reported them) or some
small tidbits about dp3 by reading the forums. You may have also seen
some of the changes and additions if you have been reading the wiki.
Below, you can see a summary of what has been worked on for Developer
Preview 3:
Most notable new scripting functions:
- Ped support
- Customizable handling for vehicles
- DirectX drawing
- Clientside money handling
- More pickup functions
- shutdown() function to close down the server
- More xml stuff (xmlNodeGetSubNodes and xmlNodeGetParent)
Most notable improvements and/or bug fixes:
- Heavy emphasis on fixing and improving shooting synchronization issues, as they have been revealed as a major issue by user-created resources. This includes a major change in the streamer.
- Carjacking issues leading to desync problems mentioned above.
- Sliding bugs directly linked to shooting sync mentioned above and sliding bugs that only affected animations.
- No shooting with uzis while crouched is fixed
- Scripting improvements on certain functions (most notably rewritten camera functions).
- Fixing issues discovered in MTAs default resources while using them with certain settings or under certain conditions.
- Continued work on the map editor resource is being done by its QA team developers. They hope to have it done for DP3.
Note: A daily changelog of developer work should resurface sometime after the release of DP3. This is a small list of some of the most major bug fixes for DP3. There are many more unmentioned fixes. The changelog is temporarily gone due to equipment upgrades on the machine that was used by developers to log build changes and automatically update the changelog on this site.
In order to ensure that releases are stable with a large amount of players, MTA is considering changing the mass testing policy from semi-public testing to public testing, in order to achieve the largest player counts possible. The QA team would ensure that the build has no major issues and conduct a public test, perhaps weekly. This action would lead to much more mass testing and more confidence in stability. In effect, it would pave the way for quicker releases. Watch for more news on this, coming soon.
Most notable new scripting functions:
- Ped support
- Customizable handling for vehicles
- DirectX drawing
- Clientside money handling
- More pickup functions
- shutdown() function to close down the server
- More xml stuff (xmlNodeGetSubNodes and xmlNodeGetParent)
Most notable improvements and/or bug fixes:
- Heavy emphasis on fixing and improving shooting synchronization issues, as they have been revealed as a major issue by user-created resources. This includes a major change in the streamer.
- Carjacking issues leading to desync problems mentioned above.
- Sliding bugs directly linked to shooting sync mentioned above and sliding bugs that only affected animations.
- No shooting with uzis while crouched is fixed
- Scripting improvements on certain functions (most notably rewritten camera functions).
- Fixing issues discovered in MTAs default resources while using them with certain settings or under certain conditions.
- Continued work on the map editor resource is being done by its QA team developers. They hope to have it done for DP3.
Note: A daily changelog of developer work should resurface sometime after the release of DP3. This is a small list of some of the most major bug fixes for DP3. There are many more unmentioned fixes. The changelog is temporarily gone due to equipment upgrades on the machine that was used by developers to log build changes and automatically update the changelog on this site.
In order to ensure that releases are stable with a large amount of players, MTA is considering changing the mass testing policy from semi-public testing to public testing, in order to achieve the largest player counts possible. The QA team would ensure that the build has no major issues and conduct a public test, perhaps weekly. This action would lead to much more mass testing and more confidence in stability. In effect, it would pave the way for quicker releases. Watch for more news on this, coming soon.
by Ransom, 194 comment(s)
