-
Posts
1263 -
Joined
-
Last visited
-
Days Won
5
Content Type
Profiles
Forums
Blogs
Everything posted by Phenomenum
-
Though ingame camera have ABSOLUTELY ZERO head bob (you can test it walking straight to the wall) there's a strange effect, causing Motion sickness - nausea and headache. Watch the far landscape and clouds. Who in Obsidian team is high on drugs? Please, remove this stupid effect and those stupid guy, who come up with such stupid idea! And add OPTIONAL classic headbob camera animation like in thosands other 1st person games.
-
So... Use the one of most advanced game engines - UE 4 - just to put baked lowres shadows in 2019... It's a some sort of perversion in my book. Our spaceship: I think some of interiors needs a total uplift. P.S. Nah... Don't tell me about "this game is not about graphic". It's a 1st-person game in a first place, where players staring close on every damn thing. More crappy graphics –> less immersion.
- 1 reply
-
- 1
-
-
Small Text?
Phenomenum replied to thedumbfish123's topic in The Outer Worlds: Technical Support (Spoiler Warning!)
Also, i want to say that cyrillic type (russian) is awful – letters are placed too close to each other and sometimes it's hard to distinguish some words. -
Small Text?
Phenomenum replied to thedumbfish123's topic in The Outer Worlds: Technical Support (Spoiler Warning!)
Yeah. Geme definetely need textsize slider of something. -
I have this issue on fresh 19.10.2 version driver. So... i'm curious is this AMD fault or Obsidian?.. Anyway there a lot of other issues for me – unable to save the game, for example.
- 8 replies
-
- lod
- terrain bug
-
(and 5 more)
Tagged with:
-
Confirmed. RX 570, newest "optimized for TOW" drivers. VIDEO
- 8 replies
-
- lod
- terrain bug
-
(and 5 more)
Tagged with:
-
RT itself doesn't grants HP on kill. Can you be more specific about items/abilities you're using with +20HP on kill? About Brilliant: I did some research and figured out that not all suggestions is technically available. I suggest (and this was a long time ago) to divide Brilliant tick duration for casters and non-casters: leave 1 each resource per 5-6 sec. for non-caster classes and adjust tick duration to, say 10-12 sec. for casters. This is an easy and gentle solution. Thoughts?