What is DSH / PTC?
Deepseek Harness. PTC is one of the 'modes' it has.
I tested 10 model/harness combinations on the same Three.js task
31–40 of 81 posts
Re: I tested 10 model/harness combinations on the same Three.js task
#32The Astra version seems to have used three.js r170, which is from October 2024. Sol used an even earlier version. GLM's code used the latest version, but I think it's just getting three.js@latest from jsdelivr so it's unlikely to be writing code against that version. Qwen on OpenCode also fetches from jsdelivr, but using a pinned version at r160. I don't think any of these examples are using things like tone mapping…
What’s a good way to drive models to use current versions?
Re: I tested 10 model/harness combinations on the same Three.js task
#33I’m always confused, are all these shapes programmatically generated or are they downloaded from some source?
Also I think Astra looks the best and has the best functionality. Also shocked how much better GLM is on the Non Codex harnesses. Didn’t think it would make such a difference.
Would be nice if you could include cost in the table
Re: I tested 10 model/harness combinations on the same Three.js task
#34The Astra version seems to have used three.js r170, which is from October 2024. Sol used an even earlier version. GLM's code used the latest version, but I think it's just getting three.js@latest from jsdelivr so it's unlikely to be writing code against that version. Qwen on OpenCode also fetches from jsdelivr, but using a pinned version at r160. I don't think any of these examples are using things like tone mapping…
Anyone know of pertinent skill files to nudge the agents into these directions?
Re: I tested 10 model/harness combinations on the same Three.js task
#35The Astra version seems to have used three.js r170, which is from October 2024. Sol used an even earlier version. GLM's code used the latest version, but I think it's just getting three.js@latest from jsdelivr so it's unlikely to be writing code against that version. Qwen on OpenCode also fetches from jsdelivr, but using a pinned version at r160. I don't think any of these examples are using things like tone mapping…
Not tone mapping/shader graph is probably the least of the sins, these kinds of one-shots tend to produce hundreds of THREE.Geometry, massive matrix walks, etc. that explode once you move beyond a screen saver.
The models _can_ do it, but you need to ask for the right things. Most people don't, they'll usually blame the browser for being slow or ugly when they can't break through the THREE demo page wall.
Re: I tested 10 model/harness combinations on the same Three.js task
#36I saw examples on X of people building amazing things with Three.js and models, and I figured out how to build them myself. But the results are mostly low-poly materials and crappy animations (pretty sure because I am not the best at these things). I thought it was my prompt (it was detailed), but it seems to be mostly a limitation of the models.
From all the examples I've seen, Astra does it really well, and I suspect it's because they wanted to attract game designers, so they trained the model more on 3D, animation libraries, etc.
Re: I tested 10 model/harness combinations on the same Three.js task
#37The Astra version seems to have used three.js r170, which is from October 2024. Sol used an even earlier version. GLM's code used the latest version, but I think it's just getting three.js@latest from jsdelivr so it's unlikely to be writing code against that version. Qwen on OpenCode also fetches from jsdelivr, but using a pinned version at r160. I don't think any of these examples are using things like tone mapping…
Anyone know of pertinent skill files to nudge the agents into these directions?
Don't use skills. Point it to a game engine or better yet full game repo or whatever and ask for what you want.
Re: I tested 10 model/harness combinations on the same Three.js task
#38Btw in my quest for a good desktop codex/claude like app - https://github.com/openchamber/openchamber - this seems to be front-runner. I pair it with OMP via https://github.com/alvins82/omp-openchamber-server/ . I wanted a powerful GUI+harness setup for open models so I could use/test as they came out.
I like Paseo https://github.com/getpaseo/paseo But I am annoyed at these GUIs implementing features I don’t care about. I want them to just wrap my harness and forward it to my iPhone, but they can’t help themselves from feature creep.
I've been impressed with orca
https://github.com/stablyai/orca
I did have some issues getting it installed on a headless server. I sort of gave up and installed the instance that I use as the remote server on a Debian + xfce machine I had laying around.
Re: I tested 10 model/harness combinations on the same Three.js task
#39The Astra version seems to have used three.js r170, which is from October 2024. Sol used an even earlier version. GLM's code used the latest version, but I think it's just getting three.js@latest from jsdelivr so it's unlikely to be writing code against that version. Qwen on OpenCode also fetches from jsdelivr, but using a pinned version at r160. I don't think any of these examples are using things like tone mapping…
Not tone mapping/shader graph is probably the least of the sins, these kinds of one-shots tend to produce hundreds of THREE.Geometry, massive matrix walks, etc. that explode once you move beyond a screen saver. The models _can_ do it, but you need to ask for the right things. Most people don't, they'll usually blame the browser for being slow or ugly when they can't break through the THREE demo page wall.
Can you elaborate on this? how would you work on a larger THREE project? would you create models independently?
Re: I tested 10 model/harness combinations on the same Three.js task
#40Qwen with open code seemed like the best to me. It seemed like the best balance between performance and visuals
Astra has so much more detail. It did take 5x more time, but that's usually negligible when it replaces x hours of human output.