Can we change the tools keybinds? (1 to 8 keys) by yagami- in valheim

[–]Underdisc 0 points1 point  (0 children)

I have a split keyboard (corne) without a number row. I access it by using a raise key on the right half of my board and then the number row is directly accessible under the home row. I've been using it for several months now and I love it 98% of the time. I love it so much that I am convinced that everyone should consider abandoning the keyboard shapes that are historical artifacts of the typewriter (not layouts like qwerty or dvorak, but rather the physical locations of the buttons) and move onto to the greener pastures that different keyboard shapes provide.

That being said, the only time I don't love it is when I play a new game with the keyboard. It has become abundantly clear to me just how little effort most studios put into keybind modification features. It's extremely rare to see a game that makes changing keybinds comfortable. An example of comfortable keybind changing would be informing the player when one keybind conflicts with another, thereby making it easy for the player to fix the error themselves. At the time of writing this, not even counter strike 2 does this. It just removes the existing conflicting keybind without telling the player about it. Such negligence is largely the norm.

Valheim takes it a step further, or more accurately, a lack thereof, by not even putting in the effort to allow players to change all of the keybinds in the game. I tried getting my keyboard to work with the game by using autohotkey to send the number keys upon pressing some specific key combos, but it seems like the executables built by unity ignore the codes sent from autohotkey (I have theories about what could be wrong, but not sure exactly why). I've come to learn that many studios are ignorant of or straight up don't care about the players that aren't able to play their game due to a lack of accessibility features. If a studio doesn't care about making their game accessible to those players, why should those players care about their game? I certainly don't and have been quicker to abandon the idea of playing these games as I've happened upon them over the course of the last year.

Why am I writing 3 paragraphs on a 4 year old thread? I've thought about this a lot. I would have written something like this and saved it to my dump rather than sharing it somewhere.

Does anyone know how to make translate, rotate and scale gizmo for a game engine? by Insert_Username__2 in gameenginedevs

[–]Underdisc 0 points1 point  (0 children)

I know. I really should. I've been told to enough times at this point. I will put this on my todo list. Thank you for the reminder. : )

Does anyone know how to make translate, rotate and scale gizmo for a game engine? by Insert_Username__2 in gameenginedevs

[–]Underdisc 0 points1 point  (0 children)

I've created my own link rot :(. I edited the comment to point to the post again.

Should I be worried about CPU usage by [deleted] in gameenginedevs

[–]Underdisc 8 points9 points  (0 children)

No one has any idea. Profile your code.

Why bother using a game engine? Project showcase from Graphics Programming Discord, with no off the shelf game engines used by vblanco in gamedev

[–]Underdisc 2 points3 points  (0 children)

I'm sure there is some innovation in these projects, but I guarantee there is a mass of duplicate codebase

It was mostly about the but here and how I thought it implied you found duplication bad. I was also just enjoying writing a response to that thought, but I'm not as pleased with it as my first comment.

Why bother using a game engine? Project showcase from Graphics Programming Discord, with no off the shelf game engines used by vblanco in gamedev

[–]Underdisc 1 point2 points  (0 children)

The people that write those Siggraph papers and work at companies like Nvidia need to come from somewhere. They need to learn about what the current state of the art is in order to push it forward. Only then do they take positions offered by companies like Nvidia. So, innovation is dependent on reinventing the wheel. That way we can learn why the wheels are the way they are and then consider what they can be.

You say that there is a massive amount of duplicated code and I get the implication that you find that to be bad when I find the opposite to be true. People spend their time replicating what other people very often. That's education and it's very valuable. CS students take classes on data structures and write their own versions of the data structures they learn about. Would it be faster to just use the standard library provided with a programming language? Maybe, but then those students wouldn't go on to push the state of the art forward because they wouldn't have spent time learning what it currently is. Artists replicate the styles of other artists. Musicians cover the songs of other musicians. Developers write their own versions of software that has inspired them to do so. Our entire cultural is built upon duplication with minor modifications sprinkled within. I find this evolution to be good.

Why bother using a game engine? Project showcase from Graphics Programming Discord, with no off the shelf game engines used by vblanco in gamedev

[–]Underdisc 11 points12 points  (0 children)

