[jkas789]

Man you have been on a roll!

[Dzierzan]

Added 7935:



I hope Voidpoint will add an option to disable transparency via DEF for voxels, they look like shit in Polymost:

[Dzierzan]

Added 9522 and 9527:

[Striker]

Dzierzan, on 08 October 2021 - 06:09 AM, said:

I hope Voidpoint will add an option to disable transparency via DEF for voxels, they look like shit in Polymost:

Wonder if this can be resolved by some form of backface/occlusion culling? (So only the frontmost faces are drawn) Also, I notice that there's some bugginess, some faces that are supposed to be drawn, aren't...

[Dzierzan]

Leo, according to your suggestion here https://forums.duke4...post__p__366355, I changed pivots for wooden railings to be default. Yeah, I shouldn't have touched those offsets.

I hope you know how to make Pull Request on Github, this would be more convenient for me and good for git history.

A good example why maphacks are needed, double ladder! I know, I know, two sprites for shading. Just one has to be moved underground or disabled (notmd in DEF).

[oasiz]

EDuke32 / VoidSW - r9751
---
8970754aa | [terminx] engine: add "notrans" .def token for voxels to disable drawing with translucency in GL modes

[Dzierzan]

Thank you! Now it looks better in Polymost.

[LeoD]

Dzierzan, on 02 November 2021 - 01:29 PM, said:

I hope you know how to make Pull Request on Github, this would be more convenient for me and good for git history.

Actually no. I've avoided that topic so far. I guess I should learn it now. Do I need to join your project team somehow, like it seems to be necessary with EDuke32, or is a normal GitHub account sufficient?

[Dzierzan]

Everybody can make a pull request, so yeah, a generic account is enough. I recommend using GitKraken, so you don't have to learn git commands and there are simple tutorials for that. Just remember that if you make changes, make a branch using my master branch, newbies can make a pull request using their master branch instead. Technically speaking I can merge that, but it's a better habit making seperate branches.

Make branch (right click on "main"):



Makes changes and stage them, write Summary:



Push your changes:



And then make a pull request (your branch needs to be checked out [being selected]):




If it's too hard or there are issues, I can just take stuff from you in the end.

[LeoD]

Dzierzan, on 06 November 2021 - 07:56 AM, said:

Everybody can make a pull request, so yeah, a generic account is enough. I recommend using GitKraken, so you don't have to learn git commands and there are simple tutorials for that. Just remember that if you make changes, make a branch using my master branch, newbies can make a pull request using their master branch instead. Technically speaking I can merge that, but it's a better habit making seperate branches.
If it's too hard or there are issues, I can just take stuff from you in the end.

Nah, I knew that I would have to get there one day. Since I'm kind of used to TortoiseSVN, and prefer FOSS in general, I'll give TortoiseGit a shot first.

[LeoD]

Initial maphack commit for the IFVP...

Despite an embarrassing lack of understanding I've somewhat found my way around to contributing to Git repos.

Spoiler

After trying out four different clients and the command line, being forced to change my default web browser, creating access tokens, bla, bla, bla, I finally understood that I have to make a fork into my own GitHub account first... noobishness sucks.

Those who've missed it should check out the Ion Fury maphack post I had put into the wrong thread. (Actually it's post #2368 somewhat above; the forum's link creation feature no longer works correctly.)

Compared to the Duke3D HRP and its MD3 models there is probably less work to do, since the pickup voxels are already part of the game's release. On the other hand, there's a lot more detail in the maps.

If you want to check out were I'm heading to, I have prepared a ready-to-use IFVP-with-maphacks sneak-peek you can download here. However, for the time being, "moving" voxels is only provided by a patched executable ('notrans' feature from main branch included). Rename the *.exe of your choice to "fury.exe".
Use/Installation:
- Simply unzip the IFVP into your Ion Fury folder.
OR
- Drop the ZIP into the autoload folder, and add the line "NoAutoLoad = 0" to the [Setup] section of fury.cfg.
OR
- Command line invocation: fury.exe -g IonFuryVoxelPack.zip
OR
- The grpinfo way: create fury-voxelpack-91.grpinfo with the following content, and move away the original fury.grpinfo or rename its extension (like grpinfoX)

Spoiler

grpinfo
{
    name       "Ion Fury 2.0 Voxel Pack 0.0.91"
    size        754427
    crc         0x0CB1192B
    flags       144 // GAMEFLAG_FURY (128 / 0x80) + GAMEFLAG_ADDON (16 / 0x10)
    dependency  0x960B3686 // fury.grp 2.0 CRC
    scriptname "scripts/main.con"
    defname    "fury.def"
}

Your fury.log/eduke32.log should contain one or more lines similar to this after playing:
Loaded map hack file "maphacks/usermaps/foobar.mhk"

The most noteworthy improvements in the few maps I've processed so far can be found in Ionpiercer and in the first original level's (The All-Seeing Eye, z1a1.map) Technoir bar + The Playful Noodle restaurant.

For quick and easy comparisons, this excerpt from my settings.cfg might be interesting:

Spoiler

bind "Kpad*" "god"
bind "Kpad7" "r_voxels 0"
bind "Kpad8" "r_voxels 1"
bind "Kpad4" "map _Maps/_wip.map"
bind "Kpad5" "give all"
bind "Kpad6" "activatecheat 12"
bind "Kpad1" "setrendermode 0"
bind "Kpad2" "setrendermode 3"
bind "Kpad3" "setrendermode 4"
bind "Kpad." "activatecheat 17"
bind "Kpad/" "noclip"
bind "PgUp" "r_models 1"
bind "PgDn" "r_models 0"
bind "Insert" "r_hightile 1"
bind "Delete" "r_hightile 0"

@Dzierzan: about the fence-like sprites mentioned earlier - would you prefer issue reports about the ones I consider to be change-worthy in addition to those WOODEN_RAILINGs, or rather merge requests? (Moving the pivot is my only ability concerning voxels at least.)

[Dzierzan]

Quote

@Dzierzan: about the fence-like sprites mentioned earlier - would you prefer issue reports about the ones I consider to be change-worthy in addition to those WOODEN_RAILINGs, or rather merge requests? (Moving the pivot is my only ability concerning voxels at least.)

Just make pull requests. I trust you in what you are doing.

@Leo
Lamp posts will also require maphacks, as the top is usually misaligned with the base. Anyway, here's the lamp:

[Dzierzan]

BTW Leo, I added new maphacks on my own and they seem to be not working. As a matter of fact, I think maphacks are not loaded at all. Are you able to verify that?

[LeoD]

Dzierzan, on 09 November 2021 - 10:35 AM, said:

BTW Leo, I added new maphacks on my own and they seem to be not working. As a matter of fact, I think maphacks are not loaded at all. Are you able to verify that?

You are right. Check my pull request though (will fix it). In voidpoint_mhk.def, only the existing mhk files are activated so far. Sorry, should have told you. Thanks to syntax highlighting it's obvious to me. C-style comments ( /* */ ) are used. Since there appear to be no warning messages in the log if a defined *.mhk doesn't exist, all MHK could be activated by default, if you prefer that.

Btw, it seems that the 9981/9982 cockroach voxels never show up ingame. They appear upright in Mapster 3D, but as flat textures during gameplay. I assume they are turned floor-aligned upon spawn. The xrepeat/yrepeat values set in Mapster 2D are ignored as well, and they will always be standard size.

[Dzierzan]

Yeah, cockroaches will not render as voxels as they are floor oriented. Pity.

Yeah, let's just add empty maphacks for now. So one will not have to remember about activation.

[LeoD]

Dzierzan, on 09 November 2021 - 11:27 AM, said:

Yeah, let's just add empty maphacks for now. So one will not have to remember about activation.

Done.
You have added the author name to z2a1.mhk. Is there an official list? I have scraped them from tags in 2D mode so far.

[Dzierzan]

Emmm... I did indeed added that, probably I didn't think too much about that. Might be wrong as well.

Now maphacks work for me.

[Dzierzan]

Added 11291 and 10973

[Outtagum]

Dzierzan, on 08 November 2021 - 12:42 PM, said:

[SolivaN]

thanks for this great job men, i love ion fury

[LeoD]

Voxel request : 8163 - 8165
Seems simple - copy/paste the topmost steps of ladders 8280 - 8282

[Dzierzan]

I updated 3 main ladders and I added missing ones.

[Dzierzan]

Added 11427:

[LeoD]

When I found the unicorn I immediately thought that this one should be a voxel model.

[Dzierzan]

Added 3663-3668

[Dzierzan]

Added 11071-11073. Leo, I am sure this will require maphacks because it has seperate sprite for its back.

[Dzierzan]

I voxelized 8294-8299. Well, I didn't expect those sprites to be used like that. I mean in below's case, I thought those were textures or something. What should I do? Leave it like that? It doesn't look that bad.

[LeoD]

Dzierzan, on 07 May 2022 - 01:30 PM, said:

Added 11071-11073. Leo, I am sure this will require maphacks because it has seperate sprite for its back.

Maybe not. See z1a4.map. Sprite #4377 (tile11070 ART) lies within sprite #4376 (11072_METER_ON.kvx) and is invisible. However, a mapper might forget to prevent them from rotating towards the player. I suggest creating 11070_METER_BACK.kvx by removing the two front rows of voxels from 1107?_METER_*.kvx and turning it by 180°. This way it should always be invisible when used in the typical way like in this example. And not flicker like the two-sided railings with different shades.

Dzierzan, on 07 May 2022 - 02:31 PM, said:

I voxelized 8294-8299. Well, I didn't expect those sprites to be used like that. I mean in below's case, I thought those were textures or something. What should I do? Leave it like that? It doesn't look that bad.

Leave it as is. The notmd maphack command is our friend here and I will take care of that. We might reconsider if it should turn out that these are [meant to be] used as sprite-art only, like in that bar.

[LeoD]

Dzierzan, on 07 May 2022 - 02:31 PM, said:

I voxelized 8294-8299. Well, I didn't expect those sprites to be used like that. I mean in below's case, I thought those were textures or something. What should I do? Leave it like that? It doesn't look that bad.

LeoD, on 08 May 2022 - 12:11 AM, said:

Leave it as is. The notmd maphack command is our friend here and I will take care of that. We might reconsider if it should turn out that these are [meant to be] used as sprite-art only, like in that bar.

I chose not to notmd those lamps, but slightly move them inwards. Good compromise I think:

Elsewhere we get quite some additional detail. Btw., I found another 'missing' voxmodel, #06466, maybe has more relatives:

[jkas789]

Just wanted to report a voxel... problem? In the map Fan Service in the following location:



There seems to be 2 voxel fences overlapping each other.



Anyways, thanks for all the hard work dudes. The IF voxel pack is getting better and better.