|
Socoder -> What Have You Done -> What Have You Done? - April 2013 |
|
| Wed, 24 Apr 2013, 04:59 | |
Jayenkai
|
UpsWhat did you get done this month?Did everything turn out as planned? Did it buggery. After the first week's release of StringyThings things took a turn for the worse, as reports of "words not working" started flying thick and fast. It soon became obvious that certain Android devices would funk up images as they're being drawn to the screen, so colours weren't quite working out accurately, and the whole image loader thing was basically fudged. DownsWhat didn't you get done?Why not? Due to my constant reworking of the image colour loader crap, I pretty much wasted two entire weeks, buggering about with the thing. April's been a bit of a let down, to be honest. I'm quite annoyed by the entire experience. NowWhat are you working on right now?I have a fucking Migraine again. Had the bastard since yesterday, and I feel like crap. How's that going? I want to curl up in bed, but that's too boring. Sick of doing that. NextWhat's the plan for the month ahead?--- You can copy+paste the BBCode from the box below, or structure however else you'd like... > Reveal 🔎 -=-=- ''Load, Next List!'' 
|
| Wed, 24 Apr 2013, 10:20 | |
Cower
|
This post is evidence that I don't know how to be concise.UpsWhat did you get done this month.Did everything turn out as planned? re: GLFW_CURSOR_HIDDEN, not exactly, since I found some oddities in GLFW_CURSOR_CAPTURED behavior. The mouse cursor wasn't kept inside the window, so if you clicked after focusing the window while the cursor was outside, you'd lose focus again because the click went to another window. I moved it inside the window when it gains key status, but now you can't move the window without it hurling itself into the corner of the screen. Side-effects. There's really no good way to handle this problem, either. The engine stuff went mostly according to plan. I got client/server communication going in the netcode side of things, though that was mostly an experiment. The server won't be used in the current project since there's no need for it, but the event passing and so on between client/server is still in there. Ideally, the server is just a client with different systems and no renderer, so it's not very special right now. There are also some issues with timing (particularly waiting on netevents, since they may not arrive depending on the timeout used), but that's probably easily solved by using a non-blocking queue and polling in a separate thread (since there's nothing requiring the net code to run on a specific thread). The lexer has gotten a few more updates, but nothing substantial. It's currently being used to parse materials and so on at runtime, so it's fairly handy that it's fast as heck. The material parsing itself is also a bit of an interesting problem since the materials are contained in .mat files that contain zero or more materials. So, you have to scan the material files for the material you're looking for. I ended up doing the scanning at the start of the frameloop (so right after initialization), so the resource manager scans all material files, keeps a map of each material's hashed name to its offset into the file, its length in the file, and its path (the path itself is just an iterator into a set of filepaths). So, when it's needed to load at runtime, it jumps directly to the material offset, parses just that material, and then drops out. This doesn't currently account for changes to material files at runtime (they shouldn't change, and I'm debating whether I can just call that undefined behavior even if it would be handy to reload materials at runtime - it'd be simple enough to check for and reload materials as needed, but it's also a bit of a hassle, so who knows). The console variables/commands thing is more or less the same as those in any of id's engines. They've got some permissions and flags to hint how they're used, but nothing too special. The main reason they're useful is that - with the console mostly implemented - I can set a cvar in one system and it'll be accessible in another. So, any system that wants to kill the client/game just needs to set cl_willQuit to true. Cvars can have delayed updates as well, so setting one's value won't actually alter its value until after a frame is completed (this prevents a few odd side-effects, though it's worth keeping in mind that it will delay stuff by at least one frame). This simplifies a lot of stuff, at any rate. Not much to say about the memory pool. It's a memory pool. I have some ideas for rewriting it to support defragmentation, but I'll only deal with that if it becomes an issue. Swapping out libdispatch was unfortunate but necessary due to it not being a very portable library. I'd already had my own functions for making the transition to a clang-less environment, but TBB accomplishes similar things and does about as well. I'd love to use OpenMP, but that's not really realistic due to lack of compiler support in clang (and possibly Microsoft's compiler, but I'm not porting the engine to Windows anytime soon, so it doesn't matter). DownsWhat didn't you get done?Why not? Classes, depression, boredom, procrastination, and other things I have/do that make me just go back to sleep for very long periods of time. NowWhat are you working on right now?Working through some literary criticism and such for a class. How's that going? It's all completely over my head. I suspect this is because the instructor got their doctorate recently and has lost touch with what undergraduates are capable of understanding. So, it's all mostly gibberish and discussing things we'd need several years of study to understand. NextWhat's the plan for the month ahead?
|
| Wed, 24 Apr 2013, 10:30 | |
steve_ancell
|
UpsWhat did you get done this month.Did everything turn out as planned? Has so far. DownsWhat didn't you get done?Why not? Meh!. NowWhat are you working on right now?Devouring a chicken Tikka Masala. How's that going? Mmm TASTY!. NextWhat's the plan for the month ahead? |
| Wed, 24 Apr 2013, 12:04 | |
|
Afr0 |
View on YouTube
|
| Wed, 24 Apr 2013, 12:46 | |
Dabz
|
UpsWhat did you get done this month.Did everything turn out as planned?  DownsWhat didn't you get done?Why not? Weather was actually okay, so, I obliged, and thus... Coding time took a mega dive fortunately/unfortunately. NowWhat are you working on right now?Sitting typing a "how you doing" post!  How's that going? Just finished it! \o/ Dabz -=-=- Intel Core i5 6400 2.7GHz, NVIDIA GeForce GTX 1070 (8GB), 8Gig DDR4 RAM, 256GB SSD, 1TB HDD, Windows 10 64bit
|
| Thu, 25 Apr 2013, 09:21 | |
waroffice
|
UpsWhat did you get done this month.Did everything turn out as planned? Better than expected but more expensive than I would have liked DownsWhat didn't you get done?Why not? work * lack of sleep + weather NowWhat are you working on right now?PHP/jQuery gallery, ag33k.net/i/newgallery.php you can track progress here How's that going? a learning curve thats not too steep NextWhat's the plan for the month ahead?
|
|
|
| |||
|
| ||||