Widescreen Gaming Forum

[-noun] Web community dedicated to ensuring PC games run properly on your tablet, netbook, personal computer, HDTV and multi-monitor gaming rig.
It is currently 19 Mar 2024, 08:49

All times are UTC [ DST ]




Post new topic Reply to topic  [ 14 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: Ori and the Blind Forest
PostPosted: 06 Jan 2016, 22:19 
Offline
User avatar

Joined: 17 Jul 2010, 21:49
Posts: 79


Widescreen Grade: A
Ultra-Widescreen Grade: Incomplete
Multi-monitor Grade: Unsupported
4k Grade: Incomplete

Read Full Detailed Report - Ori and the Blind Forest

Ori and the Blind Forest is a single-player-only platform adventure video game designed by Moon Studios, an independent developer, and published by Microsoft Studios. Players assume control of Ori, a white guardian spirit, who has the ability to wall jump and pairs up with a spirit named Sein that can shoot Spirit Flames. Sein is the light and eyes of the forest's Spirit Tree. In order to progress forward in the game, players are tasked to move between platforms and solve puzzles. The game also features a system called "soul links", which allows players to save at will, and an upgrade system which gives players the ability to strengthen Ori's skills.

Set as a 2D open world platform game, the player controls Ori, a white guardian spirit. He has the ability to jump, climb and has many other abilities. Sein can also shoot Spirit Flames to assist in combating enemies or obstacles. Ori is required to interact with his environment as he jumps from platforms and solves puzzles. Ori is faced with enemies as he makes his way to restoring the forest. The player helps Ori collect health shards, energy shards, new abilities, and upgrades. Beside Ori is Sein who is the light and eyes of the Spirit Tree.

Source: Wikipedia



4:3


16:10


16:9


3x1



Last edited by Timobkg on 06 Jan 2016, 22:26, edited 2 times in total.
Edit


Top
 Profile  
 


PostPosted: 12 Jan 2016, 20:37 
Offline
Insiders
Insiders
User avatar

Joined: 11 Dec 2008, 23:51
Posts: 685
Location: Germany
I dont own this Game (yet) but since it is UNITY Engine its probably easy to get it to HOR+ .Hex edit the Assembly-CSharp.dll and if necessary Ori.exe - look for 39 8E E3 3F and change it to your Aspect Ratio......

_________________
CZARMAN aka 彼得爸爸


Top
 Profile  
 
PostPosted: 14 Mar 2016, 17:48 
Offline
User avatar

Joined: 14 Mar 2016, 17:42
Posts: 10
There is a new version of this game launching soon, any ultrawide support?


Top
 Profile  
 
PostPosted: 14 Mar 2016, 23:50 
Offline
Insiders
Insiders
User avatar

Joined: 12 Mar 2013, 23:18
Posts: 366
Deh wrote:
There is a new version of this game launching soon, any ultrawide support?

The Definitive Edition supports ultra-widescreen natively (Twitter post) but note that this is not going to be a free update.


Top
 Profile  
 
PostPosted: 02 May 2016, 02:33 
Offline

Joined: 26 May 2013, 23:08
Posts: 31
Garrett wrote:
Deh wrote:
There is a new version of this game launching soon, any ultrawide support?

The Definitive Edition supports ultra-widescreen natively (Twitter post) but note that this is not going to be a free update.


Any Surround fixes for this?

_________________
Intel i7-5960X @ 4456 1.20V; Noctua NH-D14
G.Skill 32GB @ 2800 CL15 1.25V; ASRock X99 OC Formula/3.1
2x NVIDIA TITAN X Pascal
2x Intel 520 240GB RAID-0; 2x Crucial BX100 500GB RAID-0; 2x Mushkin Reactor 1TB RAID-0
1x Seagate Backup Plus Fast 4TB
EVGA SuperNOVA 1600 P2; Rosewill Thor V2; 3x Asus PG278Q 2560x1440 144Hz G-SYNC
DacMagic Plus, 2x Dynaudio BM15A, 2x Dynaudio BM14S; Windows 10 Pro x64


Top
 Profile  
 
PostPosted: 16 Oct 2016, 19:51 
Offline
User avatar

Joined: 31 Jan 2007, 06:46
Posts: 64
Location: Orange, CA
The original supported 3x1 surround gaming using Flawless Widescreen. However the new Definitive Edition does not as the EXE changed to oriDE.exe now. :cry:

Does anyone know how to create plugins for Flawless Widescreen? I'm trying to hack the non-DE version, but it's not working.

_________________
ASUS Maximus XII Gene MB | i7 4790k CPU with Corsair Hydro Series H80i | Corsair Dominator Platinum 32GB | (2) EVGA nVidia GeForce GTX1080 Founders Edition in HB SLI | 1TB Samsung EVO SSD | Corsair Digital AX760i PSU | (3) Asus PG279Q (1) Asus PG278Q mounted on WSGF Ultimate Desk Stand v2 with Thru Desk Mount (3+1 Landscape Surround) | HTC Vive | Grace Design m9XX Headphone Amp/DAC | AudioEngine A5+ Bamboo | Ultimate Ears CIEM UE-5 Pro | ErgoDox Infinity Keyboard (Cherry Red) with Custom Keycaps | Logitech G502 Proteus Core Mouse | Win10 Enterprise x64

Current Setup


Top
 Profile  
 
PostPosted: 18 Oct 2016, 02:25 
Offline
Insiders
Insiders

Joined: 21 Oct 2014, 23:33
Posts: 291
2016 Definitive Edition (proof of 21:9 support, by default)
Tried very hard to fix this thing to spread with no pillarbox. Bitter failure. Dev, why you force Unity into a fucking box? Let it free, user knows best.
Attachment:
DE_cp1.jpg
DE_cp1.jpg [ 281.43 KiB | Viewed 7760 times ]

2015 edition, with FWS (or no-FWS & instead Assembly-CSharp.dll hex edit yourself, swapping 16:9 aspect (39 8E E3 3F formatted hex) with yours).
Attachment:
nonDE_cp1.jpg
nonDE_cp1.jpg [ 314.64 KiB | Viewed 7715 times ]

(manual PLP, borderless with Borderless Gaming. Though 2015 can also be spread manual FS w SoftTH DX9 enforced, but doesn't run butter smooth)


Top
 Profile  
 
PostPosted: 20 Oct 2016, 02:43 
Offline
User avatar

Joined: 31 Jan 2007, 06:46
Posts: 64
Location: Orange, CA
I wish I knew more about programming in C#. I found this other thread within WSGF also based upon the Unity engine:
http://www.wsgf.org/forums/viewtopic.php?f=64&t=27490

So I downloaded JetBrains decompiler just to take a look:
https://www.jetbrains.com/decompiler/

I loaded the file Assembly-CSharp.dll from Ori DE into the decompiler. In looking around I found the following for FOV under the CameraSizeConstraint.cs object within the Root:
Code:
using System;
using UnityEngine;

public class CameraSizeConstraint : MonoBehaviour
{
  public float FixedWidth;
  public Transform CameraOffset;
  public Camera Camera;

  public CameraSizeConstraint()
  {
    base.\u002Ector();
  }

  private void Start()
  {
    float num = this.FixedWidth / 2f / Mathf.Tan((float) ((double) this.Camera.get_fieldOfView() / 2.0 * (Math.PI / 180.0))) / this.Camera.get_aspect();
    Vector3 localPosition = this.CameraOffset.get_localPosition();
    localPosition.z = (__Null) -(double) num;
    this.CameraOffset.set_localPosition(localPosition);
  }
}


Now just to make sense of this all and compile it or hex edit it (I wish I could).

-b0n3z

_________________
ASUS Maximus XII Gene MB | i7 4790k CPU with Corsair Hydro Series H80i | Corsair Dominator Platinum 32GB | (2) EVGA nVidia GeForce GTX1080 Founders Edition in HB SLI | 1TB Samsung EVO SSD | Corsair Digital AX760i PSU | (3) Asus PG279Q (1) Asus PG278Q mounted on WSGF Ultimate Desk Stand v2 with Thru Desk Mount (3+1 Landscape Surround) | HTC Vive | Grace Design m9XX Headphone Amp/DAC | AudioEngine A5+ Bamboo | Ultimate Ears CIEM UE-5 Pro | ErgoDox Infinity Keyboard (Cherry Red) with Custom Keycaps | Logitech G502 Proteus Core Mouse | Win10 Enterprise x64

Current Setup


Top
 Profile  
 
PostPosted: 20 Oct 2016, 08:03 
Offline
Insiders
Insiders

Joined: 21 Oct 2014, 23:33
Posts: 291
It is a good find b0n3z, thanks. It is aspect we want. Have some ideas at least now, need to build somehow later.
-----
The most disturbing code, most likely the problem:
MaintainAspectRatio.cs
1. First of all, dev has used "1.77777..." a fair amount in this dll. That is why so many 16:9 aspect hits in hex. I think. Switching them does not improve the logic, so that hex don't fix game. I think, something like that.
2. The main issue here (I think) is dev's new & funky 21:9 code (2.389f), stuck snuggly in here. I think that's got to go, somehow. In a manor of speaking (the flow could be shoved with a hardcode, or the 21:9 value changed to a logical value that would alter the flow)
3. Guess1 (strong guess): Change the dll's hex for 21:9, to something else, to affect the Clamp statement's effect on flow.
Code:
4. Tuning... will describe some vars in this area. This is rough, sharing thought
A.   'num1 = your proper aspect, temp-stored here.
   'eg0 num1=1.333333333 (4:3) (!)
   'eg1 num1=1.777777778 (16:9)
   'eg2 num1=2.388888889 (3440x1440, ~21:9)
   'eg3 num1=3.259259259 (3520x1080, ~16:5) (!)
   'eg4 num1=5.333333333 (LLL 16:9x3) (!)
B.   'num2 looks faulty, is used as a flag. It is compared with num1 to decide a horrible fait. I think.
   'Clamp is used to direct aspect-range's future flow (branch of two, one is bad & should be shunned).
   'num2 shuns your wide aspect (via clamp), storing instead 21:9 (for flagging, not actual visuals yet).
   'eg0 num1 of 1.333333333 = num2 of 1.777777778 (!)
   'eg1 num1 of 1.777777778 = num2 of 1.777777778
   'eg2 num1 of 2.388888889 = num2 of 2.388888889
   'eg3 num1 of 3.259259259 = num2 of 2.388888889 (!!!)
   'eg4 num1 of 5.333333333 = num2 of 2.388888889 (!!!)
C.   height (used first as a flag):
   'i. Examples
   'eg0 height = 0.75 (!)
   'eg1 height = 1.0
   'eg2 height = 1.0
   'eg3 height = 1.364341085 (!!!)
   'eg4 height = 2.232558140 (!!!)
   'ii. Logic branch (BAD I think):
   '- if height > 1.0 (eg PLP, LLL; we are forced into this BAD branch atm), then
   '- 1. store (eg):
   '- - eg3: new width-variable = 0.732954545 (ie 1/height-variable, ie 1/1.364341085)
   '- - eg4: new width-variable = 0.447916667 (ie 1/height-variable, ie 1/2.232558140)
   '- 2. width-variable then thrown to Rect (____), along with height (of 1, for all egs, including eg3).
   '- - means: these values will be used to calc later (are not your actual px/aspect-values, here). But we can fix logic here, for later.
   '= 3. OutputGuess1: appears nasty code, whining for pillarbox.
   '= - eg3: 3520 x 0.732954545 (width-variable) = 2580 pxWidth, which will auto-use 1080, which is about ~21:9, a hint wider (2560x1080 would be dead-proper 21:9).
   '= = = This is exactly what I see in-game (game-image bare-hint-wider than 21:9). Our first test of theory passes.
   '= - eg4: 5760 x 0.447916667 (width-variable) = 2580 pxWidth, which will auto-use 1080, which is about ~21:9, a hint wider (2560x1080 would be dead-proper 21:9).
   '= = = Same exact 21:9 output. This villian.
------WE ARE HERE-------
   'iii. Logic flow (GOOD BRANCH. we PLP/LLL want to shove over to this branch. Sort of):
   '- if height < 1.0 (ie, eg0 of 4:3; PLP can't get in here atm), then
   '1. width-variable is never used (ie it will not mess with our wider-aspects). Rect is instead sent 1 (for width; which will likely = [x yours = yours]. your proper width's aspect, in theory)
   '2. It uses height variable & defaults to your width (1x yours), which appears exactly what we want.
   '3. This branch is evil toward 4:3. I think. It will letterbox narrow aspect. I think.
   '4. If we force our way here, the height needs a fudge. I think. This is a spanner in the works. I think, hope can think around it. I don't know it could block, very easily.
   '= - eg0: 1200 (pxHt) x 0.75 (height-variable) = 900 (!)
   '= - eg1: 1080 (pxHt) x 1.0 (height-variable) = 1080
   '= - eg2: 1440 (pxHt) x 1.0 (height-variable) = 1440
   '= - eg3: 1080 (pxHt) x 1.364341085 (height-variable) = 1473.488372000  (!!! what would that do?)
   '= - eg4: 1080 (pxHt) x 2.232558140 (height-variable) = 2411.162791000 (!!! what would that do?)

