217 karma · joined February 19, 2018
Website: adipa.me
A source available license allowing for personal modifications, sharing with other licensees, contributing fixes that might not be a priority to the dev is present with projects like Unreal Engine and a few other examples I can think of. However they are all bespoke licensing.
Seeing the similarity between this and their previous efforts like WebThings, in terms of providing more open alternatives to upcoming proprietary trends. It's unfortunate they lack follow through and commitment.
This is usually a lot more common in software projects, and it doesn't come across well when most the effort is clearly (at least from a quick overview)from a single person.
Software suites like Houdini, which is something of an industry standard in VFX and gamedev can potentially leverage ML techniques. AFAIK the folks who make Houdini have talked in the past about using ML to improve their terrain heightmap modelling, improving the quality of the erosion etc...
The real value add with using procedural tools to automate creating parts of large worlds (eroded terrain, placement of foliage according to rules) is that it frees up artist time to focus on hand crafting individual locations and detail into the map.
There is an interesting talk from Ubisoft which talks about how they leverage tools for building their large worlds https://www.youtube.com/watch?v=NfizT369g60 (slides: https://ubm-twvideo01.s3.amazonaws.com/o1/vault/gdc2018/pres...)
AFAIK with systems like Unreal's landscape feature, the landscape is not stored to disk as meshes, instead the heightmap and layer masks (for terrain coloration) are stored as textures which are looked up at runtime in order to render the landscape.
Would assume this means its relatively lightweight to store large amounts of terrain to disk compared to storing it as textured meshes.
The only scenarios where this wouldn't be true is if your landscape texture is for example satellite imagery instead of a combination of texture samples blended together at runtime with masks. With Unreal Engine 5's Nanite there is also the the baked Hierarchical Level of Detail meshes which would add to the storage cost.
Notably landscape is excluded from Nanite since the path Epic wants to go down is to continue generating landscape mesh at runtime.
Would love to get some more insight into landscapes in general in game engines :)
Its fascinating when you start looking into any historical time period (you wouldn't even need to go far back), before a lot of details are educated guesses. Since no one chose to record the mundane in detail or it failed to preserve over time.
Really the way I see it outside a few large banking firms, its kind of hard to be sure any provider of digital services would be around in the 50+ year term for this kind of public archive.
I hope the Internet Archive manages it.
EDIT: I do worry the IA has a bit of a lightning rod effect with skirting issues re: legality of archiving content. IMO its no guarantee it survives any significant time span either.
> Terminus is too close to Termius - a commercial terminal app. This causes a number of users to end up on our issue tracker when they're actually looking for help with Termius - it's better to cover your butt before the lawsuit comes than regret it later.
> There's another terminal app that's literally called "Terminus" and is packaged under this name at least in Debian and Ubuntu repos.
> It just rolls of the tongue better
It's not a huge deal in most cases, is a bigger issue if you are running any sort of scheduled ETL to update (or insert new) things.
Since then used it a decent bit as an alternate to Blender for hard surface modelling, like the ability to script stuff up fairly easily (to handle a specific need that I can't find an operator for) etc.., granted its not quite as fast as doing things with things like Boxcutter for Blender.
Is there any specific strategy you follow WRT building JSON parsers that you found lacking in std lib implementations in order consider writing your own?
Quite curious re: the reasoning behind writing the libs and how you even figured it was worth the time effort to consider it in first place.
Impressive performance numbers in general :)
The worst I found was another team which merges in depandabot PR's one by one. Their git history isn't pleasant to look through :(
Usually its junk, but occasionally you do get lucky and find tokens.
Notorious for "Deadpooling", providers sell ultra cheap hosts. Run them on over-provisioned servers for a year or two and disappear overnight.
ex: https://tech.slashdot.org/story/19/12/08/1549222/20-low-end-...
In fairness a decent chunk of the rejected PRs are low effort / not acceptable things.
EDIT: Ah a more plausible reason, it seems the PRs get merged at googlesource and the bot closes them on github
It looks like this Spectre.Console you are using is a bit more fancy albeit a lot newer.
I wonder if they have any interest in bring this to the rest of us, as an extension to the current codeowners feature.
At least locally with idiots pointing lazers near airports usually the culprits get apprehended in fairly short order.
Is it this usual for a repeated event near a busy airport to go on without intervention?
Usually that goes away when you get them to try some of the IDEs, the experience is second to none (as far as IDEs that work extremely well out of the box go).
The amount of times I've got praised for writing neat C# code that was Resharper doing its magic :P
Or at least be a steward in maintaining containers themselves (Dockerhub has the concept of Verified Publishers IIRC).
Worst case here might be lots of containers showing up here that aren't by the same organization maintaining the equivalent Dockerhub containers, would get really annoying to deal with.
Just the sheer amount of interesting games and videos available on places like NewGrounds and Kongregate was something else. It was kind of crazy how easy it was at the time to get at least some attention to any proof of concept project simply by posting onto said sites.
Something that has definitely gotten much harder over time despite the more advanced tools that are available to hobbyists these days.
I think it was a mix of how easy flash made it to go from some vector art drawn in app, to hooking up some key-frames together with logic for a game etc... But it was also IMO strongly influenced by the internet culture at time, where there was (at least it felt like) a larger audience of people available to try out wacky often no/low-budget things.
I haven't quite seen the same environment emerge on places Itch.IO and to an extent Steam.
Now that sounds very cool.
Out of curiosity, do you have any plans to handle things that cannot be local first (for example with YNAB I like the Plaid Integration to pull transactions data out of banking).
Something like that for your application would need to clear through your own API right?
Namely, paying for exclusivity onto their store (or more accurately paying for the developer to not release onto Steam - the current incumbent). I'm not sure how you can argue that they are helping users exercise choice when this is behavior they already engage in.
But almost all third party assets have restrictions, it's not like the assets can have DRM to prevent the paid for asset being redistributed and used in other works.
A compromise I've seen (and what I do with my hobby projects) is to publish source code to github without a FOSS license, so at least the code I write has some value to others to look at, binary assets (including third party) are included in the project over git LFS so its possible to deny access to those by not providing LFS credentials.
An example along the lines is a project I follow a lot, the developer publishes their core gameplay mechanics code as MIT[1] and it's been very useful to me in a UE4 context (for things like understanding good practices re: building larger systems in UE4).
I guess I mean realistically impossible for you to release projects as FOSS but IMO there is still value if you can push any content you do have ownership to in an open way (at least for educational purposes for others).
LaTeX still does a better job out of the box, which goes a long way for my understanding of its typical use cases (resumes or long form reports).
Thanks for the correction.
I'm fairly sure this is incorrect.
Unsure about Lion King specifically but all of the other recent Jon Favreau titles (The Mandalorian, The Jungle Book) have done virtual production with Unreal Engine.