If f19 and f20 are 0 @ 80ab73e8 then my code shouldn't be doing anything. Breakpoint 80ab73ec and f0 should be 20. If you're using savestates, maybe try loading the game without them and only using my code.
Working on the hockey simulator pt.2
|
hah mate, I'm sure we'll figure it out at the end, but it will be really interesting to see, what is causing that.
Because I don't use save states in this cases, I even use separate portable/debugger build that is completely clean. So from these screens, it does look as you would expect? Is this correct? 043420f0 3f800000 c2ab689c 00000003 2c030001 40820008 c282ff30 7c651b78 60000000 00000000 c2ab73e8 00000003 fc149840 fc00a090 40a20008 c01e01ec 60000000 00000000 I'll try again...
specs:
Windows 10 Intel i7-9900K @ 4.9Ghz 32 GB RAM Nvidia 1080ti
so this is the breakpoint 80ab73e8 human shooting.
It seems that f19 is indeed 0, but f20 is 3ff...., what do you think?
specs:
Windows 10 Intel i7-9900K @ 4.9Ghz 32 GB RAM Nvidia 1080ti
Also when breakpoint 80ab73ec and f0 is not 20, but 3ff0000000...... (cpu shoot this time)
EDIT: the f0 andĀ f20 is 3ff00000000000 even when human shoot, so that might be our issue? [color=#ffffff][/color]
specs:
Windows 10 Intel i7-9900K @ 4.9Ghz 32 GB RAM Nvidia 1080ti 09-03-2020, 09:27 PM
Right click one of those values and choose to show all as float.
It should be 1 when human shoots. Then you change the first line of the code to fit the accuracy you want and the 1 will change to something else. It should be 0 when CPU shoots. I guess the game could just not be resetting the register, but that seems weird... 09-03-2020, 09:36 PM
do you think that the in-game shot accuracy slider could be affecting it somehow?
specs:
Windows 10 Intel i7-9900K @ 4.9Ghz 32 GB RAM Nvidia 1080ti 09-03-2020, 09:39 PM
(This post was last modified: 09-03-2020, 09:42 PM by One More Try.)
The game has got to be preserving the state of all the floats and then reloading them each time a shot is taken. We use f20 both as a flag that the shot is from a human, and also to hold the accuracy data we want. We can fix that by zeroing out f20 after using it. Multiple ways to do that, but I'll assume f19 is always zero and copy it over to f20, as we require f19 to be zero for the rest of the code to work anyways.
$Shot fixed? 043420f0 3f800000 c2ab689c 00000003 2c030001 40820008 c282ff30 7c651b78 60000000 00000000 C2AB73E8 00000003 FC149840 FC00A090 40A20008 C01E01EC FE809890 00000000 09-03-2020, 09:57 PM
looking promising !!!! I cant hit the net and cpu just scored a goal.
I''ll give it full game....
specs:
Windows 10 Intel i7-9900K @ 4.9Ghz 32 GB RAM Nvidia 1080ti
And working!
Look at the after game stats. It was a short game, but as you can see the difference between the CPU (Flyers) and me (Canadiens) in shots that hit the net is enormous (16:1) That's what we need. Awesome work again!
specs:
Windows 10 Intel i7-9900K @ 4.9Ghz 32 GB RAM Nvidia 1080ti 09-03-2020, 10:57 PM
If only we could just make the cpu goalie better?
Remember to tweak that float on the first line if you need to. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)