[Fox]

They converted most textures to 16 colors.

[Phredreeke]

I should clarify, by DN64 I don't mean any converted tiles, only the new weapon/ammo pickups such as the dual SMGs and plasma cannon

[NightFright]

It would be great if voxel defs supported ifcrc like tilefromtexture since then we could just add Carribbean content to the existing voxel pack without having to mess with override packs or something like that.

[DJP]

Number 691 cleaver and 692 knife as voxels
My link

[NightFright]

After Borion is finished with doing some QA work on the voxels, DJP's cleaver and knife are now on Github. Thanks a lot for the contribution!

[LeoD]

Hi @Borion,
could you please do me a favour?

I need a cubic, hollow, dice-like voxel model for my test/calibration/bug hunting map. My "flat version":

The inner structure should be some 3d-cross, with the beams ending in the centre of each side.

Side "5" should look like this, for example:

1 square = 1 voxel

I hope this isn't asked too much, at least if your voxel tool has good copy/paste capabilities.

[Striker]

Borion, on 27 April 2020 - 03:52 AM, said:

That link was posted as proof of concept. You made it clear guys that You don't want/need voxelized enemies and as Dzierzan said, it would be insane amount of work.

There is only one enemy that I'm sure I will voxelize - Pigcop Car. I can't stand how flat it looks while hovering in place & shooting. In this one moment when whole illusion of mass is gone. I think due to the height in relation to ground level and length of "car". Contrary to Cacodemon or Gargoyle from Blood, this one has not optimal shape for 2.5D trickery, IMO.

I won't forgo work on props, there are still at least 20-30 objects that need voxelization. Just pipes in all variations are 15 models. I think I will take care of few more objects and take a break for a while. By break I mean making i.e. Duke64 or Caribbean stuff

Fox, what do you mean by palette issues? 3DR used different palette for N64 port?

EDIt: typos

Personally, I think you can do whatever you want. Props should take priority, yeah, but if you want to do enemies too and feel like you're up to the challenge, I'd say knock yourself out.

[Borion]

LeoD, on 06 May 2020 - 10:30 AM, said:

Hi @Borion,
could you please do me a favour?

I need a cubic, hollow, dice-like voxel model for my test/calibration/bug hunting map. My "flat version":
mhkalib.jpg
The inner structure should be some 3d-cross, with the beams ending in the centre of each side.
3dcross.jpg
Side "5" should look like this, for example:
mhkalib.png
1 square = 1 voxel

I hope this isn't asked too much, at least if your voxel tool has good copy/paste capabilities.

Sure, I will do it as soon as I can. But I'm totally hammered by work stuff ATM, Leo.

Striker, on 06 May 2020 - 09:50 PM, said:

Personally, I think you can do whatever you want. Props should take priority, yeah, but if you want to do enemies too and feel like you're up to the challenge, I'd say knock yourself out.

Hi Striker
Making VP props set 'feature complete' has priority for me. About enemies & other stuff, I wan't to experiment with other Build games (besides Pig Car).

[LeoD]

Borion, on 09 May 2020 - 12:58 AM, said:

Sure, I will do it as soon as I can. But I'm totally hammered by work stuff ATM, Leo.

No need to hurry. Not urgent right now, but really nice to have.

[LeoD]

@NightFright
It's a good time to rebase the Voxel Pack's maphacks on the HRP svn727 revision, and re-apply your patches (not so many yet, IIRC). I think I've made all conceivable fixes and improvements that could be achieved without actually replaying all the maps.

[NightFright]

Maphacks update done. Hopefully this won't be necessary again, but to be on the safe side, I have created an internal document for myself listing all edits I have applied to HRP maphacks.

I am attaching it here, also for backup purposes in case I lose the document for some weird and unpredictable reason:

Spoiler

=============================================================================
E1L1.mhk
=============================================================================
[edit] sprite 348 angoff 512 --> 1024 // tile0925 neon1 (cinema)
[comment] sprite 399 angoff -512 // tile0925 neon1 (cinema)

=============================================================================
E1L1_13d.mhk
=============================================================================
[edit] sprite 346 angoff 512 --> 1024 // tile0925 neon1 (cinema)
[comment] sprite 397 angoff -512 // tile0925 neon1 (cinema)

=============================================================================
E1L1_worldtour.mhk
=============================================================================
[edit] sprite 347 angoff 512 --> 1024 // tile0925 neon1 (cinema)
[comment] sprite 398 angoff -512 // tile0925 neon1 (cinema)

