[Aleks]

NightFright, on 21 October 2021 - 06:42 AM, said:

Added on Github.

(Note: These camera/movie rolls are often used in different ways in user maps, e.g. for stoves, so they won't look right there and would need maphacks to deactivate them.)

I think it's mostly the 2nd frame of the animation (static one) that's used in user maps for other purposes, which I assume doesn't get voxelized - so shouldn't be much of a problem (Also using it as e.g. stoves would probably require applying the sprite floor aligned, which doesn't voxelize by definition).

[Phredreeke]

Isn't the animation using both frames? It would look weird if it alternated between voxel and sprite I'd think

[Dzierzan]

Quote

I think it's mostly the 2nd frame of the animation (static one) that's used in user maps for other purposes, which I assume doesn't get voxelized - so shouldn't be much of a problem (Also using it as e.g. stoves would probably require applying the sprite floor aligned, which doesn't voxelize by definition).

Both are voxelized

Quote

(Note: These camera/movie rolls are often used in different ways in user maps, e.g. for stoves, so they won't look right there and would need maphacks to deactivate them.)

Stoves? Oven stoves? If it's a flat surface on the "floor" then those are not voxelized in Build Engine. I've seen that mxrtxn managed to have floor oriented sprites being rendered as voxels but I never understood how he did that.

[LeoD]

Dzierzan, on 21 October 2021 - 08:19 AM, said:

Stoves? Oven stoves? If it's a flat surface on the "floor" then those are not voxelized in Build Engine.

I'd really like to have an 'unflatten' feature for floor-aligned voxels. That would include a 90° backward tilt, which may or may not be difficult to implement.

Dzierzan, on 21 October 2021 - 08:19 AM, said:

I've seen that mxrtxn managed to have floor oriented sprites being rendered as voxels but I never understood how he did that.

mxrtxn, how did you do that?

[Dzierzan]

[Dzierzan]

No idea what the hell is that... But I voxelized it anyway:

[NightFright]

Live on Github.

One of these days I gotta check which sprites are still left. It can't be that many any more. Considering the original goal was just to get the pickups done, lol...

[Dzierzan]

It strongly depends on where you want to finish that. All bodies? All gibs? All enemies? All props? DC sprites? Vaca Sprites? Xmas sprites?

EDIT: I am the only guy who makes voxels for all voxel projects. Which isn't an easy task.

[jkas789]

I would think all props should be the goal. Maybe add gibs and dead bodies if y'all feeling the mood.

But props IMO should be the goal. It would be nice if DC, Caribbean and Xmas got voxels as well but it's not a obligation. This is in theory something that is being made for fun/love/whatever. Not a effing job.

Quote

mxrtxn, how did you do that?

@LeoD

You are gonna have to message mxrtxn directly Leo. AFAIK mxrtxn has been pretty busy with irl to chack the forums for a while.

[Phredreeke]

It would be nice if every voxel with a Vaca counterpart also had that voxelized. (the one missing that comes to mind is the pearl health)

Right now you can't undefine voxels in DukeGDX, only override them with new ones.

[Dzierzan]

It's fine, I am doing it for fun. Anyway, here's the claw crane.

[NightFright]

Phredreeke, on 21 October 2021 - 02:02 PM, said:

It would be nice if every voxel with a Vaca counterpart also had that voxelized. (the one missing that comes to mind is the pearl health)

Right now you can't undefine voxels in DukeGDX, only override them with new ones.

We would need on-the-fly loading of addon-related content first, like the filters they are using in Raze. Can't expect users to change def files on their own on demand.

Crane added on Github, btw.

[Striker]

Dzierzan, on 21 October 2021 - 12:18 PM, said:

No idea what the hell is that... But I voxelized it anyway:

I do believe this is meant to be an arcade joystick.

[NightFright]

Makes sense. I will rename the voxel accordingly, then.

[Dzierzan]

Is it fine? Maybe should be double sided? There seem to be visual glitches, might be due to being too thin.

[NightFright]

There isn't such a big visual gain here, I gotta admit. Especially once the bills are on the floor.

[Dzierzan]

Well, they no longer "follow" you, so that's a benefit for me. I think I'll paint the other side as well. A voxel is a voxel .

[Skull-Haver]

They look cool, I imagine you could use that DN money cheat to make potato PC's explode with that many voxels haha

[Dzierzan]

Updated model:

[Skull-Haver]

Nice job! Make it RAIN baby

[NightFright]

Added to Github.

[Dzierzan]

Letters are ready as well, but there's a small issue I cannot figure out. And it seems the same issue money has as well, but it's less visable. I understand that the sprite is being flipped, but that I cannot understand. Is something happening code wise?





EDIT: Update, when I made "idle" sprite totally flat, the issue is gone:



So... make it flat?

[Striker]

Dzierzan, on 22 October 2021 - 09:18 AM, said:

Letters are ready as well, but there's a small issue I cannot figure out. And it seems the same issue money has as well, but it's less visable. I understand that the sprite is being flipped, but that I cannot understand. Is something happening code wise?





EDIT: Update, when I made "idle" sprite totally flat, the issue is gone:



So... make it flat?

Jesus, looks like it's being turned inside-out. What happens in software?

[Dzierzan]

I decided to pull request flat letters and I updated 1234 money to be flat as well. As I strongly doubt there will be any fix for that.

[Dzierzan]

[Dzierzan]

[NightFright]

Github updated.

[Dzierzan]

Are you keeping it up @NightFright?

[NightFright]

I think I am done till Monday. Just keep doing your thing.

[Striker]

Dzierzan, on 23 October 2021 - 12:01 AM, said:

I decided to pull request flat letters and I updated 1234 money to be flat as well. As I strongly doubt there will be any fix for that.

You didn't answer my question, though. What happens in software? If it's an issue that happens in one renderer, and not the other, there's a better chance of it being fixed.