Page 4 of 5 FirstFirst 12345 LastLast
Results 61 to 80 of 100

Thread: AO New Engine Crashing

  1. #61
    Occasional (rare) crash during gameplay, laptop freezes and wont respond to anything but Ctrl-Alt-Del. Other than that, I am enjoying the experience, rediscovering old areas with new engine.

    Running on laptop I7-4700HQ / GTX770M / 32GB RAM.

    Added - Looking forward to higher def skies (love the nebulas, stars, moons/planets, etc)

  2. #62
    The crashes seems to be related to the hardware.

    AO crash on start on this computer:
    Intel Pentium 3.00 GHz
    8 GB RAM
    Windows 8.1 64bit

    It runs without errors on these two:
    GeForce GTX 770
    Intel i7 4.00 GHz
    8 GB RAM
    Windows 8.1 64bit

    Acer laptop Aspire V3-772G
    Intel i7 2.2 GHz -3.2 GHz
    GeForce GTX 760M
    Windows 8.1 64bit

  3. #63
    I've had a great time with the new engine on my 970 so far. The only issues I've found was the missing dragon models for inferno antideluvian (sp?), tara etc. and I seemed to have a fairly repeatable crash outside of inferno unred temple at sorrow when farming for DOJAs.

  4. #64
    Quote Originally Posted by Malosar View Post
    I've had a great time with the new engine on my 970 so far. The only issues I've found was the missing dragon models for inferno antideluvian (sp?), tara etc. and I seemed to have a fairly repeatable crash outside of inferno unred temple at sorrow when farming for DOJAs.
    Spinetooths and some other mobs (mantis queen) currently have too many bones for the new engine, some have been set as invisible.
    Caloss2 LVL 220 melee VANGUARD (semi retired).....Llewlyn 220/30/70 meepmeep.....Boooocal 220../30/70 Soldier.......Knack 220/30/70 Keeper.....Hiesenberg 215/xx/xx NT NERFED Neytiri1 220/30/70 Shade Knacker220/30/70Meat shield
    https://www.youtube.com/user/caloss2 for guides/walkthroughs/letsplays and all your other AO needs
    Quote Originally Posted by Mastablasta
    In my special design documents that I feed to the FC devs, who are my willing slaves.

  5. #65
    With 18.2, the new engine goes to a black screen before crashing so hard that it can't send a bug report. Task manager force quit is the only way to get AO shut down. Previously posted error reports on this thread. (Win7 Pro 64bit, i7 3770, Nvidia GeForce GTX 660 Ti, 32GB RAM, SSD for OS drive, game installed on D:, etc...)

  6. #66
    I've had no trouble with the new engine until the patch today, now I crash whenever I get to the character selection screen. I can't send an error report, the only way out of the lock up is to task manager force quit.
    [Windows 7x64, i7-4770k, Nvida GeForce GTX 770, 16GM RAM] If I can provide further info to help please let me know.

  7. #67
    No issues with 18.8.2 but if you have a i74770 check you don't have a hot core running (more than 8c higher than the other cores 1-5c is normal) as intel skimped on the Thermal transfer compound quality under the IHS.

    http://www.alcpu.com/CoreTemp/ To test the cores.

    Replacing the the TIM under the IHS (extremely risky) and not recommended.

    https://www.youtube.com/watch?v=7tPK6CdV_WI (will void any warrenty)
    Caloss2 LVL 220 melee VANGUARD (semi retired).....Llewlyn 220/30/70 meepmeep.....Boooocal 220../30/70 Soldier.......Knack 220/30/70 Keeper.....Hiesenberg 215/xx/xx NT NERFED Neytiri1 220/30/70 Shade Knacker220/30/70Meat shield
    https://www.youtube.com/user/caloss2 for guides/walkthroughs/letsplays and all your other AO needs
    Quote Originally Posted by Mastablasta
    In my special design documents that I feed to the FC devs, who are my willing slaves.

  8. #68
    Thanks for the tips and the links. A full uninstall and reinstall of the client got me up and running again, for now lol. I had no idea about the heat issues with the i74770, at least now I know to keep a special eye on the core temperatures. Thanks =]

  9. #69
    Quote Originally Posted by Lithodora View Post
    Thanks for the tips and the links. A full uninstall and reinstall of the client got me up and running again, for now lol. I had no idea about the heat issues with the i74770, at least now I know to keep a special eye on the core temperatures. Thanks =]
    There's a couple of sites you can check which generation chip you have, some have the issue, and later ones don't but you need CPUID to check which one your chip actually is, fingers crossed that you have a later gen
    http://www.cpuid.com/
    Caloss2 LVL 220 melee VANGUARD (semi retired).....Llewlyn 220/30/70 meepmeep.....Boooocal 220../30/70 Soldier.......Knack 220/30/70 Keeper.....Hiesenberg 215/xx/xx NT NERFED Neytiri1 220/30/70 Shade Knacker220/30/70Meat shield
    https://www.youtube.com/user/caloss2 for guides/walkthroughs/letsplays and all your other AO needs
    Quote Originally Posted by Mastablasta
    In my special design documents that I feed to the FC devs, who are my willing slaves.

  10. #70
    Quote Originally Posted by Sewlew View Post
    With 18.2, the new engine goes to a black screen before crashing so hard that it can't send a bug report. Task manager force quit is the only way to get AO shut down. Previously posted error reports on this thread. (Win7 Pro 64bit, i7 3770, Nvidia GeForce GTX 660 Ti, 32GB RAM, SSD for OS drive, game installed on D:, etc...)
    Looks like we're crash buddies I get the same thing. "Failed to send bug report". I guess that's one way to get us to stop sending bug reports.
    I'll probably try a fresh OS install on another drive this weekend. Maybe a different OS to see if that helps tracking down the source of the problem.
    Mpfha - your friendly neighborhood metaphysicist

  11. #71
    So far three golden tips seems to be.

    1, Run in borderless windowed mode.

    2, Sweetfx really helps, disable FXAA in game and your graphics card settings

    3, Mitchi and team are tweaking that engine every patch since it hit live, I and a lot of others can see the differences; I've seen more engine development in the last two patches than all of last year on beta.

    4, I will be making a how-to vid on installing and setting up the new engine, along with sweetfx and posting my own template for the sweetfx settings, once I feel confident it's solid enough.
    Caloss2 LVL 220 melee VANGUARD (semi retired).....Llewlyn 220/30/70 meepmeep.....Boooocal 220../30/70 Soldier.......Knack 220/30/70 Keeper.....Hiesenberg 215/xx/xx NT NERFED Neytiri1 220/30/70 Shade Knacker220/30/70Meat shield
    https://www.youtube.com/user/caloss2 for guides/walkthroughs/letsplays and all your other AO needs
    Quote Originally Posted by Mastablasta
    In my special design documents that I feed to the FC devs, who are my willing slaves.

  12. #72
    I to notice reliability improvements. Only one crash today..

    Funnily game was playable while windows reported crashing. So i ran to safe spot and accepted crash.

    Engine is also faster, more playable. Hardly a reason to log old engine. I only do that for buffing alts.
    Quote Originally Posted by Michizure View Post
    This'll be fixed for the next patch

  13. #73
    Mitchi and team have definitely been tweaking the engine; it's not in the patch notes but you do notice it revisiting certain areas before the last patch and since the last patch; there was a dark-spot (everything went very dark under the beast) and now it's a light spot (source of light)

    Also shadows now change more naturally as you character rotates and they don't tick or leave traces behind.
    http://i.imgur.com/Az8xO5F.jpg
    Last edited by Caloss2; Jul 11th, 2015 at 09:31:42.
    Caloss2 LVL 220 melee VANGUARD (semi retired).....Llewlyn 220/30/70 meepmeep.....Boooocal 220../30/70 Soldier.......Knack 220/30/70 Keeper.....Hiesenberg 215/xx/xx NT NERFED Neytiri1 220/30/70 Shade Knacker220/30/70Meat shield
    https://www.youtube.com/user/caloss2 for guides/walkthroughs/letsplays and all your other AO needs
    Quote Originally Posted by Mastablasta
    In my special design documents that I feed to the FC devs, who are my willing slaves.

  14. #74
    Just doing a bump post. My new engine client is still going to a black screen hang on launch and timing out on making a bug report. Bumpin' 'cause obviously all of us who are experiencing the same thing are not posting bug notifications to FC...
    Last edited by Sewlew; Jul 15th, 2015 at 16:08:20.

  15. #75
    Mine does the same. Anyone that solved this have any input?

  16. #76
    Over the last two weeks, I've tried a variety of additional workarounds to the "black screen hang on launch" problem with no success on my i7 3770/32GB/nVidia 660ti 3GB/Win7-64bit rig. I have gotten the new engine to work just barely on my 3rd gen i5 laptop with built-in Intel graphics but with only 10-15 fps in every zone I've visited. I see that this thread has over 5000 views, more than any other in the 18.8 update forum, so I'm betting there are quite a few other folks with the same or similar issues. What I'm baffled by is that I can see no pattern in what kind of rig the new engine will work on verses what kind it won't... since several folks with hardware and OS similar to mine are running the new engine.

    Has anyone had any success in overcoming this bug? Or are we just forced to wait for FC to find and fix the issue? After all these years of waiting, I'm anxious to play in the new engine.

  17. #77
    Very similar hardware here. i7 3820/nvidia 680gtx 32gig/ win7 64. Try downloading https://www.microsoft.com/en-gb/down...s.aspx?id=6812 and installing the SDK kit for directx, as some of the older dx9 files are missing in win7/64 for some obscure reason.

    I'd done this a while ago for certain fallout3 mods, but I did notice that the new engine shares some of the same ones.

    I as you can probably tell by my youtube channel have no problems running the new engine in it's current state.
    https://www.youtube.com/user/caloss2
    Caloss2 LVL 220 melee VANGUARD (semi retired).....Llewlyn 220/30/70 meepmeep.....Boooocal 220../30/70 Soldier.......Knack 220/30/70 Keeper.....Hiesenberg 215/xx/xx NT NERFED Neytiri1 220/30/70 Shade Knacker220/30/70Meat shield
    https://www.youtube.com/user/caloss2 for guides/walkthroughs/letsplays and all your other AO needs
    Quote Originally Posted by Mastablasta
    In my special design documents that I feed to the FC devs, who are my willing slaves.

  18. #78
    And... you have found the solution!

    It also turns out that you don't even need to have the DX SDK install complete successfully (an error code about open programs was produced during the final steps of the installation) in order for engine to begin working. I started up the AO client before I realized that there was an error code on the DX installation. Do you also get a few seconds of black screen... lag?... before the login screen pops? And is it normal for landscapes to draw in slowly when entering zones?

    In any case, thank you!

  19. #79
    Quote Originally Posted by Sewlew View Post
    And... you have found the solution!

    It also turns out that you don't even need to have the DX SDK install complete successfully (an error code about open programs was produced during the final steps of the installation) in order for engine to begin working. I started up the AO client before I realized that there was an error code on the DX installation. Do you also get a few seconds of black screen... lag?... before the login screen pops? And is it normal for landscapes to draw in slowly when entering zones?

    In any case, thank you!
    Ah good to know! (I suggested the D-SDK as it's a ~"cover all" solution and from a trusted source, download .dll sites are not so safe)
    If you install most newer game releases the installer always wants to run a dx-setup of some type; the beta engine doesn't do this (yet) and it is probably why the missing dx.dll's are not there after installation.

    The blank screen when the game initializes is "normal" and load times when zoning are still not "optimised" (I'm pretty sure the blank before login is the same as the zoning loading lag) but with AO running on an SSD they are, like everything else, greatly improved.
    The new engine certainly runs better now on the live server than it did during early beta, and Mitchi and team have taken it more than a few steps from where it was towards "finished" (disclaimer we are not there yet oh no) But it will get there, there was a recent suggestion to port over some of the textures from TSW to AO; if possible this could save a great deal of time and effort, although it might actually cause more work load, can't say for sure as I don't have the creation kit to play with.
    Last edited by Caloss2; Jul 27th, 2015 at 00:20:35.
    Caloss2 LVL 220 melee VANGUARD (semi retired).....Llewlyn 220/30/70 meepmeep.....Boooocal 220../30/70 Soldier.......Knack 220/30/70 Keeper.....Hiesenberg 215/xx/xx NT NERFED Neytiri1 220/30/70 Shade Knacker220/30/70Meat shield
    https://www.youtube.com/user/caloss2 for guides/walkthroughs/letsplays and all your other AO needs
    Quote Originally Posted by Mastablasta
    In my special design documents that I feed to the FC devs, who are my willing slaves.

  20. #80
    Quote Originally Posted by Caloss2 View Post
    Very similar hardware here. i7 3820/nvidia 680gtx 32gig/ win7 64. Try downloading https://www.microsoft.com/en-gb/down...s.aspx?id=6812 and installing the SDK kit for directx, as some of the older dx9 files are missing in win7/64 for some obscure reason.

    I'd done this a while ago for certain fallout3 mods, but I did notice that the new engine shares some of the same ones.

    I as you can probably tell by my youtube channel have no problems running the new engine in it's current state.
    https://www.youtube.com/user/caloss2
    OMG i'll try this.

    For me new engine crashes a lot at Tara and S42.. so much its totaly unplayable. Which is a shame, because it is waaay faster in mass people scenarios than old engine.

    BB to report after Dx SDK.
    Quote Originally Posted by Michizure View Post
    This'll be fixed for the next patch

Page 4 of 5 FirstFirst 12345 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •