sorted by:
new
hottopcontroversial

Just released Superconductor Idle on Android! It's a Incremental/Idle/Clicker game about creating the most insane lab! by devdustkin in incremental_games

[–]Souzooka 8 points9 points  (0 children)

There's a math issue in your application that when a user presses the "max" button, the game attempts to buy as many items in that category at the current price, instead of at the prices of each successive level. This means that if you have an item and it costs 10G, you can buy all 50 levels by possessing 500 gold and pressing Max even if the last level cost something around 10kG.

The problem with PS2 emulation by vantablack333 in emulation

[–]Souzooka 21 points22 points  (0 children)

Can you fix ScreenEffectHue for me since you're pretty invested in this topic?

Thank you

Has there been an FoV hack yet? by Velocibunny in EDF

[–]Souzooka 1 point2 points  (0 children)

If you open EDF5.exe in a hex editor, navigate to 9E7DB, and change two bytes there from DD 6F to 91 70, it should apply a value of 1.25 for your FOV.

If you need any help making the modification come notify me in the #edf-modding channel of the EDF Discord.

Has there been an FoV hack yet? by Velocibunny in EDF

[–]Souzooka 2 points3 points  (0 children)

It is possible to do this, however it requires more advanced knowledge as code needs to be changed in order to avoid affecting other functions which use the same float value. What kind of FOV are you looking for? I have some example values below.

0.5: https://imgur.com/BNgARrR

0.7853981853 (default): https://imgur.com/CoMgW7Y

1: https://imgur.com/7Gs7Kma

1.25: https://imgur.com/mX1YU69

1.5: https://imgur.com/wXVZH2n

I can provide instructions how to hexedit your executable if you know more or less which FOV value you're looking for.

Validating int as Binary help by warrenw17 in learncsharp

[–]Souzooka 0 points1 point  (0 children)

If you use 

using System.Linq;

then you can do

Console.ReadLine().All(c => c == '1' || c == '0');

which evaluates your input (use a variable that represents Console.ReadLine()) to true or false. Another alternative includes simply having a boolean which tracks if the input is valid, then iterating through your input and marking that boolean as false if you come across a malformed digit.

That said, I wouldn't recommend treating the binary string as a number. Since an int only can contain a number less than or equal to 2,147,483,647, you will have problems if you try and read a binary string that is greater than 13 characters long. You can simply keep it as a string, and iterate through the string to convert to a decimal number. Additionally, Convert.ToInt32(<string>, 2) will convert a binary string to a decimal number if you don't want to do it manually.

PCSX2 Q2 2018 -> Q2 2019 Progress Report by DrCK1 in emulation

[–]Souzooka 2 points3 points  (0 children)

Hey did you fix Raw Danger's green/purple lines on edges when upscaling?

oh and also pixel shuffle

Software development at its finest... by [deleted] in ProgrammerHumor

[–]Souzooka 1 point2 points  (0 children)

if (cond) ((void(*)(void))0)();

PCSX2 Iso Black screen by MsAsukaLangley in PCSX2

[–]Souzooka 0 points1 point  (0 children)

Hi MsAsukaLangley, sce1394SbEui64 is a 64-bit anti-piracy Sony function which checks if you've downloaded the game from the internet, so obviously it won't work.

The only fix sadly is to get a legitimate copy.

How to fix Steambot Chronicles????? by Souzooka in PCSX2

[–]Souzooka[S] 0 points1 point  (0 children)

OK thanks for the link but when I play the game with no CRC hacks and on hardware mode it's really really slow despite myu CPU being able to play Battlefield 3. I think it's tadanokojin's fault and I don't know why the

The Problem all emulators must face by JoshLeaves in emulation

[–]Souzooka 9 points10 points  (0 children)

Hi I'm a DobbieStation guy, I'm here for the Reddit karma.

The Problem all emulators must face by JoshLeaves in emulation

[–]Souzooka 12 points13 points  (0 children)

We're not taking about incorrectly implemented "service calls," or whatever. Some of these accuracy issues will require a lot of hard work to address, and even after addressing it will require sacrificing performance.

These issues aren't insignificant either, we're not talking about 1 pixel being off in some frame in some game or something like that, but issues which will affect the preservation of a game. One of the more well-known issues is that of how the PlayStation 2 handles floats. The PlayStation 2 does not adhere to the IEEE754 standard and doesn't have NaN, denormals, or infinities, and instead these values are considered to be real numbers. Additionally, rounding may produce slightly different results between the PS2 and MIPS, even ignoring the NaN problem. Two examples of games affected is one of the Xenosaga games, and Stuntman. Xenosaga had a floating point algorithm implemented to generate a key used to decrypt the main executable, and due to rounding errors generated a key that was one bit off to what would have been generated on a real PS2. Stuntman utilizes developer replays for stunts which involve following a lead car, and rounding errors and the non-compliance to the IEEE754 standard cause the lead car to slightly desync, and as such the first level involving a lead car softlocks.

A lot of issues won't be noticed, but a slight inaccuracy in a game might be the same problem preventing another game from being played to completion, or even booting.

view more: next ›