=============================================================================
nwl2-1997.mhk
=============================================================================
[edit] sprite 445 angoff 512 --> 1024 // tile0925 neon1 (cinema)
[comment] sprite 493 angoff -512 // tile0925 neon1 (cinema)

=============================================================================
nwl2-megaton.mhk
=============================================================================
[edit] sprite 441 angoff 512 --> 1024 // tile0925 neon1 (cinema)
[comment] sprite 489 angoff -512 // tile0925 neon1 (cinema)

=============================================================================
nwl2-r70.mhk
=============================================================================
[edit] sprite 437 angoff 512 --> 1024 // tile0925 neon1 (cinema)
[comment] sprite 485 angoff -512 // tile0925 neon1 (cinema)

=============================================================================
E3L4.mhk
=============================================================================
[add] sprite 395 angoff -768 // tile0678 scale

=============================================================================
E3L4_worldtour.mhk
=============================================================================
[add] sprite 384 angoff -768 // tile0678 scale

=============================================================================
E3L7.mhk
=============================================================================
[edit] sprite 144 angoff -128 --> -384 // tile0607 antenna

=============================================================================
E3L7_worldtour.mhk
=============================================================================
[edit] sprite 143 angoff -128 --> -384 // tile0607 antenna

=============================================================================
E4L5.mhk
=============================================================================
[add] // Voxel Pack additions
[add] // sprite 83 angoff 1024 // tile4443 (flag)
[add] sprite 477 angoff -512 // tile4377 policelightpole
[add] sprite 478 angoff -512 // tile4377 policelightpole

=============================================================================
E4L5_worldtour.mhk
=============================================================================
[add] // Voxel Pack additions
[add] // sprite 82 angoff 1024 // tile4443 (flag)
[add] sprite 474 angoff -512 // tile4377 policelightpole
[add] sprite 475 angoff -512 // tile4377 policelightpole

=============================================================================
E4L8.mhk
=============================================================================
[edit] sprite 335 angoff -256 --> -512 // tile4443 (flag)

[Jan Satcitananda]

Borion, on 16 April 2020 - 04:25 PM, said:

Bravo! Your contributions have actually put this glorious pack to a conceptually new level.

Isn't that little toggle switch supposed to be flipped once the tripmine is attached to a wall and activated? Note that the large tripbomb sprite was primarily intended for use by the HUD graphics (hence its relatively high resolution), and the ingame sprite was apparently kept the same to save memory. As long as you've got a separate voxel model for the ingame sprite, why not make the switch flipped up and the blue LED glowing?

[Borion]

LeoD, on 10 May 2020 - 06:59 AM, said:

No need to hurry. Not urgent right now, but really nice to have.

Hey Leo, catch!

Side size 32 voxels:
https://mega.nz/file...1IWF-1xVC_vRjnc
Side size 64 voxels:
https://mega.nz/file...qrD8f3eZiOq1C9s

Let me know if it is as you described.

Jan Satcitananda, on 11 June 2020 - 03:02 AM, said:

Bravo! Your contributions have actually put this glorious pack to a conceptually new level.

Isn't that little toggle switch supposed to be flipped once the tripmine is attached to a wall and activated? Note that the large tripbomb sprite was primarily intended for use by the HUD graphics (hence its relatively high resolution), and the ingame sprite was apparently kept the same to save memory. As long as you've got a separate voxel model for the ingame sprite, why not make the switch flipped up and the blue LED glowing?

Thanks! : )

@switch flipping - IMO good idea

[Searinox Navras]

There was a post back many pages about the voxel pack not working with EDuke32 + 20AWT GRP file + Compatibility Stopgap and someone suggested that in addition to voxels being enabled in graphics menu and the presence of "duke3d_voxels.zip" in the autoload folder, the file "e32wt.def" should also have "include duke32_voxels.def" at the end. I did this but the voxels still aren't working. They are mentioned as loaded in the launch splash screen log and the option for Voxels appears in the menu but all I see everywhere is still the old sprites. That was years back though. Is something different now?

Loading "e32wt.def"
............Duke3D Voxel Pack v1.3
.....
Definitions file "e32wt.def" loaded in 262 ms.

I then added the "e32wt_voxel.zip" which is mentioned in the Compatibility Stopgap thread. Still not working, except unlike the voxel pack I get a feeling e32wt_voxel isn't being loaded at all(nothing in logs). Anything I can do about that?

