Just the custom level editor. Game Engine is still Frostbite.

I mean not the engine. But the community level editor for custom maps, sorry for not making that clear. Here is a short tutorial using it: https://www.youtube.com/watch?v=l1LNorfPlNc

I dunno, but there are plenty of other proprietary options, many of which are the actual "industry standard". However, because it is free, blender is the default option for non pros, and some pros are adopting it too.

[Sad 3DSMAX noises]

Yea, I read about it before but never tried it myself. I really hope they have a official "movement" in a similar direction. Cause I don't see that being accepted by "normal" people.

It’s a little more pain [...] oriented

Oh good... just what I wanted.

Krita for me was quite a learning curve, but far more intuitive / with a far better workflow than Gimp once you got used to it. So I'd recommend it too for image editing, though with this, to me, a positive caveat.

It helps that it's also a good engine. Unity dominated not just due to familiarity, but because for a long time it was just plain accessible and feature rich.

Godot and Blender are two applications that have been on a very long journey to build not just advanced features but also something that's intuitive to use. The advancements in UX are the single strongest thing there is in replacing long-standing creative tools.

I actually think AI development is going to close a lot of these gaps faster than people think.

And I think the options for audio and office are pretty decent, LibreOffice definitely does all that I need and there's a healthy community of musicians and audio enthusiasts building things in Linux.

Hardware design and CAD have the additional blockers that they require physical manufacturing and open source hardware has a long, long ways to go. Without an ability to actually produce the physical goods, open source software doesn't go anywhere. Kind of a bootstrapping problem.

• I use FreeCAD and OpenSCAD when you can write code instead of draw.
• Hardware design software is complicated because of hardware patents. For simulation there is Octave, scilab, sympy, einsteinpy and other python projects.
• For video there is openshot.
• For audio production there is Sonic Pi, strudel, where you write music by writing code. There is also audacity and fluidsynth. The problem is with VST plugins but it's also problem of standard because VST was created by Steinberg. There is no single software so you need to juggle.
• For office there are alternatives like OnlyOffice and fork Euro Office, I've seen at least one more office packet from India.

Opensource software have no budget and no money, not to mention marketing budget, people make it to use it and share not to sell it. When company dies you end up with no software if it's cloud based or some installer on deprecated operating system. With opensource you can always take the source code and port it to new OS. One opensource project dies, some other is building on it's ashes. You can't kill it as long as at least one person use it and develops it.

For ex. elastive wave mode solver if you mean dispersion calculator you can load matlab files to Gnu Octave or look up some specific waves by typing above projects I mentioned with github in search.

Of course it's much harder than just type to google what you want and pay money to company that have marketing division and worked out SEO to be first on list. Especially if you have business income that backs it up and limited time, just pay to get it done. It's obvious choice. I assume people are sane. But you can pretty much find all the scientific equivalents on univeristy websites or on github if you really put some effort. It won't be perfect because there was no support that someone paid to solve specific business use case but if you contribute to opensource it will improve and if not you over time someone will do it.

Like someone mentioned the process is much slower but eventually it will always win because it's not so much tied to money.

↘️⬇️↙️

➡️⭕⬅️

↗️⬆️↖️

As someone who came into godot with programming knowledge, the whole signals thing was probably what took the longest to get used to, but now that I understand it it seems very simple. For code, the godot documentation is both accessible on the web and built into the engine, and it's generally very thorough.

Here's an intro guide to programming in godot that I wrote a little while ago:

# If you don’t know how to do something, google it!

# to write a comment, type a hashtag

# lines are executed in sequence

# words typed are variables, and can be assigned by typing "var" and then its name

# GDScript uses the word "var", but leave out "var" in python

var x = 1

var number = 5

# display the value a variable holds

print(number)

# you can do math, with +,-,*,/,% (modulus), ** (exponentiation), sqrt(), etc

print(number / 2)

# variables can be reassigned, by setting them equal to something else

# variables that store numbers can be used as a number

number = 2 / x

number = number - 4

# operations such as the one directly above can be simplified:

number -= 4 #this does the same thing

# variables can also hold:

# true/false (aka Booleans)

var thing = false

# words, etc (aka Strings), surround in quotes

thing = "Hi, I'm Adrian"

# lists of other data types

thing = [number, False, "Hi, I'm Adrian", 52.67]

# access elements of a list by using []

# the first element in a list is element 0

print(thing[1]) # will print False

# you can reassign list elements

thing[1] = True

print(thing) # will print [-6, true, "Hi, I'm Adrian", 52.67]

# you can add elements onto lists with __.append(), remove with __.pop()

thing.append(3.4)

print(thing) # will print [-6, true, "Hi, I'm Adrian", 52.67, 3.4]

thing.pop(2)

print(thing) # will print [-6, true, 52.67, 3.4]

# similarly to how we can do math, we can also evaluate logic (conditionals)

# 'and' will return true only if both inputs are true

# 'or' will return true if either or both inputs are true

var bool1 = false

# remember, thing[2] is now 52.67

# here, thing[2] < 4 is false and bool1 is false

print(thing[2] < 4 or bool1) # will print false as both sides are false

# to compare any data types, you can use == (equal to), != (not equal to)

# to compare numbers, you can use <, >, <= (less than or equal to), >=

# you can also use the words 'or', 'not', 'and'

print(thing[2] != 3 and not bool1) # will print true

# 'If' statements will run code inside of them if they receive the value true

# lines of code inside of the if statement will be indented one level

# you can use the words if, else, elif (else if)

# you can use conditionals here:

if true: 

    print("is true")

#will print "is true"

if thing[2] == 2: 

    print(thing)

    print("as thing[2] == 2, we will not evaluate the rest of the if statement")

elif bool1: # is equivalent to writing "elif bool1 == True"

    print("bool1 is true")

else:

    print("bool1 is not true")

#will print "bool1 is not true"

# Loops operate over ranges and lists (aka iterables)

# ranges work with the format range(stop), range(start,stop), or range(start,stop,step)

# ranges start at 0 and step by 1 by default

for i in range(1,11): 

    print(i)

# will print 1,2,3,4,5,6,7,8,9,10 (stops before 'stop' number)

# lists are also 'iterables'

for i in [1,5,2]: 

    print(i * 2)

# will print 2,10,4

# inside of the for loop, we can access this new variable I have called 'item'

for item in thing: 

    print(item)

# will print -6, true, 52.67, 3.4

# functions allow you to simplify code and remove re-used elements

# you can put multiple things inside of the function's parenthesis,

# which can be used as variables by code inside of your function

# use "func" in GDScript, and "def" in Python

func repeated_sqrt(value, times):

    for i in range(times): #will start at 0 and go up to times - 1

        value = sqrt(value)

    return value

# return will immediately exit out of the function,

# and give this value to wherever the function was called

# this function can be used as below:

print(repeated_sqrt(5.2,3)) # will print sqrt(sqrt(sqrt(5.2)))

var number1 = 1

print(repeated_sqrt(thing[2],number1)) # will print sqrt(52.67)

number += repeated_sqrt(thing[2],2) + 1

# will increase number by sqrt(sqrt(52.67)) + 1

# function returns don't need to be used

func printvalue(value):

    print(value)

    return "hello"

printvalue(2) #will print 2

print(printvalue(3)) #will print 3,hello