The WIP Thread

[InsanityBringer]

I don't know why it didn't work before for you, or why Doom might have opted for using multiple UDP ports. But just to help clarify how UDP sockets works: an UDP socket is listening on a single port. Anything the socket sends will have that port as its source port. Anything the computer receives on that port will be received regardless of what the sender IP and port was. If you don't bind a listen port explicitly, the system will pick a free port number the first time you send a message from the socket.

In other words, when you call recvfrom on an UDP socket you'll get the information (IP address and port) about where the message was sent from. You can have multiple other peers sending to your socket where you can use their IP+port for looking up which peer it came from. And you can send messages back to each of those without needing a port for each, by supplying the IP+port of the destination when you call sendto.

now things are starting to make more sense. I have something that seems to run somewhat reliably on a LAN so far, but there's still a lot of testing and the like I need to do to ensure reliably, and then I need to beat the actual netcode into shape to excise all the remaining IPX assumptions.

Also I ended up implementing this with Winsock, since I looked at things like SDL_net and saw there's only like 10 functions I'd be calling in a UDP environment, so I figured it would be easy to roll manually for each platform. Though this was the right choice, it's been slightly annoying since the Winsock documentation is full of holes, missing data, TBDs, and so on. That was fun to deal with...

[dpJudas]

Glad to hear you're making progress, InsanityBringer. Descent was my favorite multiplayer game until UT99 came out - I have a lot of fond memories from playing it with my friends.

On a different subject, how about a game of Frozen Time with the software renderer?

[Graf Zahl]

How did you get 79 fps there?

[dpJudas]

Fixed the crash bugs in r_scene_multithreaded, removed the drawer threads (r_multithreaded) to get rid of some overhead, and ran it on a Ryzen 5950X (16 core zen 3). End result: it splits the scene including the BSP into 32 slices and renders each slice on its own thread.

I get similar speeds in Eviternity. Best result is for Brigandine where geometry is heavily spread all over the viewport at all times, which results in all parts of the map to run consistently at over 200 FPS on my computer.

[drfrag]

Cool.

[Kinsie]

Fixed the crash bugs in r_scene_multithreaded, removed the drawer threads (r_multithreaded) to get rid of some overhead, and ran it on a Ryzen 5950X (16 core zen 3). End result: it splits the scene including the BSP into 32 slices and renders each slice on its own thread.

Neat! Sounds like the sort of multithreaded rendering Gooberman's been experimenting with in Rum & Raisin Doom, his Chocolate Doom fork. You ought to confer with him if you haven't.

[dpJudas]

Yes it is exactly what his fork was doing. Note however that r_scene_multithreaded is several years older than his fork. It just wasn't ever enabled due to certain bugs preventing it to become an official feature. There isn't really much to learn from his fork here since the real problem isn't the idea, but rather executing it with GZDoom's far more complex code base. The only really noteworthy thing to copy from his fork is the framebuffer transpose, but that means breaking the 'constant Z' rule for flats. It is doable but requires some work where I once again can't really use anything from his fork.

[TiberiumSoul]

I'm just going to leave these here... Mostly because I don't want to bump the remaster thread.

---

A Webley Fosbery sits by the campfire... Seems that its owner wasn't fast enough on their reload... We'll have to do better then, now won't we?

---

A fine demonstration of why Shotgunners were the most OP Loadout Class in WW1 and why Germany wanted them all banned from the server...
Jokes aside, this is the player's answer to the Darkmoon Cultist's Sawn-off Shotgun, a Winchester M1897 Trenchgun, And as you can see... It fucking shreds.

[MyNameIs]

i'm working on a cyberpunk-ish HotlineMiami-Warframe inspired thing with focus on speed and vertical movement
no map yet tho

(thing starts at 0:12, you can ignore stuff before that timestamp)

[Captain J]

Hella impressive. Is the baddies have 3d model but with some kind of custom rotation behavior? Never seen like this before.

[MyNameIs]

Hella impressive. Is the baddies have 3d model but with some kind of custom rotation behavior? Never seen like this before.

i'm changing its SpriteRotation, works with models too. sadly it can't be interpolated i guess, so it's noticeably "lags" if fps is greater than 35.

anyways, it's looks like shit when you're upclose, even more if model's height is small (like weapons, or if enemy is lying), so i think i won't use that in the end.

[RailedRobin]

Working on a hub area where you enter teleporters to go to different episodes/maps. Currently working on how the teleporter will look.
Everything is just for test atm, and I will of course change textures and such. And the mess at the end is because I was playing around with brightmaps..

https://imgur.com/VdjdX3W

[Stopsignal]

i'm working on a cyberpunk-ish HotlineMiami-Warframe inspired thing with focus on speed and vertical movement
no map yet tho

(thing starts at 0:12, you can ignore stuff before that timestamp)

That looks fantastic.
I'd suggest a mechanic in order to regain life (maybe using the combos? that would encourage always moving forward and playing stylishly) as you stopping to get those healthpacks brought the pace to a complete halt. Otherwise, it's got fantastic flow, i'm playing that!

[KynikossDragonn]

So I just had the amazing discovery of Nem's Terrain Builder working under Wine finally when Wine 6.2 came out with Wine Mono 6.0.0:


So now I'm remaking a really dumb map I made in 2007:


Yes, it's as large as UnrealEd allows brushes to exist within grid coordinates.

The terrain brush I made is 512 polys and extends to 32767,-32767. While I was making the terrain I had the snap set to every 128 increments. This surprisingly does not generate BSP errors everywhere.

Also yes, UnrealEd 1 barely functions at all under recent versions of Wine, but even in this broken state I can still work on maps.

[MyNameIs]

I'd suggest a mechanic in order to regain life (maybe using the combos? that would encourage always moving forward and playing stylishly)

that's a great idea! it would be pretty hard to balance though