[NightFright]

If the stopgap is loaded after the voxel pack and contains a duke3d.def, it will override the one from the voxel pack. In that case, you would have to add these lines to duke3d.def in the stopgap:

https://github.com/N...ster/duke3d.def

Anyway, if you aren't using the latest stopgap, you should do so now since it's finally fully working, provided you are using a recent EDuke32 snapshot.

[Searinox Navras]

NightFright, on 12 June 2020 - 09:12 AM, said:

If the stopgap is loaded after the voxel pack and contains a duke3d.def, it will override the one from the voxel pack. In that case, you would have to add these lines to duke3d.def in the stopgap:

https://github.com/N...ster/duke3d.def

Anyway, if you aren't using the latest stopgap, you should do so now since it's finally fully working, provided you are using a recent EDuke32 snapshot.

I am using the latest stopgap and an eduke32 from a week ago. I do not have a duke3d.def in the folder, only an e32wt.def. I created one and put the text you linked in mine. Still not working.

[NightFright]

If you are using the Polymer renderer, voxels also won't show.

[LeoD]

Borion, on 12 June 2020 - 06:48 AM, said:

Hey Leo, catch!

Thanks, man! Great job. (Looks really nasty in classic mode when you're close.)

Borion, on 12 June 2020 - 06:48 AM, said:

Let me know if it is as you described.

Almost. The dots on the sides are supposed to match the side number dice-like: 1,2,3,4,5,6. Currently it's always 5. No big deal though. I'm happy.

[Borion]

LeoD, on 14 June 2020 - 08:52 AM, said:

Thanks, man! Great job. (Looks really nasty in classic mode when you're close.)

Almost. The dots on the sides are supposed to match the side number dice-like: 1,2,3,4,5,6. Currently it's always 5. No big deal though. I'm happy.

No problem!
I thought those dots were sth different...I'll fix them soon, it is not a big deal.

[NightFright]

Is there a demand for another pre-release? I guess right now would be a good time during Borion's productive break, plus we just added updated maphacks.

[Darkus]

I found small problems, concerning two models:

The original shrinker sprite is a bit lowered compared to the expander:



However, the voxel model is on the same height:



Also the geisha statue (tile 753), has a white line on the back:

[ReaperMan]

Id, say the shrinker and expander being at the same height fixes an error originally in the game.

[NightFright]

Agreed. It's basically the same sprite/model, so height should be the same. In the original maps you just can't see this difference since there are no Expander pickups, just ammo. The geisha statue back may be worth looking into, though.

[Fox]

The y-offset seems intended to be used with cstat 128 (half-centered).

[NightFright]

Just noticed the "satellite dish" of the ammo on Expander should be considerably bigger. At least if you want to match the sprite. However, I guess the idea was to match ammo and weapon model somehow.

[Jimmy]

Yeah the sprite is grossly inaccurate because it's just a shitty copy paste job of the ammo behind the shrinker sprite. It's only used in multiplayer so no one really ever noticed. Take note that the satellite dish is at the wrong angle on the sprite, but the proper angle on the voxel.

[NightFright]

Didn't even notice the different angle on the weapon at first. Borion did everything right with the Expander, then. It's great that the voxel pack is not only an improvement over the sprites due to voxels being 3D, but also concept-wise.

[Jimmy]

Indeed. The job that has been done here by everyone is commendable, not only has accuracy been a priority (even to a pedantic level sometimes) but mods and maps that don't even exist yet have been taken into consideration. I love this project.

[ReaperMan]

jimmy is a stupid fuck, on 22 June 2020 - 11:32 AM, said:

... not only has accuracy been a priority (even to a pedantic level sometimes)...

I think we can agree that was the right choice, it avoided creating a mish-mash of assets like the HRP has. There's a lot of great models in there but you can tell different people made them.

[Doom64hunter]

jimmy is a stupid fuck, on 21 June 2020 - 12:48 PM, said:

Yeah the sprite is grossly inaccurate because it's just a shitty copy paste job of the ammo behind the shrinker sprite. It's only used in multiplayer so no one really ever noticed. Take note that the satellite dish is at the wrong angle on the sprite, but the proper angle on the voxel.

Funnily enough the satellite dish on the ammo sprite is itself just a copy-paste of the HUD weapon tile, which is why it's angled that way in the first place.