3D Models — dengine Forums

3D Models and Free Textures Resource for Dengine

Paul2025 — Mon, 18 Aug 2025 07:58:11 +0000

Just sending this out there to hopefully find out about some new 3d models and free textures sites. The website has lots of 3D models (some are free) that are great for Dengine game development. It’s packed with a huge variety of assets that are super easy to download and perfect for Dengline. Relebook helps to make your games look amazing without costing too much. It’s a great way to boost your visuals and save time.
3D Models and Free Textures Resource for Dengine: https://3dmodels.relebook.com/model-category/8-1-Game & Movie Character

UV Shells Treated as Hard Edges

NiuHaka — Mon, 30 May 2022 00:36:06 +0000

I’m hoping someone out there can shed some light on this issue.

@skyjake
@veirdo
@Tea Monster
@KuriKai

My models are rendered with some strange lighting issues, as if the angles of some faces or edges are miscalculated. My models are exported from Maya to FBX and then a final save from Motionbuilder.

In these examples it is most noticeable on the shoulders and spikes, but the problem exists all over the model. There seems to be hard edges that I didn’t add to the models along the borders of the funky light directions.
Crazy light inside hard edges on shoulders:

Hard edges on spikes:

Compare those to the same model opened in Maya, which only has the hard edges I added:

Part of the issue is that while it does have the hard edges that I added, I discovered that the outer edges of my UV shells are being treated as hard edges on the mesh… or something.

The blue lines trace some of the intentional Hard edges. The green lines trace some of the strange maybe-hard-edges that are the outer edges of UV shells.

head bobbing model.weapon.

KuriKai — Sun, 14 Mar 2021 05:23:08 +0000

Hey @skyjake is there a way to put in a dei a way to limit the gun sway movement? currently it moves way too much for my shotgun model (me changing the fov may have caused it to look like it's moving more than it should?)

Texture Atlas Border/Padding Size

NiuHaka — Sat, 06 Mar 2021 22:23:46 +0000

Most malevolent Doomsday Mastermind,
In the Optimization Tips section, on the 3D Model Assets page of the manual, it reads:

All textures used by a model are stored in a large atlas. This means there are no restrictions on texture sizes, i.e., they do not have to be powers of two (e.g., 1024×1024). However, because the atlas needs borders and other padding around the textures stored in it, it is recommended that the model's textures are a bit smaller than power-of-two sizes. For instance, four 1000×1000 textures will easily fit on an atlas of 2048×2048; however, only one 1024×1024 texture would fit.

I’m looking for the exact borders and other padding the engine needs for my model textures to be optimized. The “a bit smaller” wording is unsatisfactory to my inferior robotic mind.

My current quandaries:

Would a single pixel difference work, where four textures at 1023x1023 px would fit into a 2048x2048 atlas?
Or, is a single pixel border for all four edges required, where four textures at 1022x1022 px would fit into a 2048x2048 atlas?
Or, is there some other specifications hidden inside “borders and other padding” I should consider when optimizing/maximizing my pixel budget?

HeXen 64 3D Logo Extracted

WhiteMagicRaven — Tue, 03 Mar 2020 23:01:11 +0000

Full Post is Here: http://hexen-game.ru/forum/10-158-25306-16-1583189237
or English here: https://forum.zdoom.org/viewtopic.php?f=37&t=28369&start=60#p1140384

Download: http://raven-05.narod.ru/hexen64j/hexen-64-3d-logo-vrml.7z

Can be opened in Blender 2.78

doomsday 2 new particle system soon?

KuriKai — Sat, 08 Jun 2019 10:15:27 +0000

How far away from using dei for doomsday 2 renderer particles are we? As I would like to release a few models that will need particles (lost soul, baron of hell). It would also help with monster deaths.

The current verido shader we have has a few issues with it and can't be used for bigger flames else it will be noticible

Thanks

Model (FBX & MD5), Texture, Scripting Considerations?

NiuHaka — Sun, 30 Jul 2017 09:59:18 +0000

I'm so excited for DE 2 that i'm starting this thread without regaining my composure so forgive me if I seem a bit giddy/frantic/chaotic/swoony. I wasn't able to discover the answers to these questions but that might be because i'm being a bit hasty at the moment.

Model Considerations:
As I dive into this are there any FBX specific considerations, such as version compatibility, or other limitations that should be made in relation to developing models and animations for DE2?

Textures & Materials:
Are there any new fancy texture effects, and/or shaders (such as glow maps, normal maps, or metallic refraction) available now or coming down the pipeline that I should consider when designing for my new models?

Scripting:
Generally speaking, would the scripts look similar to the way they did for the pre-2.0 versions of DE? Is there very much that will be, or already is, depreciated that I should be aware of? Scripting is not my field of experience so all of my projects past scripts were made possible by harassing the hell out of DaniJ back in the day.

Rendering environment maps ("cubeshot")

skyjake — Tue, 07 Mar 2017 19:21:54 +0000

The next 2.1 unstable build will introduce a new console command to help with 3D model creation.

cubeshot takes the player's current camera position and renders a 6-sided cube map in the format that the Doomsday 2 model renderer uses. For instance

cubeshot 256

writes a PNG file "cubeshot.png" to the runtime folder with the size 1536x256.

Reflection map documentation

Model scripting improvements

skyjake — Sun, 18 Jun 2017 15:42:14 +0000

2.1 unstable build 2360 adds some new functionality for 3D model scripting. I'm currently documenting model scripting on this Manual page: http://dengine.net/manual/assets/scripting_with_stateanimator

A big new feature is that there is now a script callback method for executing code when a mobj switches to a particular state. Previously one could only execute scripts if there was an associated model animation sequence present. Some objects, like power-up artifacts, are actually static models so they don't need animations. It is still useful to know when the artifact has been picked up, for instance.

Also, model scripts can now start specific animation sequences and/or script timelines. This gives a lot of flexibility for example for choosing a specific animation sequence when a monster receives damage. This also makes it possible to start multiple consecutive animations in the timeline script.

record model.thing.misc3 ()
    def onStateChange (animator, state)
        print "State changed:", animator.ID, state
        animator.startTimeline("off")
    end
end

In that example, one could also do something like:

animator.startSequence("attack1")