you could solve the rain lerping upwards for one frame by having the drop go to zero scale the frame before and after the upwards lerp.

-metlslime, general abuse thread

nice test, madfox. is it necessary for the flakes to be models or could they be sprites? 

That sounds like black magic... but I like this attitude. 

My first test was with a sprite, but as I haven't fixed the viewframe with it, it keeps turning.
When it are models of a small size it's easy to fill up 124 of them or even more. Only bad is animating as the lot gets me dazzled.

Strange falling startframe without framegroups.

in game 

I made the flakes smaller so the amount is larger. There's that strangle sizzle in the animation, as if the interpolation slides along the stroll. It makes no difference if I use framegroups or not.
So far I'm glad with the result.

Now I bit of turbulence. 

Because the uniformity isn't great (I know it's only a test). And the white colour doesn't suit the quake aesthetic at all. It would probably work on a whole new palette / texture set though.

http://www.howtogeek.com/wp-content/uploads/gg/up/sshot4d2ab8c3eb126.jpg

The concept is interesting to me, I'm fairly sure particle effects would look nicer though. And would maybe be more "quakey". 

.. are a little bit too organized IMHO.
This would need a little bit more of randomness to show up like real snow fall... anyway...
Good try ! Keep it up ! 

It's a static entity of 90 frames and caused by a qc-file. Result is a coloured skin I added, but my main concern is the interpolation.

I know it's been a point in earlier statics I made, but the ignorant collapsing of the first frame destroys the view of it.
It seems to make no difference if I framegroup or not, the first frame keeps on falling back.

They are surely too orginized, but I have to take a little care with the amount of triangles. They now are on 1525verts/1830tris.
So it's more a case of seeing the engine can handle the lots of flakes.

Particle effects would look better, but imagine, this static entity carries 305 flakes.
If it would be individual ones 305 entities would be needed. Now they're closed in as one. 

Just an another stupid idea how to make it more optimal.. would it be possible to make circle raycast check or something, from player to some range.. increasing range more and more, grouping snowflakes and giving them different alpha values.. or just making them much smaller until they dissapear from player's view.. after all player wouldn't notice that if done right. But that should make it much faster I believe.

Hopefully you get the point, sorry my terrible English skills. 

Madfox made a model.

Models can't do raycasting. ;-) 

nononono.. I mean program code? 

I trimmed the flakes into a circling motion so the symetry is broken, but by scaling them out the shape of the flakes become to pronounced.

mdl

In game the large shape is rather out of place, or I should try to make them smaller.

@newhouse- I'm already glad I can spawn the static without typo's. My first idea was to use the viewport to project a transparanr sprite, but that wouldn't have depth.
Maybe a sphere that surrounds the player could catch up with a static ebtity, but as far as I know statics are lame. 

http://imgur.com/gallery/K45sm 

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

New: axe, grenade, nail, super nail.

Changes:

- Lots of tweaks.
- Played around with Edge Split, mostly for source ports that use Gouraud shading in a meaningful way.
- The view weapons should look semi-inoffensive in FOVs up to about 130. In Quakespasm anyway. The value might be lower depending on your engine and settings.

Then there are optimizations of various levels of retarted. They were supposed to make the models look better in software engines, Darkplaces, and the like, without affecting how they look in Quakespasm et al. Results:

- My sources are a mess.
- The result for software engines is underwhelming.
- Darkplaces and DirectQ look serviceable.
- I introduced a very subtle glitch in the intended engines.

Nevertheless, I think it was educational. I probably won't do that again. Making two versions of each model (just like I wanted from the start) would most likely be a better solution. I thought it would make a mess, but now I'm not sure which of the two evils is the better one.

One thing the latter approach would certainly help with is getting 100% OK result for each engine (instead of 99% for half of them, and 80% for the other half).

One thing the current approach is good for is a partial conversion with maps. I wouldn't want to complicate it with two possible setups. Another reason to not redo everything immediately is the fact that I'd have to go over the skins again just to be thorough. Ugh.

Despite all this, I more or less got to the point where I almost don't really hate this thing all that much, so I'm considering it to be one-point-zero. 

 

Incredible work Dwere !!
I like them very much.

If you need some comparism screenshots or gifs, please visit this page:
http://quakeone.com/forums/quake-mod-releases/finished-works/12408-new-faithful-weapon-rework-dwere-da-werecat.html

Thanks again,
Seven 

Heh, wow. Thanks.

Yeah, the gifs are appreciated, since I didn't make such comparisons myself (other than between versions, comparing new models to slightly older new models). 

Very good job, dwere. I'll stick to the hi-poly weapons I have installed but I can definitely see this as a default replacement for id's originals. Well done. 

What is the version you're using ? Where can we find it ? 

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

Fixed subtle glitchy seams where I found them. 

I'm using Ruohi's. Check this link: http://quakeone.com/forums/quake-help/general-help/10727-definitive-hd-replacement-content-list.html
They're the first entry in the "Weapons" section. Two .pk3s to drop in \id1, one for the equipped weapons in the player view and one for the pick-ups. If your engine doesn't support .pk3 format, just unzip them in \id1. 

The link is akward to use, and I need a proper .pak file to work with Quakespasm. And I'm on OS X, so I don't have any tools to make pak files.

Please, could you give a link to a proper weapons PAK file for Quakespasm ? 

Awkward to use? Huh! In what way? I can access the page just fine, even on my phone. The dropbox links to the files are at the top of post #2. pk3 is simply a renamed zip, so you can extract the files and build the pak yourself using a program like PakScape - I have no idea what programs exist on Mac, so the research is up to you. If you still can't manage to sort it out, let me know and I'll see what I can do. 

Thanks,

I successfully downloaded both pk3 files and unzipped them. I'm getting several prog and textures files, that I could drop into the prog and textures folders in the id directory, but they don't show in Quake. I'm not even sure that Quakespasm could use them. I'm unable to find any tools on OS X to make them in a proper PAK file for Quakespasm.

Is it possible for you to try to make a PAK version for Quakespasm ? That would be great ! 

Quakespasm complains about the wrong MDL version number. Apparently, these models are in a modified format or something. 

I made a pak with the files and tested it in QS. It doesn't work. Apparently there needs to be some modification to the progs.dat to make them work, but this goes beyond my knowledge. Use them in Darkplaces or search for info on how to make them work in QS. I'll upload the pak if you want but besides that, I can't help you further. Sorry.