Jump to content

psionprime

Members
  • Posts

    84
  • Joined

  • Last visited

Posts posted by psionprime

  1. nVidia PC users, try using "-dx11" as a launch option. If that cures much of your crashes, petition nVidia to work with ASA devs to fix their dx12 driver. I put ASA on a new laptop with a nVidia 4090 and lasted about a minute before the shader crash. I moved my wife from 1660 super to a 3060Ti and it had crashes at launch. I used the "-dx11" launch option on both and, viola, no crashes since. My AMD 7900XTx system has,still, never crashed.

  2. I have a theory that those with nVidia GPUs crash the most. My wife has a i3-10100, 8G RAM, GTX1660 Super, 1920x1080, default game settings (sans motion blur and bloom) and crashes every half hour or so. I have a 7950x3D, 32G RAM, 7900XTX,  3440x1440 (sans motion blur and bloom) and have never crashed in ASA.

    There are a lot of various arguments about the cause(s) for ASA crashes. This poll is just for what GPU you have. I haven't heard much from the Intel or Chinese GPU community with ASA issues, so am curious what you have if "Other" is picked.

     

    Good Hunting !

    PS

    nVidia PC users, try using "-dx11" as a launch option. If that cures much of your crashes, petition nVidia to work with ASA devs to fix their dx12 driver. I put ASA on a new laptop with a nVidia 4090 and lasted about a minute before the shader crash. I moved my wife from 1660 super to a 3060Ti and it had crashes at launch. I used the "-dx11" launch option on both and, viola, no crashes since. My AMD 7900XTx system has,still, never crashed.

    Update 2023-12-21 - I managed to get my 6900 XTX, 7950x3D using just the extra cached cores all AMD system to crash. I tried the new driver "Hyper-RX" mode and it crashed inside a minute with, ironically, a nVidia dx12 set of error messages that my wife's nVidia machine often gets. I put it back to quality with only anti-lag and enhanced sync options enabled and now no more crashes. A lot of this thread suggests issues with DX12 nVidia common code.

    I start with native resolution 3440x1440; fullscreen; Epic preset; resolution scale 100; max framerate, motion blur, light bloom unchecked. I get about 60 fps +/- 30 ish

    I personally run with console variables:

    (turning off volumetric fog/clouds gets rid of the pixelated ick)
    r.VolumetricFog 0
    r.VolumetricCloud 0
    (DOF off keeps things sharp in the distance. I see obelisk detail on a clear day as I expect it to be)

    r.DepthofFieldQuality 0
    (this was suggested for a crash. I don't think it matters on my system but here for reference)
    ark.VertexCountScaling 1

  3. Okay so I used WinSCP in SFTP mode to download the save and profiles into the appropriate ASV folder, changed the ASV map to where the fresh download was and it parsed fine. I spent maybe an hour swapping around different maps and refreshing. I've had the original map in question load fine and not several times. My current thought is ASV FTP/SFTP is a little glitchy. FTP does not work for me in ASV, only SFTP. 

    v4.5.0 has been fine. v4.5.0.4 is the one. You know I can probably get the git and make it do a loop connecting a few thousand times to see any trends. Who knows, maybe the line was crap the other night.

  4. Here are Fjordur's Realms' bounding boxes I collected in-game. I imagine more precision can be had by someone with the editor. Perhaps Z height range can be added to the .json map descriptors and then common code to filter the item lists /shrug ?

    It looks like the layers, top to bottom, are Midgard, Jotunheim, Vannaheim, Asgard. What I don't know is the bottom boundary and if the XY Realm placement is to minimize space so the planes may intersect, eg. maybe the deepest Midgard ocean trench is below the top of Jotunheim. If so, then the filter will need to take in account all three coords of XYZ to make the bounding box... if that is indeed, how it works 😜

    Using admin commands to fly up in corner and "showdebug camera"
    (ASV indicates from the save file Z is 350 more than in-game "showdebug camera")

    Midgard top NE
    GPS Lat, Lon
    00.0, 99.9
    Player POS X,Y,Z
    377983.469, -365083.469, 70459.055

    Midgard top SW
    GPS Lat, Lon
    99.9, 0.00
    Player POS X,Y,Z
    -372453.406, 357573.531, 70459.156

    Vannaheim top NE
    GPS Lat, Lon
    0.00, 99.9
    Player POS X,Y,Z
    393597.000, -403011.344, -125791.547

    Vannaheim top SW (not precisely in corner though up all the way)
    GPS Lat, Lon
    33.1, 66.5
    Player POS X,Y,Z
    117962.820, -120665.750, -125791.734

    Asgard top NE
    GPS Lat, Lon
    17.6, 56.1
    Player POS X,Y,Z
    43999.340, -231116.531, -269462.125

    Asgard top SW
    GPS Lat, Lon
    68.7, 05.2
    Player POS X,Y,Z
    -319216.938, 133661.766, -269462.813

    Jotunheim top NE (not precisely in corner though up all the way)
    GPS Lat, Lon
    57.8, 59.9
    Player POS X,Y,Z
    71036.680, 56352.563, -103541.438

    Jotunheim top SW
    GPS Lat, Lon
    94.3, 21.6
    Player POS X,Y,Z
    -202710.422, 316841.438, -103541.422
     

  5. Thank you for your efforts, MirageUK !

    I am using 4.3.0.5. My servers are the Linux Steam distribution on an Ubuntu 20.04 server vanilla install (ensuring FTP/OpenSSH servers running). A few things:

    1. Fjordur map scaling is off but that is on their side, like Lost Island was initially

    2. I currently use the SFTP option with no issue. Almost all prior issues were due to permissions/firewall

    3. I suggest adding the Fjordur Realm maps to the map drop down as Fjordur_All, Fjorfur_Midgard, Fjordur_Asgard, etc. The drop down will cause the respective map to load programmatically as it does now. Hopefully the .json parameters will scale, etc so the coords are correct - as it does now. The main reason for this suggestion is to add a new feature so when a Fjordur map is selected, a Z coord range filters the lists so, eg. when Fjordur_Asgard is selected, that map displays using legacy code though with only the items in the Asgard layer displayed.

    I hope the devs make the in-game map an automatic process for whatever realm you are in.

  6. Looks like the ...\Scorched\ directory was never created and no fault message for failed FTP (SFTP). Copying the file with a different SFTP client then opening via the file interface worked fine.

    Also noted no levels for Wyvern eggs, just a "x1" on some ??? (nm uncheck "Stacks")

     

    Mode: Mode_Ftp

    Save:
    E:\games\ark bu\ArkViewer2021-3-19\Scorched\ScorchedEarth_P.ark

    Message:
    Sequence contains no elements

    Trace:
       at System.Linq.Enumerable.Min(IEnumerable`1 source)
       at ARKViewer.frmViewer.RefreshWildSummary() in F:\Projects\VS\ARKViewer-Master\ARKViewer\frmViewer.cs:line 1993
       at ARKViewer.frmViewer.LoadContent(ContentManager manager) in F:\Projects\VS\ARKViewer-Master\ARKViewer\frmViewer.cs:line 168
       at ARKViewer.Program.Main() in F:\Projects\VS\ARKViewer-Master\ARKViewer\Program.cs:line 249

×
×
  • Create New...