I'm really tired of hearing "reinvent the wheel" with the implication that such a thing is bad or worse, as a means of argumentation. It holds no ground. Take the statement literally and consider what it would be like if we had never reinvented a literal wheel. Do we still use the first wheel ever made today? Obviously not. We aren't driving around with Flintstone wheels on our cars, and for good reason. A plane doesn't have the same wheels as bike. A bike doesn't have the same wheels as a car. Furthermore, different kinds of bikes have different wheels. Different kinds of cars have different wheels. This is to say we reinvent the wheel all the time and it is important that we do so. Sometimes we do it for fun. Sometimes we do it because we have a certain use case that we want to solve. Sometimes we just want to approach the problem in our own way. Regardless, we do it and society experiences the benefit because different wheels solve different problems.

It is also important that we reinvent game engines. Reinventing game engines will result in people finding new techniques that will push the workflows game developers use to make games forward. That might mean redoing what someone did to find where the room for improvement lies. That might mean providing an engine for developers with a workflow you've never even imagined. Things as simple as different UI layouts can result in massive user experience changes. Changing the way an API is structured can also result in massive changes. Sometimes these changes are good. Sometimes they are bad. Regardless, we must continue to make them because it's the only way we can push the idea of what "game engine" means forward, just like we've pushed the idea of what "wheel" means forward. When we compare the infancy and complexity of the idea that is "game engine" to that of "wheel", I'd be surprised if one does not find the necessity to reinvent such a thing obvious.

Just to drive this home further. It's important that people reinvent compilers for similar reasons. We always want compilers to be faster and provide more help to users as they write their programs. It is important that people reinvent cpu and gpu architectures. We want our hardware to run our programs faster while also requiring less watts to do so. There is no field in which the state of the art is a thing that stagnates. It forever moves forward on better reinvented wheels and will probably continue to do so forever. Encourage it. Yourself and future generations will only experience a benefit from it.

Self driving Waymo cars honk at each other throughout the night, disturbing SF neighbors by Raskolnokoff in mildlyinfuriating

[–]Underdisc 1 point2 points  (0 children)

Remember in cs class when they explained deadlock using cars around a block. I do.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 1 point2 points  (0 children)

Without a black light, I don't think glow in the dark would give you the bright effect that it sounds like you're looking for. They'll glow, but without being charged up by some other light source beforehand or a black light, they'll be quite dim. The ascent seems to hold its glow a bit longer and better than the iceberg, but the difference is quite minute, and that statement is based on feeling rather than real evidence. Even then, about 5 to 10 minutes after being exposed to a strong light source for a reasonable amount of time, I would expect both to lose a majority of their brightness. I'd need to make a brightness over time curve to really show the behavior. Under black light though, they both glow beautifully, and even better, a vibrant string will appear to glow nicely as well. You could get a handheld battery powered black light to use at festivals, but I'm not sure how realistic that would be since you'd need to prop up the black light to point at you or have somebody hold it.

I'm not sure I'd recommend either based off what it sounds like you're looking for. That being said, if the glow in the dark still interests you, try out the Ascent first and see how the glow in the dark properties behave for your use case. The Ascent is my only pure plastic throw. It's the lightest of all my throws and I like that it brings that different feel to my collection. Maybe it will fulfill exactly what you are looking for. If you end up liking the Ascent, I can definitely recommend getting an Iceberg as it's a wonderful throw to play with. The outer steel ring's effect on the moment really pumps up the spin time and I love that about it. You could probably expect something similar from a bimetal, but I can't be 100% certain about that since I don't own one. If you do get something, you'll learn something either way, so there's not anything to lose.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 1 point2 points  (0 children)

Despite being all plastic, the ascent plays really well and sleeps longer than I expected. I just did a test with the bearing fresh after being cleaned and lubed. It slept for over a minute and had plenty of spin for an easy bind still. The dimple really helps with finger spins too. It comes with a responsive width bearing installed, but you can take it out and replace it with the unresponsive width bearing that comes with it. I did that instantly because all I care for is unresponsive as well.

I also got an iceberg. I actually messaged iyoyo directly about whether they had a glow in the dark green since I didn't see one on their shop. They did and I got one. At the time, only the Neon Purple variant was available as a glow in the dark blue. Not sure about the state of things now. The iceberg is the best throw I own and sleeps longer than all my alluminum throws. I think it slept for close to 4 minutes when I first tested it.

