1. Sample renderer to check conformance
2. PBR Next
1. absorption / attenuation, clear coat, subsurface scattering, anisotropy
2. Consistency and fallbacks for performance
3. Compressed textures: KTX2 & CTTF (draft): involved both format and web transmission
4. Check out gltf assets viewer cross engine
5. Google model viewer based on gltf (for e commerce)
6. Automate test between different renderers (internal work)
1. https://github.com/GoogleWebComponents/model-viewer/tree/master/test
2. https://googlewebcomponents.github.io/model-viewer/
7. Mozilla hubs: a interactive and collaborative gltf model viewer, integrate models into collaborative environment (avatar, dynamic model loading)
8. Mozilla editor: spoke

WebGL 2.0 is the baseline for Web graphics, WebGPU targets low-end and high performance standard.

Tools for Marvel』s Spiderman: Editing with immutable data

(IMPORTANT, FOR ALL TOOL DEVELOPERS)

Background

• Transition from previous web toolchains
• Transition during project development
• Targeting pure native toolchains
• The game scale extended dramatically

Changes

• QT framework
• 12 editor to port

• Target
• Performance
• multi thread
• maintainable
• Type safe
• Enforce correct use of edit loop
• Reuse maximum work that have been done in game (assets)
• Identical features between C++ and JS version: Avoid needs expand and lost control
• Guarantee 100% data compatible
• Two version coexist at the same time in Transition
• Already have many features runs on LunarServer which manages
• Asset data
• MongoDB
• perform operation
• Already using a Date Description Language
• Continue to use JSON
• Type safe JSON would be better (non type safe is a draw back in new tool)
• DDL format is saving in JSON data

Type safe, C++ friendly JSON

• ToolsDDL

• Compiles C++ source code for DDL declaration

• ToolsDDL transpiles the DDL to a C++ data type with its JSON data parsers

1 : getter

2 : read value from payload or default values

3 : DDL

• Why JSON

1. Already using JSON in all existing editor, can』t break data compatibility

2. JSON is needed for data representation in undo redo system

3. Conversion for a intermediate format from and to JSON is waste (JSON will be used anyway for the editor』s source asset)

Implicitly shared data with copy on write (for JSON data access)

• 1. Only one data reference, the inner data is atomic
• 2. Setter will detach the data reference

• 3. Detach will copy a new object copy for the modification

• 4. In synchronization process, old version data will be deleted, all shared data owner will point to the new object reference

• 5. Ref count is used to identify whether a data reference is shared by other owner, also for deallocation
• 6. JSON data is using implicitly shared data with copy on write (recursively, reference count mechanism, no mutex needed)
• 7. No cost copy operation(compare to mutex)
• 8. In large tree

Immutable data

• 1. Target: Remove the setters, encourage functional style programming, readable and testable code, easy to reason about
• The object is a value rather than has a value
• 2. Treating object as primitive data

Edit loop

Type safe C++ friendly JSON

• IqJsonObject comming to open source soon

• Accessing data is half rewritten solved
• Multiple version of data flying
• not a problem because Spiderman only request data in main thread
• all clients sharing the same LunarServer, only one client can make modification at a time

Conclusion

另外兩個部分的內容請點擊以下鏈接查看：

Cocos：Cocos @ GDC 2019 - Vulkan 最新進展及 Google Stadia 展台見聞?

zhuanlan.zhihu.com
推薦閱讀：