I am wondering if the MoltenVK render and the future new editor extensions will also bring to the table node based shader creation? Just wonderingā¦ 
3 Likes
Vulkan/MoltenVK wont really do much for such a feature Iām afraid, Iām building it on top of the same render API so it Will have the same capabilities as the current renderer. But it does opens up a bunch of other potentielly cool features down the line that Iām excited about 
7 Likes
One (boring) thing Iām particularily excited about is that we get more than 4k textures on iOS. On iOS, OpenGL is restricted to 4k textures, even if the hardware supports more. Yay! More space for huge keyframe animations!
6 Likes
Before you release the new raycast API I would suggest making rays hit ātriggerā collision objects too. This will not hurt anything, but make the new ray casts more flexible.
3 Likes
I havenāt tried it specifically, but I just assume it works since itās the same raycast code being invoked.
1 Like
This flew a bit under the radar but actually shipped in 1.2.149 under the issue DEF-3618 - Preloader path cache.
In case anyone was waiting for this.
11 Likes
This Friday was an Exploration day and I decided to implement gamepads for html5.
Itās not done yet, but I have the first results:
23 Likes
wooooow 
glad to hear!
1 Like
Got back to doing a bit of vulkan work this sprint, so thought I should share the progress so far. Iām currently looking into dealing with the render pipeline state management for things like culling and depth testing.
21 Likes
Are multiple material IDs per model on any roadmap for 3D?
1 Like
No, itās not on the roadmap. How would it be used?
In the model you can select a material ID # for certain faces. Then in the model you would be able to assign a material per material ID. So you can have a model with completely different material logic for different areas.
Itās one way to get separation of rendering in models. Another way is to map different shader logic based on color coded texture regions for material IDs that way, or to use a PBR approach.
3 Likes
Hey all,
hereās a little teaser Tuesday sneak peak of joints support:
Here you see some classic spring joints, but also hinge joints with motors enabled on the ācarā. 
We recently took a new stab at the design for joints/constraints, based on input from @Mathias_Westerdahl previous exploration, and are now in implementation mode. We want to keep the scope down so we can deliver it as soon as possible. The current plan is;
- Supply a runtime API in the initial release, and having the editor/build-time joint creation as a separate task.
- Initial release will only support joints in 2D physics.
Canāt promise a definite release date, but it is being actively worked on so expect āsoonā. 
26 Likes
whoa! awesome!!
5 Likes
Wow! Something really great! 
opening new possibilities!
5 Likes
Finally
1 Like
One more teaser from @sven , but I donāt know why he doesnāt want to share it himself (I decided to steal his likes =)) )
New API for changing the vector of gravity in runtime:
22 Likes
Hereās another Vulkan teaser Updated to Mojave yesterday which unlocked more debugging tools for Metal / MoltvenVK shaders. I can now step through a piece of shader code for a specific pixel to actually see what goes on with the values, itās pretty wild!
16 Likes
Thatās rad! Will it be possible to debug shaders like this with Defold in the future?
3 Likes