Search the Community

Showing results for tags '1.0.3.0'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Astroneer Forum
    • Announcements
    • Patch Notes
    • General Discussion
    • Suggestions and Ideas
    • Support + Suggestions
  • System Era
    • Announcements
    • General Discussion

Calendars

  • Community Calendar
  • Astroneer Livestream Calendar

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 6 results

  1. Summary: 1.0.3.0 - Windows 10 - Medium Battery Model Glitch Description: I traveled to Novus to get some Methane and when the back hatch of the Large Shuttle opened, the model of 2 medium batteries were glitched. Even when I came back to my main base on Sylva both models were still glitched. The batteries were still working though. Platform: Windows 10 Store Version / Build Number: 1.0.3.0 Specifications: OS: Windows 10 Home x64 | v. 1809 | Build 17763.316 CPU: Intel i7-7700 CPU @ 3.60Ghz GPU: NVIDIA GeForce GTX1070 RAM: Kingston 16GB DDR4 2400Mhz Drive: WDC WD10EZEX-60WN4A0 -----------------------------------------------------------------------
  2. Summary: 1.0.4.0 - Steam - Catastrophic PC freeze Description: Random hard freeze of computer while playing the latest build of Astroneer (Steam). My entire PC just crashes to a black or other solid colored screen, audio buzzing, and I have no option but to physically push the reset or power button. This happened in the launch 1.0.3 build and again today in the latest 1.0.4 build. I was able to play all previous Early Release builds without this particular issue. 2/6/2019 - First Freeze was minutes after I landed after starting the tutorial in 1.0.3 build. I then updated my AMD drivers to 19.2.1 from 19.1.1 in hopes that might help and then managed to play for a couple of hours without problems. Assumed it was fixed. 2/9/2019 - Second Freeze was not long after starting my saved game in 1.0.4 build and I was just running around looking for resources / exploring. 2/9/2019 - Third freeze was while mining some Malachite on a mountain top on my starting planet. Played for nearly 2.5 hours happily since previous crash. Unfortunately, the log file located in the logs directory below is almost a year old. Is there a new location in 1.0 to get log files? ~\AppData\Local\Astro\Saved\Logs I’m loving the updates in 1.0 and really want to play, but I don’t want to keep losing so much progress with these crashes. I’ll have to wait until a fix or workaround is discovered before I can play any more. Specifications: OS: Windows 10 Pro | v. 1809 | Build 17763.253 CPU: Intel i7 6700k @ 4.0ghz GPU: Sapphire Radeon Vega 64 Nitro+ RAM: G.Skill Ripjaws 4 4x8GB DDR4 2400 Drive: Intel 710 series 100gb SSD DxDiag.txt
  3. Summary: Two bugs: one Place i found a ravine kind of place whilst playing around i got catapultet up in to the sky after bugging into the ground, when trying to repoduce it the second time i got thrown into a cave. Description: by jumping and ocasionaly mining soil at a thight spot (see 20190206105026_1.jpg) i glitched throug the ground to the side and down whilst being catapultet upwards. (becaus of your if in soil than fly up deglitching method wich safed me many times because of falling into the soil whilst mining and getting up again). when you get catapulted out you can reach great hight and fall to your deat even on higher level soil (see 20190206105155_1.jpg). also you can get into caves without oxigen (20190206110520_1.jpg) Platform: Steam / XBox One / Windows 10 Store Version / Build Number: 1.0.3.0 Specifications: OS: Microsoft Windows 10 Home Win 64 CPU: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz, 2601 MHz, 2 cores, 4 logic proccesors GPU: ? RAM: 16 GB total virtual storage 30.9 GB
  4. The audio for item/object sounds are in the opposite channel from where they should be. That is, an object on the left on screen, produces sound in the right hand channel, and vice versa. I have seen other people mention the same problem while streaming. I have video of the problem, if needed.
  5. Objects fall through the terrain. I have observed the following examples: Excavating a Research Item only to have it fall through the terrain into a cavern below. THIS IS AN OLD BUG FROM PRE-RELEASE! Vehicle (buggy) fell through the terrain but was hanging by the rear axle. Attempting to excavate it just made it fall further into the terrain. Placing an object (e.g. resource) onto the ground and it just falls through. I have video examples, if needed.
  6. Just wanted to report some achievement-related bugs me and a couple of friends found while playing version 1.0.3.0. [ACH] "Barrier Buster" is not awarded to players who have fulfilled the requirements [ACH] "Delve Greedily and Deep" is not awarded to players who have fulfilled the requirements [ACH] "Resources in the Rough" is not awarded to players who have fulfilled the requirements [ACH] "Journey to the Center of the Thing" is not awarded to players who have fulfilled the requirements Attached is a screenshot of a visit to Sylva's core during a multiplayer session. I can also provide video footage of the triptych event if need be. In addition, we experienced the following negative side effects in relation to the teleportation mechanic: [BUG] Player dies of suffocation while standing at a monolith site, although active tethers are present and seem to be working. [BUG] Player dies of fall damage after teleporting from one monolith site to another. Monolith type (surface vs. core) is irrelevant. [BUG] Player appears inside the hull of the Exo Dynamics space station after completing a triptych event, teleporting from the planet core to any other surface monolith, then teleporting back to the core. Bug occurs during the last teleport attempt (surface to core). Once the player ends up inside the EDSS, they can only rotate their camera but not move. A crash occurs shortly after, disconnecting the paralysed player from the current multiplayer session. From that point onward, the affected player's character model is always loaded inside the EDSS every time they rejoin the same session, rendering it unplayable for them ⇒ game over. So far, this has been observed only on Sylva and by a non-host player.