@smurfmier1985 currently ue4. main reason is that the last project (descent underground) is/was in ue4, and i’m most familiar with.
however, i’ve used unity in the past. didn’t get much done other than effects, since c# isn’t something i like writing. i like the visual aspect of ue4 blueprinting.
That said, the more i now have experience with ue4 blueprinting, going back to c# propably isnt going to be that much of a hurdle. its a tool like anything else. i’ve gotten more scripting experience at dayjob with powershell past year, so atleast some good things comes from there aswell. 🙂
i think both engines work fine, if i were to get a job at a studio using unity, i’d say it would most take 3 months to get familiar with it again, and then its just chuggin along.
sorry for non answer. 😀
