That was a bit of a hussle. I'm not exactly sure what happens, but for some reason the g_lavagun skin keeps interfering with the player skin.

I tried different placements of it in the merging file, but even from the corners it kept crunching the player's back.
For me I wouldn't mind, as it's just a small side of the gun. It takes more time to scale it and make it move accordingly the shotgun.(compare before delete).

I don't have an explanation for it, my weapons just load fully aside from the orginal.
Solution I found is load the model in the Quark4.07, clip the brushes in the skin view so you see vertex points light. Then slowly turn them back to left so they don't tresspass the ones of the player skin. Takes some skill

c0burnplayer 

@madfox, you're an absolute star. Thank you very much. 

You're welcome! 

https://drive.google.com/open?id=0B9DxOfPvG2G1RDdoY0wtTzU5RW8

Changes: new hand, improved lighting, skin pixelings. The last one cost me the most time for the least amount of visible change, as always.

Source files are included. Ignore the hammer, it's unfinished. The stock id1 axe wasn't updated with the hand mesh and rigging improvements I made when molesting the AD axe, so it's a little obsolete.

I had to unmangle the original shadaxe from what the MDL format did to it, then the model was animated from scratch, and then it was mangled again during exporting => the shape might not be exactly like it was.

Since the hand that I made takes more space on the skin, I had to cut the second side of the blade. I could make the skin bigger, but I wanted its size to be power of two, and preferably not very ridiculous. I wanted to reinclude the second half for the pickup model, but I'm too tired after doing cruel and unusual things to 7 subtly different versions of the first half.

http://i.imgur.com/xdBH3Az.png 

That looks amazing, I use all of your weapon mdl revamps so I am excited to check this out later! 

The hand still needs work, I think. It was supposed to be the main (or even the only) improvement, but got neglected in the end. 

Dwere,

I want to let you know your SSG model is my favorite. Love the small details done there.

And to Skiffy,

Your HD shambler is irreplaceable and a must have whenever I reinstall quake anywhere. I hope you are still continuing with the vore work but I lost track of any updates/cancellations. 

Which one? I made two sets - one stock-ish, one completely different (lever-action).

Regardless, thanks for the kind words. 

Needs to be made for all these cool models! 

The model with the subtle wooden details on the sides? At least I think it is wood!

Also that reminds me, I recall you talking about some animations or the like you use for Quake and shared them somewhere but I can't find where... 

This reminds me of the sock's updated SSG in AD (view model). Its forestock looks more like wood than the one on the original id model.

I like it, but it's not mine.

I made the 1.5 pickup model though, except the version that's present there is obsolete and I hate it.

Also that reminds me, I recall you talking about some animations or the like you use for Quake and shared them somewhere but I can't find where...

Not sure what those could be. Maybe someone else said it? 

Nope it's yours!

I just tested and compared with 1.5 and then adding your pak. I was mistaken, the brown "wood" is from the subtle brown reflection or what have you that the detailing on the sides gives (My favorite part)

But AD's is indeed wooden I do see that now.

-Hmm, I have no idea about my other question it was just an offering in a random thread...oh well! 

I created a folder using a static model.
Therefore, a space with an additional block, in which there are two entities with their own skin.
The exterior is an animated sky texture space.
When I compile the directory without lighting, so good.
When I using light, the two models are suddenly the animated sky colored texture, not their own skin.

How can I avoid this, or doing wrong? 

Never encountered this effect before with light.exe. 

Models take their light values from the surface directly below them. Even though a sky texture is always drawn at the same brightness, that doesn't give it a light level automatically. Replace the sky brush on the bottom of the map with a normal solid brush, add some lights until it is lit correctly and the models look OK, then place a thin sky brush on top of it to restore the appearance. 

I placed lights right under the info_static, but for some reason these only give a dim glow.
Covering the bottom brush seem to give the light a chance, but as it's such a large distance, I found my skill with the sky light in worldspan.

Thanks for the hint, Preach!

starlog 

I've been modelling quiet some time now for Quake1 models, but there's one thing that keeps on erratum.

After creating my model frames according their position, and adding the corresponding qc in game the model refuses to die.
The first hits relate with blood gibs, but after three shots the model just animates on, without dying.

model 

The error is in wocat_die, and it's something that the function is missing. Compare it line by line to shalrath_die and see what is missing in your function. 

forget statement, me donkey. 

To change a func's ability can be easy done with target & targetnames.
What if I want to change the ability of a static entity?
I can't use the target arguments in game as it is a static.

So if there were four kind of animation frames, how would I add a qc, that defines the static entity for its specific argues in game?
So I could use the certain animations from one entity by togling?

Or does a static stays a static, except killframed. 

When you make an entity static, you are giving up the ability to change it in any way. You can't even killtarget it!

But with the right QC code you can make a model appear without needing it to be static. Most entities in the game have models and are not static entities. For example, if you make a map in Quoth and add a mapobject_custom, you can see that it does most of what you need it to do. If you trigger it, the model will switch from frame 0 to frame 1. Trigger it again and it goes back to 0. If you killtarget it then it will disappear.

The QuakeC code for this entity is really simple, it's basically copying the code for func_wall and func_wall_use then deleting the lines that make it solid.

To go from 2 frames to 4 frame, the difficult part is planning how you want it to work. Can the mapper decide which frame should appear next each time they trigger it, or do the 4 frames always cycle round in the same sequence? When you have a clear plan of what you want out of the entity, I can help with the coding parts. 

Is it possible to use some of dwere's new weapon models (for example the shotgun) in Arcane Dimensions and The Forgotten Sepulcher? 

 

I making and testing map with gamma 0.75 in quake. Thinking i have some dark places and more middle-dark places.What gamma do you play and is the recommended value of gamma?
tnx 

...for me. Open Quake's Start map (start.bsp) and compare your map to it's lighting. That's how I tell id things are too dark.