Southkraut
A tale Told by an idiot, full of sound and fury, Signifying nothing.
All alliterations are accidental.
User ID: 83
K&R, accept no substitutes.
It's logically consistent, space-efficient, orderly and readable. The others don't even come close.
As for people being naked in locker rooms, I'd be happy to see the practice die out.
Then how the fuck are you supposed to change out of your wet/sweaty/dirty clothes?
This. Discord is their domain.
I thought that was the general consensus.
It is. I posted late at night and was tired and got dumb and messed up my Englisch to the point of stating the opposite of what I intended. Contend, contest, contradict...Nach Müd kommt Blöd.
Lots of time wasted on engine switching and reconsideration. Better focus more on disassociation from engine even at cost to performance. Said this before, but optimization always draws me towards tighter integration - need to not do that. A cleaner separation with minimal engine specificity (is that a word?). Don't let the siren song of premature optimization lure me from the good path.
Is there a way to do C++ without header files? I realize it's incredibly petty, but having two files per class just keeps turning me off of Unreal.
Other than that, I keep comparing engines.
Unity:
- C# as a scripting language.
- Single-precision coordinate system only.
- Messy development, priorities of the Unity company are unclear, future is uncertain.
- Documentation is pretty decent.
- Has a live scene editor.
- Many features are semi-maintained only and better not used.
Unreal:
- C++ as scripting language. Big meh. I just don't find it fun to work with.
- Overengineered editor and blueprint system keeps getting in the way.
- Huge file size and memory footprint.
- Amazing features; would anyone contend that this is the most powerful engine?
- Double-precision coordinates out of the box.
- Documentation is OK, but surprisingly thin on many features. Seems to live mostly in youtube videos.
Godot:
- Does support C# scripting AND double-precision coordinates...but good luck getting that to compile, nevermind getting support for it when it bugs out.
- Engine
- Documentation is OK.
- Community is very actively woke.
- Has a bunch of bugs.
- Amazingly small file size and resource consumption.
- No live editor.
Redot:
- Like Godot, minus the politics but I'm not sure how long it'll live.
Stride:
- Engine written in C#, open source, and scripting is in C#. C# versions are up to date. It's a dream come true.
- No live editor.
- No double-precision coordinates.
- Very buggy.
- The documentation is completely worthless.
- The community is agreeable but doesn't have the manpower and/or time to bring the engine up to scratch.
- Even if I don't use the engine itself I can cannibalize many utility classes of theirs and even learn a thing or two about efficient C#!
No idea where I'm going with this. Right now I'm trying to fiddle some dev time into my new routines. Not yet sure how to. Maybe I'll just get used to the job and end up being less weary by the end of the workday so I can get something done in the evenings, or maybe I'll follow a friend's recommendation and just get up even earlier to do some coding in the mornings. Or maybe I'll find a way to take a few short breaks (legitimate breaks, not slacking off.) during work to...I don't know, dictate code to my phone?
which I remember @Southkraut taking great offense at for reasons that still strike me as insufficiently thought through
They are. The thought terminates at "Rightful German clay must remain in German hands."
And then he was replaced by a lesbian, and many an article was written about it.
Surprised I never heard of this on the Motte.
Sorry for being unavailable, by the way. My excuses are kid's joining Kindergarten and I started at a new time-consuming job.
What even is the message?
Redot
I'm happy to hear it. If they can make it so that compiling for double-precision AND C# actually works, then they're winners in my book. I'll check it out once I've established a new weekly routine that makes some suitable time for sitting down and tinkering.
@Southkraut, you mentioned you probably wouldn't have time over the past week, but I'll traditionally ask how are you doing anyway.
Thanks for asking, and please do keep it up, even though it's a bit of a drought right now. I did not get around to anything at all - I was always at work, or making up for my absence by going full hog on dad duty, or just plain tuckered out.
Can you elaborate on this. I think I know what you mean, but I don't know what consequences, if any, it would have on picking an Engine, for example.
It wouldn't. It's not related to the engine question. It's rather a change in how I approach my cluster of projects, and a change that snuck up on me and I only recognized it long after it happened. Let me illustrate the comparison a little.
Old: There are many Physical Entities. All these entities have complex physical properties and interactions. All these entities are always rendered and physically simulated. Some of those entities may contain so-called Functional Structures. Some of those Functional Structures might support Behaviors. Some of those might be Agents, who actually act upon the game world. All their actions and interactions go through the physical properties of their Physical Entities.
New: There are many agents. All these agents have goals and sets of possible actions. Some of those agents have physical bodies. But the actions and interactions of the agents only account for their physical bodies in the broadest sense, i.e., usually just location. Those physical bodies that are very close to the player's location are actually rendered and physically simulated, but the abstract behavior of the agents has priority over the physics simulation, and they can interact with non-rendered, non-physically-simulated agents just fine.
Also, congrats on the new job! I recall you posted about being burned out with the old one a while back. I've been in a similar position not long ago, so I'm glad to hear you took matters into your own hands, and hope the new job is a better fit.
I didn't really take the initiative on this until the last job really started falling apart, but it's still a sound improvement overall. Better salary, conditions, benefits, location, and most importantly I get along with my new colleagues very well, which was sadly not really the case in the old job. That last point is very important to me; I'm much more motivated when people I actually like depend on me. I'm also on premises all the time, which helps a lot with actually focusing on the job - no more distractions on the home front. The work itself is extremely dry and technically uninteresting, but I suppose you can't have it all. I'm honestly surprising myself with how easily I manage to adapt to the new working conditions after four years of practically pure home office, and how much energy I can muster for work after so much time spent just dragging myself along in a job I hated. It's nice. Exhausing, too, but I'm happier than I've been in a long time.
How did your similar situation turn out?
I'm strongly considering going back to Unity or Godot. Stride is a documentation disaster that obscures whatever technological disaster may be going on below. I suppose there's a reason why Distant Worlds 2 is the only halfway well-known game to have been made with Stride, and it's a strange example because it's both based on a unique fork of the Engine and, frankly, technologically the opposite of impressive. Stride is halfway between a community project kept alive by plucky contributors and straight-up abandonware. It's a post-apocalyptic vision of a Game Engine, where the original creators are no longer around and the people who maintain it now have only very limited insight into how it all works. It's a hard sell when there are alternatives that actually work out of the box.
That said, an open-source Engine that's built from the ground up to consist of and support the latest C# is a pretty great pitch to my ears. Amazing in concept. Sadly it increasingly looks like I can't live with the implementation.
I've drawn up a spreadsheet comparing the various engines. Their strengths, their weaknesses, my personal problems with them. Color-coded it, too. It didn't help. Everything is distinctly lacking in one way or another. Trade-offs will have to be made.
Looking back upon my Unity project and comparing it to my current Godot/Stride iterations, I am struck by one fundamental difference that wasn't even intentional. My old project is primarily a physics simulation, and whatever abstract logic or behavior happens is a consequence of physical entities interacting. In the new version, everything is abstract entities that possibly project into the physical realm. Huh. I'll need to do some more thinking about this.
Anyways, I just started on a new full-time day job this week and haven't gotten anything done since the weekend, and probably won't see much progress tomorrow either. Maybe on the weekend.
But if one of the issues is giving too much power to people who can't properly wield it--and it has a gender bias--what on earth do we do?
Punish people who scream at babies, regardless of their sex.
"Last enemy wasn't so bad now that we have current enemy" seems like a pattern on both sides.
Leaving, but turning around long before they get there. It will be an in-joke, and we get to make fun of the idiots who actually fly to Alaska.
What do you mean? He all but name-dropped each and every one of us individually and hand-wrote the themotte.org URL on every surface in the world!
Please explain for someone out of the loop.
Same as in Germany, then.
Same problem here. 2nd generation, too - it's certainly genetic. Not overcome it so far. I breathe hard, I often wake up at night from not getting enough air, and I get recurring and long-lasting colds at a rather bothersome frequency especially in cold weather. I can do sports just fine when I'm not having a cold, which sadly means not that often, but breathing is troublesome at rest and at sleep.
Xylometazolinechloride works fantastically at fixing the issue...but is said to make it worse with prolonged use, so I don't.
I once got my face scanned and they detected some deformations in the cartilage of the nose which seems to block one nostril almost entirely, and my Otorhinolaryngologist (do anglos really use that term?) recommends getting surgery to fix it. I've been putting it off. So surgery it will have to be at some point, but my confidence in it actually helping is low since a family member with the same problem had it and still catches a cold practically every other tuesday.
Boo Outgroup?
It's a struggle.
Stride documentation is close to useless and the community may be willing to help but is often unable to do so effectively. There are very simple thing that Stride simply can not do out of the box. When I try to do something with Stride, it usually doesn't work, sometimes works after a lot of fiddling, and often stops working spontaneously for no discernible reason. The elevator pitch of Stride is great, but the reality so far is nothing but frustration. If this is as far as it goes, then at least I was able to cannibalize their code base for a bunch of useful utility code. But actually using the Stride Engine is a pain. Right now I've slowly been able to claw some of what I needed out of the engine, but it was a fight every step of the way.
At least I managed to get a deal of refactoring and other useful reworks done on the way.
I'll need to add a few more workarounds before my control scheme works again (Stride's coordinate system is bizarre; +Z is forward...but Cameras and rotations in general look backwards by default). My procedural meshes work again, but I need to wrestle with Stride's material system a little more before they actually look like something again. Performance is crap right now, but I'm putting that off until later; it's too early for profiling.
Aside from the code, I'm doing some concept work on how agents prioritize tasks, but it's still fairly abstract for the time being. I'm definitely overthinking it.
That's a bit strawmanny, but then again now that I know you're a transsexual (I previously assumed you were a woman or simply a metrosexual) this behavior matches what others of your kind have displayed in the past; the rapidly escalated assumptions of hostility when faced with anything other than affirmation. And instead of asking simple questions and getting worthwhile answers to better understand each other, we can instead pattern-match the other to our preferred ideological enemy group.
Wishful thinkers tend to reinforce each other.
No idea whether it's the case though. I couldn't bring myself to watch that Interview.
Not to be smug, but...that's advertisement.
So why are you doing this yourself?
- Prev
- Next
Fair enough. I don't quite agree but that's more reasonable than it sounded.
More options
Context Copy link