der link des tages

  • Joa, geht so für'n Garten!

    TUSL2-C, PIII-S 1,4GHz, 512MB, Voodoo3 3000 AGP, SB Live!
    TUSL2-C, PIII-S 1,4GHz, 512MB, Voodoo3 3000 AGP, SB Live!
    CUSL2-C, PIII 933MHz, 512MB, Millennium II AGP 4MB, 2x Monster II 12MB, SB Live!
    CUSL2-C, PIII 933MHz, 512MB, Millennium II AGP 4MB, 2x 3D Blaster Voodoo² 12MB, SB Live!
    P3B-F, PIII 800MHz, 512MB, G400 Max 32MB AGP, 2x Monster II 12MB, SB AWE64 Gold
    P2B-F, PIII 600MHz, 512MB, G200 8+8MB AGP, 2x Monster II 8MB, SB 32 PnP

  • Let them first get their crap fixed with UE4 before bringing out a new game engine....

    There are so many bugs that could of gone through simple fixing if they made time to fix them, numerous reports of bugs most developers were forced to make work arounds oor apply fixes themself.

    My friend Verran who had over 27 years of programing experience worked on Ascentroid all by himself for a good 6 a 7 years, he has encountered tons of annoying and sloppy bugs the Unreal Epic games devs simple ignored, even after the hundreds of reports of them.

    Verran like many other UE 4 devs, had to hard code fixes made by Epic, evey time we find something we'd be like Epic is Fired for not apllying a simple fix to such an annoyance instance.

    I am a main tester for Ascentroid and we both have found tons of things Epic could of fixed , yet Verran hard coded them and with many things this eats a lot of timing fixing Epic's crappy mistakes.

    Here our bugs & issues list
    https://github.com/Ascentroid/Ascentroid/issues

    Just the list of things we have to attend to it's crazy.

    As for UE5 it looks amazing but it's packed with bugs it won't be usable til like 5 a 6 years from now, since UE4 needs way more fixing and the chance is high the bugs found in UE4 will most likely also be found in UE5.