It’s like when Epic Games paid Chivalry 2 devs for exclusivity. Other games use the funding from Sony and wouldn’t be the same without it. Others just don’t have the budget to be optimized for thousands of potential PC configurations, for continuous bug fixing, et cetera. Some games simply can’t come to PC or they’ll take way more time. But I have to say that every single time Sony announces its game coming to PC, I see more and more people saying they won’t support future exclusives, they won’t pay for, say, Death Stranding 2 until it comes to PC. I’m not one of the “exclusives need to stay on PS forever because exclusives make me feel cool and elite!” people. “Its like no one has a plan for tomorrow….they just do stuff.” Time to bring Kevin Butler out of retirement to fix PlayStation again. Yet again, slippery slope, COURSE CORRECT……. That’s how bad its gotten Sony, I can’t even be bothered to remember to watch a live show from you anymore, like the way I haven’t watched an Xbox showcase live since the hilarious Kinect showcase in 2010 lol. And Sony wouldn’t even bring us GT6 on PS4 back then but at least PS3 was long dead and buried as far as developers were concerned when making new games.Īnd I’ll admit it right now, I completely forgot about this showcase and just saw a list of the games. So why is is it absolutely fine here? PS3 was nearing 90 million units sold, not exactly that far off PS4’s 115 million sold. even thought that’s what we are getting now.īut seriously, how many huge games can anybody name that came to PS3 in 2015? Exactly. That would have been the dumbest thing ever had the games industry forced that sort of nonsense on us……. Was there a SINGLE PS5 only game shown? Imagine if in 2015, we got nothing but PS3 games lol. I tried that with the far jmp, but get another error (different error) when trying to activate script.WOW. No 14-byte jump needed, no indirect addressing modes. You could also just allocate newmem near ffxv_s.exe to allow for RIP-relative addressing. Thank you bud, the error is gone after I do what you say! yay, fixed Last edited by themandem on Sat 11:58 am edited 3 times in total Btw where it says line 15:offset too big, line 15 in this case is this Code: How can I fix this? Dark Byte xD helpppp. As soon as I removed the 3rd alloc parameter, i'm now getting this ">" error. That fixed the crash, but then I was getting this error ">" so then I removed the 3rd alloc parameter.
So i adjusted the code, now that's why there is lot of opcodes in originalcode. Posted: Sat 8:24 am Post subject: Help: How to fix > errorįirst the game was crashing because of this far jump issue (14 byte jump) (Final Fantasy XV is a 64 bit game).
0 kommentar(er)