'MOST IMPORTANTLY, FOR THE GAMBLER (test at your own risk. I have not yet, still feeling around)
'- Logic (you can ignore): 2.389f == 4018E560 >>format>> 60E51840.
'- TO TEST ~GOOD BRANCH:
'Open Assembly-CSharp.dll in HxD. Find 60E51840, replace with __something else__ (evil grin) that is a lot bigger or smaller. It don't matter much, because I can't think which way. One way is right, the other way will make no difference. So 50-50 chance, you try both ways & see.
Post now complete. No more post edits.
----------
At this point, it remains feasible this can be corrected with hex or CE. But not certain yet. There is also I chance I can decompile, fix, recompile (using other tools). But that plain sucks if hex will suffice


Last edited by imusrt on 21 Oct 2016, 08:49, edited 4 times in total.

Top
 Profile  
 
PostPosted: 21 Oct 2016, 04:22 
Offline
User avatar

Joined: 31 Jan 2007, 06:46
Posts: 64
Location: Orange, CA
Sorry imusrt. I lost you a ways back. It feels like I'm watching this video:
https://www.youtube.com/watch?v=qVY2x6f3FTU

Even though I understand HTML code it's extremely hard to concentrate and understand any word she's saying (blah, blah, blah, SQUIRREL!) Maybe I need more coffee. I'm just glad your brain is on it. Thank you!

-b0n3z

_________________
ASUS Maximus XII Gene MB | i7 4790k CPU with Corsair Hydro Series H80i | Corsair Dominator Platinum 32GB | (2) EVGA nVidia GeForce GTX1080 Founders Edition in HB SLI | 1TB Samsung EVO SSD | Corsair Digital AX760i PSU | (3) Asus PG279Q (1) Asus PG278Q mounted on WSGF Ultimate Desk Stand v2 with Thru Desk Mount (3+1 Landscape Surround) | HTC Vive | Grace Design m9XX Headphone Amp/DAC | AudioEngine A5+ Bamboo | Ultimate Ears CIEM UE-5 Pro | ErgoDox Infinity Keyboard (Cherry Red) with Custom Keycaps | Logitech G502 Proteus Core Mouse | Win10 Enterprise x64

Current Setup


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 14 posts ]  Go to page 1, 2  Next

All times are UTC [ DST ]


Who is online

Users browsing this forum: Ahrefs [Bot] and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron




Powered by phpBB® Forum Software © phpBB Group