{"id":459,"date":"2022-04-12T14:55:32","date_gmt":"2022-04-12T14:55:32","guid":{"rendered":"http:\/\/engadget.vip\/?p=459"},"modified":"2022-04-12T14:55:32","modified_gmt":"2022-04-12T14:55:32","slug":"rebel-galaxy-outlaw-pc-technical-review","status":"publish","type":"post","link":"https:\/\/engadget.vip\/?p=459","title":{"rendered":"Rebel Galaxy Outlaw PC technical review"},"content":{"rendered":"
<\/div>

Rebel Galaxy Outlaw<\/em> has some noticeable differences between the highest and lowest graphics settings. For this technical review, we discuss those graphics settings as well as the surprisingly complex key controls, and we consider how the game runs while using a gamepad versus keyboard. Those who enjoy heavily customizing their spaceships might also be interested in the game\u2019s built-in paint editor.<\/p>\n

Note: <\/b>This is our technical review for Rebel Galaxy Outlaw. <\/i>We also have our official scored review.<\/p>\n

\"Smudges<\/p>\n

System requirements<\/h2>\n

Minimum:\u00a0<\/b><\/p>\n

    \n
  • OS: Windows 7, Windows Vista, Windows 8, Windows 10<\/li>\n
  • Processor: Intel Core 2 Duo, AMD Athlon X2<\/li>\n
  • Memory: 2 GB RAM<\/li>\n
  • Graphics: Shader Model 4.0, 1 GB VRam<\/li>\n
  • DirectX: 11 or higher<\/li>\n
  • Storage: 20 GB<\/li>\n
  • Sound: DirectX 9.0c-compatible, 16-bit<\/li>\n<\/ul>\n

    Recommended:\u00a0<\/b><\/p>\n

      \n
    • OS: Windows 7, Windows Vista, Windows 8, Windows 10<\/li>\n
    • Processor: Intel Core 2 Duo, AMD Athlon X2<\/li>\n
    • Memory: 2 GB RAM<\/li>\n
    • Graphics: Shader Model 4.0, 1 GB VRam<\/li>\n
    • DirectX: 11 or higher<\/li>\n
    • Storage: 20 GB<\/li>\n
    • Sound: DirectX 9.0c-compatible, 16-bit<\/li>\n<\/ul>\n

      Writer\u2019s specs:<\/b><\/p>\n

        \n
      • OS: Windows 10 64-bit<\/li>\n
      • Processor: AMD FX(tm)-8320<\/li>\n
      • Memory: 8 GB RAM<\/li>\n
      • Graphics: Radeon RX 560<\/li>\n
      • DirectX: Version 12<\/li>\n<\/ul>\n

        \"Rebel<\/p>\n

        Graphical settings<\/h2>\n

        The highest supported resolution is 1920\u00d71080. This might be a disappointment for those who run larger monitors, but for me I was pleased with the game\u2019s graphical details. I\u2019m running this game on a 21-inch monitor, and I found that the above resolution fits well with the game\u2019s user interface.<\/p>\n

        As for graphical textures, on load-up you have plenty of options to choose from. Shadow quality has a setting range from low to ultra, and there are options for blur quality, FX quality, and mesh. Alongside these, you can choose to toggle on or off bloom effects, damage decals, film grain, lens glare, distortion, and dynamic lights. There is also an HBAO option, as well as crepuscular rays and depth of field.<\/p>\n

        Now would be a good time to mention the game\u2019s photo mode. At any time, you can pull up the command menu and pause the game. Then you can move freely and take pictures in a 3D environment around your own spacecraft as well as nearby spacecraft and space stations. This was where I noticed the depth of field most prominently. When viewing my spacecraft in the photo mode, it was obvious that the space station behind me was out of focus, whereas my spacecraft (the focal point) was in focus. Although subtle, this was detail was a nice addition.<\/p>\n

        Graphical comparisons<\/h2>\n

        Since this game has some noticeably low system requirements, don\u2019t expect much stutter in gameplay. I encountered no noticeable slowdown. This is especially impressive given how often the game allows you to skip cutscenes. Every time you takeoff from or land on a space station, the game triggers a cutscene. Similarly, every time you engage in auto-pilot (which is very often) the game triggers a cutscene. Of course, at first I took to enjoying the cutscenes. The more I progressed, the more I would quickly skip through them. Even during fast bouts of skipping, I noticed no slowing down as the game loaded post-cutscene.<\/p>\n

        Taking the aforementioned graphical settings, let\u2019s take a look at some graphical comparisons. Here are a few screenshots showcasing the game\u2019s highest settings versus lowest settings.<\/p>\n

        Docked at the Nacogdoches space terminal, maximum\/minimum settings:<\/strong><\/p>\n

        \"Rebel<\/p>\n

        \"Rebel<\/p>\n

        Exiting Nacogdoches, maximum\/minimum settings:<\/strong><\/p>\n

        \"technical<\/p>\n

        Cockpit view, maximum\/minimum settings:<\/strong><\/p>\n

        \"cockpit<\/p>\n

        \"technical<\/p>\n

        In the first image that shows the ship docked at the space terminal, the most noticeable difference is in the lighting. If you look at the red lights above the terminal exit leading into space, the highest settings show a nice glare. The lowest settings have almost no glare at all, and the lights look rather dull. Similarly, in the outer space shots, the asteroids appear to lack texture.<\/p>\n

        Most prominent, however, is the cockpit view. The lowest graphical setting has an unusual brightness. This must be due to the shading effects. When used on the highest settings, the cockpit takes on a darker, more well-rounded look.<\/p>\n

        \"Gamepad<\/p>\n

        Controls<\/h2>\n

        At first, the control scheme for this game is quite overwhelming. The \u201ckey mapping\u201d section of the menu contains a number of keys that are unmapped by default. Some of these include extra \u201cinflight boost to engine, inflight boost to power,\u201d and so forth. However, those same controls are accessible from the command menu, so mapping them to a key is not necessary. The game also contains an \u201cinertial damper cut\u201d key, which is also not necessary because lowering the engine power achieves the same effect.<\/p>\n

        At first, I found all of this to be confusing, and I think other players will too, especially since the developer recommends playing with a gamepad. With the long list of keys, there\u2019s no way that every key could be mapped to a controller. So, I tested the game with a DualShock 4, and the good news is that it\u2019s playable right off the bat. I had to tweak a few things though. Being a fan of the Ace Combat<\/em> games, I switched pitch\/roll to the left stick and steer to the right stick (by default they are reversed for this game). I also made the flight controls inverted, and I put my main attack as the L2 button and boosters as R2. Admittedly, all of this was just a test, and the controller plays quite smoothly as such. However, I spent the entirety of my playthrough using keyboard and mouse.<\/p>\n

        My recommended control scheme is simply remapping roll left =\u00a0<\/em> A and\u00a0roll right\u00a0<\/em>= D. Everything else I left the same, and I steered my ship using the mouse.<\/p>\n

        Final thoughts<\/h2>\n

        In hindsight, I think most players will enter this game and meet the same roadblock I did. At first, it seems as if you have to test a large amount of control variations to get the game running. This isn\u2019t totally true, but some players will relish in the variety of control options. The control scheme I mentioned above worked perfectly fine for my playthrough.<\/p>\n

        Rebel Galaxy Outlaw\u00a0<\/em>presents wonderfully low PC requirements, and as such, the game runs well on all settings. The number of options to toggle on\/off are nice, but most players won\u2019t need them. For anyone running a PC with low-end requirements, Rebel Galaxy Outlaw\u00a0<\/em>is an excellent choice for a space-flight RPG.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Rebel Galaxy Outlaw has some noticeable differences between the highest and lowest graphics settings. For this technical review, we discuss those graphics settings as well as the surprisingly complex key controls, and we consider how the game runs while using a gamepad versus keyboard. Those who enjoy heavily customizing their spaceships might also be interested […]<\/p>\n","protected":false},"author":1,"featured_media":460,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[638,639],"_links":{"self":[{"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/posts\/459"}],"collection":[{"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=459"}],"version-history":[{"count":0,"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/posts\/459\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/media\/460"}],"wp:attachment":[{"href":"https:\/\/engadget.vip\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=459"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=459"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=459"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}