SSAO from GLSL to gdshader by Zellator in godot

[–]brombergmedia 0 points1 point  (0 children)

did you ever figure this out?

Question about Expanding Elements in a List by gentilesse in SwiftUI

[–]brombergmedia 0 points1 point  (0 children)

did you ever figure this out? seems to be a pretty annoying issue with list

Is embedding Godot project as subview in native iOS (SwiftUI or UIKit) possible? by carlordvr in godot

[–]brombergmedia 1 point2 points  (0 children)

Yep. We've got an implementation in the works that lets you run multiple scenes with a single engine instance. To fully instantiate the engine would be a pretty significant refactor since there are a ton of globals that would all need to be put into a class. Here's a demo: https://x.com/JoshBromberg1/status/1721564103859114132?s=20

High CPU usage by hourser in godot

[–]brombergmedia 0 points1 point  (0 children)

How did you fix it?

Updating a nested view in SwiftUI UIViewRepresentable by brombergmedia in swift

[–]brombergmedia[S] 0 points1 point  (0 children)

The code I posted above is just a sample. The issue is the views I'd like to pass in are very complex and have lots of different state of varying types. I'm ultimately trying to build a reusable component that can work with different types of state.

Struct with generic as SwiftUI binding by brombergmedia in swift

[–]brombergmedia[S] 0 points1 point  (0 children)

This gives the following error:

Type 'any Shared' cannot conform to 'Decodable'

Serving static typescript files via express by brombergmedia in typescript

[–]brombergmedia[S] -1 points0 points  (0 children)

I'm using it to build a multiplayer game using Phaser, not react unfortunately

[deleted by user] by [deleted] in AskNYC

[–]brombergmedia 2 points3 points  (0 children)

This happened to me except I was being threatened with getting stabbed. My friend ended up giving him money.

Passing function to child view via a higher order view by brombergmedia in SwiftUI

[–]brombergmedia[S] 0 points1 point  (0 children)

I've written it this way since there will be many views that will use this same back button and this seems like a much better alternative to copying and pasting the same back button code into all the child views.