• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

Deadly Premonition PC port locked to 720p, no gfx options (nm, Durante fixed it)

parabolee

Member
Jul 23, 2007
399
0
0
NJ
Had this pre-ordered since available. Game is amazing but I hated the over the shoulder of 360 and the framerate on the PS3 DC literally gave me headaches!

Even at 720p 60fps it would be a big step up. But sucks it's not 1080p.

Durante you are amazing! Definitely going to donate if you get this working at 1080p!
 

TheThunder

Member
Oct 23, 2009
11,844
0
685
32
Nice thread title, nice tag :lol

If DS2 doesn't have some sort of Durante NPC, item or whatever its gonna be a shame.
 

Jarate

Banned
Jul 18, 2009
17,460
0
0
29
>tfw the game runs like absolute dogshit on my computer

All I wanted to do was play teh vidya. Im getting around 10 fps, and I got an i5 and a gtx670. wtf
 

Josh7289

Member
Dec 9, 2006
7,387
1
0
  1. Check which dll's the game uses, find one suitable for injection.
  2. Replace that dll, inject my code, log all the relevant DirectX calls
  3. Run the game a bit
  4. Browse the log file (with search, it's several 100 MB), try to figure out the relevant calls
  5. Replace those you think affect rendering resolution

At this point you get the totally broken result shown first in this thread. Now you start a loop.
  1. By a combination of log reading, intuition and wild guessing, try to figure out what's wrong.
  2. Adjust the things that need adjusting to fix what presumably went wrong.
  3. Run the game and check if it helped.
  4. If it's still broken, start again at 1.

I'll probably have to continue the loop above for a few hours now.
Oh my god that's fucking sweet. So those DLLs that you're replacing, are they standard libraries and stuff?
 

Interfectum

Member
Nov 14, 2008
20,828
14
975
  1. Check which dll's the game uses, find one suitable for injection.
  2. Replace that dll, inject my code, log all the relevant DirectX calls
  3. Run the game a bit
  4. Browse the log file (with search, it's several 100 MB), try to figure out the relevant calls
  5. Replace those you think affect rendering resolution

At this point you get the totally broken result shown first in this thread. Now you start a loop.
  1. By a combination of log reading, intuition and wild guessing, try to figure out what's wrong.
  2. Adjust the things that need adjusting to fix what presumably went wrong.
  3. Run the game and check if it helped.
  4. If it's still broken, start again at 1.

I'll probably have to continue the loop above for a few hours now.
Any particular reason why the developer CODING this can't do this? Maybe you could offer your services to future devs.
 

parabolee

Member
Jul 23, 2007
399
0
0
NJ
>tfw the game runs like absolute dogshit on my computer

All I wanted to do was play teh vidya. Im getting around 10 fps, and I got an i5 and a gtx670. wtf
Oh dear. This worries me, I have a i5 and GTX 670 too!

I just want me Deadly Premonition to run at 1080p 60fps! Is that too much to ask? The game looks like shit (in a charming way) anyway!

I heard the frame rate is good from others? Maybe you can fiddle with the settings in the Nvidia Control Panel and get it running better?

Mine is still downloading, will test soon.
 
May 22, 2011
7,255
0
0
Rising Star Games is listed as both the developer and publisher of the PC version
I didn't notice that, but Rising Star have mentioned getting builds "from the devs", so it could be a case of putting their name instead of the devs used for outsourcing (or the original team?)
 

hexen

Neo Member
Sep 26, 2013
45
0
0
it's threads like this where i hate myself for not going through with my studies in computer science.

praise durante.
 

Cheddahz

Banned
Aug 10, 2011
14,096
1
745
It did that for another Greenlight game and they weren't the developers either.
It's a cool new trend for publishers not to credit the developer on Steam.
I didn't notice that, but Rising Star have mentioned getting builds "from the devs", so it could be a case of putting their name instead of the devs used for outsourcing (or the original team?)
I did not know this. Well, I still haven't heard anything back from Rising Star Games (it seems like they are more interested in their new Beyblade game)
 
Mar 8, 2013
2,260
0
405
I just have to nod in approval, I also have to restate how embarrasing it is for these japanese devs that durante comes in and knocks out a rudimentary fix in an hour.
Maybe you should offer up your services as some sort of external consultant Durante.
 

nynt9

Member
Jun 7, 2013
10,858
2
620
Durante is best. This is the third time I'm buying this game, and it's going to be the best time, thanks to him.

Can't wait for a released version of the fix!
 

Stumpokapow

listen to the mad man
May 21, 2006
17,232
3
0
Guys, Durante doesn't need your money, he needs your connections to journal reviewers so his future publishing career goes smoothly and he gets on the tenure track as quickly as possible. :p
 
Feb 10, 2009
4,521
0
665
yeah don't really feel comfortable in putting money down for swery's shit on day one anymore, horrible ps3 port, a horrible pc port and they've shown no inclination of fixing things.
This is the same team that released the PS3 'Director's Cut' with a vastly inferior frame rate and non-customisable driving controls as accelerate / brake on R1 & L1, with handbrake on R2.
Welp. I really should have checked on GAF before getting the game on PSN.
 

LeleSocho

Banned
Jun 13, 2011
16,021
13
760
  1. Check which dll's the game uses, find one suitable for injection.
  2. Replace that dll, inject my code, log all the relevant DirectX calls
  3. Run the game a bit
  4. Browse the log file (with search, it's several 100 MB), try to figure out the relevant calls
  5. Replace those you think affect rendering resolution

At this point you get the totally broken result shown first in this thread. Now you start a loop.
  1. By a combination of log reading, intuition and wild guessing, try to figure out what's wrong.
  2. Adjust the things that need adjusting to fix what presumably went wrong.
  3. Run the game and check if it helped.
  4. If it's still broken, start again at 1.

I'll probably have to continue the loop above for a few hours now.
I have no words, based Durante.
 

Miguel81

Member
Aug 20, 2013
4,950
0
0
I just have to nod in approval, I also have to restate how embarrasing it is for these japanese devs that durante comes in and knocks out a rudimentary fix in an hour.
Maybe you should offer up your services as some sort of external consultant Durante.
It's like they're so clueless it's not even funny.

NeoGAF: "There's a fuck up"

*Durante runs to clean up the mess*

NeoGAF: Pats him on the back, curses Japanese devs.
 

Levyne

Banned
Jun 6, 2011
29,024
0
0
twitter.com
I have zero intention to ever play this game but I followed the thread just for the Durante magic. Equal parts amazing on his part and sad on the devs part. So lazy.
Yeah, not really even interested in the game but even just being a spectator of seeing this go down is too good to pass up.
 

Marjar

Banned
Oct 17, 2012
2,468
0
0
It's a shame this happened to this game. Seriously one of the best games of the generation. Would hate to see technical aspects like this turn off people.
 

Dusk Golem

A 21st Century Rockefeller
Sep 15, 2011
19,008
2
800
Portland, Oregon
www.twitch.tv
It's a shame this happened to this game. Seriously one of the best games of the generation. Would hate to see technical aspects like this turn off people.
Considering the game has always had technical problems, in every iteration.

I'm not defending locking screen ratio or other flaws, but also I can say that DP likely will not be a game for those who can't overlook flaws.

And a many thanks, based Durante.
 

eot

Member
Apr 13, 2012
12,075
3,444
800
  1. Check which dll's the game uses, find one suitable for injection.
    [*]Replace that dll, inject my code, log all the relevant DirectX calls
  2. Run the game a bit
  3. Browse the log file (with search, it's several 100 MB), try to figure out the relevant calls
  4. Replace those you think affect rendering resolution
A .dll is compiled code, where do you get the source so you can edit it?
 

DUFFMCWALIN

Member
Mar 6, 2010
11,115
0
600
Chico, CA
  1. Check which dll's the game uses, find one suitable for injection.
  2. Replace that dll, inject my code, log all the relevant DirectX calls
  3. Run the game a bit
  4. Browse the log file (with search, it's several 100 MB), try to figure out the relevant calls
  5. Replace those you think affect rendering resolution

At this point you get the totally broken result shown first in this thread. Now you start a loop.
  1. By a combination of log reading, intuition and wild guessing, try to figure out what's wrong.
  2. Adjust the things that need adjusting to fix what presumably went wrong.
  3. Run the game and check if it helped.
  4. If it's still broken, start again at 1.

I'll probably have to continue the loop above for a few hours now.
I would love to read your logs if you actually keep any.