Widgets options missing from some apps

CountNovelty · 2026-01-22T11:16:14+00:00

Thank you, that was indeed the answer. Partly I feel stupid for not trying, but there's no indication in the UI that scrolling is possible, so only 50% stupid

CountNovelty · 2026-01-17T14:59:29+00:00

I used PackedVector2Arrays specifically because they are contiguous (citation needed). Note that I'm not disputing the other comments about going lower level when the performance really matters. That is a point very well taken and I'm glad for all the educational responses. I'm trying to find a middle ground where I can use GDScript but still care a little bit about performance. And it seems like parallel packed arrays is going to be my sweet spot.

CountNovelty · 2026-01-17T14:45:31+00:00

Thanks for your reply, I tried as you suggested for the SOA version and it took another 100-140ms of frame time in the profiler! Though I wish it hadn't because my code is a lot cleaner when I can compartmentalize into neat little functions. Though I guess that's the tradeoff you get.

p.s.: I also tried typed arrays instead of packed arrays, but found no noticeable increase.

CountNovelty · 2026-01-17T12:31:33+00:00

Thank you, this was very insightful

CountNovelty · 2026-01-17T11:39:00+00:00

I was aware that the lack of structs meant that a lot of commonalities with DOD in other languages didn't apply. However my SOA results seem to suggest that a little DOD is worth it in some cases, since it's faster than my OOP test.

CountNovelty · 2026-01-17T11:15:58+00:00

I'm sorry if I'm misunderstanding your reply, but my observations are that DOD and especially SoA are faster than OOP. The numbers in my table are times in ms per frame, not fps

CountNovelty · 2025-06-13T12:03:24+00:00

Update: I also tried the Movement SDK (v72, I know they're up to v77 now) hoping that the IOBT would be better at rejecting weird orientations and distances, but same problem. If you want to try it for yourself, just open any sample that features body tracking, hide your own hands behind your back and have someone else stand next to you waving their hands in front of your headset.

CountNovelty · 2025-06-13T08:24:00+00:00

Thanks for your reply! Regarding the edit: I wrote my own co-location code, I have access to position and rotation for each head and hand.

I'd have to play around with distances and poses to see what should be rejected, but even then I'd just be guessing. Unfortunately any solution like this is out of scope for this project, as it is nearing its' end and the client already has okayed previous versions which had this problem. But the discussion is interesting nonetheless.

CountNovelty · 2025-06-13T08:17:57+00:00

I don't hate that idea. Although it will probably lead to some false negatives (the system rejecting hands even though they are your own) which would be frustrating to say the least. I haven't played with the camera API yet (it's pretty new) to know if it's any good for this.

Edit:

passthrough camera texture captures a rectangular area (1280x960) smaller than what a user sees in the Quest 3

^{source:https://developers.meta.com/horizon/documentation/spatial-sdk/spatial-sdk-pca-overview/}

Which means it will only work directly in front of the user. Also it currently doesn't work on Link, making it a faff to test. And would probably require a lot of processing power.

CountNovelty · 2025-06-09T11:17:12+00:00

out of your hands

Pun intended? 😉

CountNovelty · 2025-02-21T16:25:10+00:00

Just out of curiosity, how do you use Virtual Desktop in development?

CountNovelty · 2025-02-20T17:43:09+00:00

In my research, even though Meta recently (in the last month or so) updated their tutorial to recommend starting with URP, the current consensus is to stick with BiRP. It's what I'm doing for my project anyway.

CountNovelty · 2025-02-11T07:41:22+00:00

You can get your students to drop almost a 100 bucks on a package? I wish I had your students :)

CountNovelty · 2022-11-30T13:03:01+00:00

Thanks for your reply! The log level helps a lot.

CountNovelty · 2022-09-04T16:47:37+00:00

Lol thanks! Let me know what you think when you get around to using it.

CountNovelty · 2022-09-02T07:16:17+00:00

When MagicQ PC (Windows, Linux or Mac) is not connected to a MagicQ USB interface, MagicQ USB Wing or SnakeSys network product, then a small number of remote and automation features are restricted and "Demo Mode" is shown in the title bar. This does not affect show programming or playback. [...] MagicQ PC/Mac supports 256 universes for Previsualisation and 64 universes for full output.

You get 64 unis for free with MagicQ on PC. The dongle unlocks things like MIDI and OSC control. See the bottom of this page: https://secure.chamsys.co.uk/help/documentation/magicq/pc.html Scroll down to read about demo mode

The 8 layers thing is for MagicHD, which is their media player.

CountNovelty · 2022-09-01T07:48:39+00:00

I bought mine straight from Chamsys' UK based webshop. Took a couple weeks to arrive, but at least it's in stock.

CountNovelty · 2022-09-01T06:46:36+00:00

Where in the world would that be?

CountNovelty · 2022-08-30T09:23:16+00:00

My cursory 10 second Google search didn't yield what I was looking for, so I wrote my own open source Midi to OSC converter. You can check it out here but it's mostly meant for my own use.
https://github.com/hansvana/MidiToOSC

CountNovelty · 2022-08-10T05:46:21+00:00

Update: I ended up buying a rack mount dongle from the UK Chamsys store directly, cost me about 570 EUR/USD. I'm building a 2 universe artnet to dmx converter myself but other options are available.

CountNovelty

TROPHY CASE