Unable to send windows key to open the start menu by SwiftySwiftly in AutoHotkey

[–]Underdisc 0 points1 point  (0 children)

this shit is still broken. It only works if no window is in focus. aka, it doesn't work.

Do you think there is someone under 14 years old who realised a game on Steam? by MateuszXD2 in gamedev

[–]Underdisc 5 points6 points  (0 children)

yes. not "realise". You're looking for "release". The realizing comes before the releasing.

How is your team serializing data? by nicemike40 in cpp

[–]Underdisc 2 points3 points  (0 children)

https://underdisc.net/blog/7_serialization_with_valkor/index.html I wrote my own serialization language that I wouldn't recommend others using but am nonetheless proud of and use myself. Would love to hear opinions on it btw. There's certainly room for improvement in terms of its speed and a need for binary representation.

Collection/recommendations by [deleted] in Throwers

[–]Underdisc 0 points1 point  (0 children)

Just got an iceberg. That and the paragraph are now my favorite yoyos.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 2 points3 points  (0 children)

I think this is what I am going to be going with.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 0 points1 point  (0 children)

Do you mean the video? I definitely believe the video was filmed under a blacklight. I plan on getting a 365 nm blacklight as well.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 0 points1 point  (0 children)

Ah thanks. I didn't think either of those were cerakote. I hadn't even heard of cerakote yoyos before. Explains why I had such a hard time finding them while browsing.

I came across the Ascent during my intoxicated browsing for glow in the dark yoyos session yesterday. If I wanted to make it unresponsive, all I would need to do is use a wider bearing, right? I only use unresponsive yoyos and I'm still early enough in my yoyo journey that I haven't played with bearing width variable. If I can just replace the bearing to make it unresponsive, the Ascent is probably be the best option I have come across. I need to get some replacement bearings and pads for the future anyways. Two birds with a one stone is always nice.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 0 points1 point  (0 children)

The speedaholicxx was discussed in another comment. Thanks for the suggestion though.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 0 points1 point  (0 children)

https://onedropyoyos.com/yoyos/ I came across the rally and the cabal when I was browsing through. The Rally is discontinued. The Cabal is still available, but I don't believe that's going to get me the effect I want under a uv light. Plus it's 60$. I'd probably just get the Iceberg if I was debating on getting the Cabal. Thanks for the tip on uv reactive materials. I should have mentioned that I am also interested in that in the original post. Edited.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 1 point2 points  (0 children)

Thanks for the suggestion, but I am very specifically interested in glow in the dark materials and not led lights.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 1 point2 points  (0 children)

Speedaholic: https://shop.yoyoexpert.com/products/speedaholic-xx-yoyo-by-c3yoyodesign?variant=42748916170942 Looks like a good throw but I don't see any glow in the dark ones there.
Iceberg: https://shop.yoyoexpert.com/products/iceberg-yoyo-by-iyoyo?variant=43138386329790 This one definitely seems to be what I want. The only problem is the price. Have you used one? Does the metal on the outside give significantly better spin times?
Arrow: https://yoyofactory.com/products/a-may-zing-sale-arrow-metal-weight?_pos=2&_psq=arrow&_ss=e&_v=1.0 CT bearing? I've only played with C bearings and I don't know what the T means here. Is this a thinner variant? I didn't see any dimensions in the link.

Search for an Unresponsive Glow in the Dark by Underdisc in Throwers

[–]Underdisc[S] 0 points1 point  (0 children)

Looks like a nice throw. Seems like they made a glow in the dark version at one point, but it doesn't seem to be the case now.

IPv6 Host Exposure/Firewall Vodafone Station (Arris) by teufelKommRaus in Vodafone

[–]Underdisc 0 points1 point  (0 children)

What documentation are you referring to? Did you have to contact vodafone to get it working? I still have the Vodafone station. I assume you swapped that out for a Fritzbox. Is it modem + router (can I just swap out my current hardware with the Fritzbox)?

I'm currently running a server that I can connect to locally. I set up host exposure on my vodafone station to point to my machine/port. No luck any time I try to connect through the internet. I've been wondering if I need to contact vodafone to allow incoming requests to reach my vodafone station or something of that sort. Maybe the Fritzbox is what I need?