Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - FantasticMrSocks

Pages: [1]
1
download 1998 1.02 executable.  it was a released patch.  place in root folder and use that instead of steam launcher.
I did this, and the flickering help window still appears.

2
so what's best solution? reunion doesn't use steam so how's it affecting game?  is it a case of setting steam controller to none?  if so, is that for ff7 alone?
I'm beginning to suspect that the flickering help window isn't a Steam Controller issue after all. I've just tried starting up the game with no controllers connected whatsoever, deleting ff7input.cfg, and only using the default R06d controls (WASD movement, R to select, etc). The flickering help window still occurs in battles, and pressing Backspace doesn't turn it off.

3
Why does it need mapping twice?  Surely a controller should just needmapping only in ff7? 

In the case of the Steam Controller, at least, the bindings set in Steam are what gets sent on to the game. So in my case, my controller sends a "numpad enter" to the game when I press the B button (which would be the O button if this were a PS controller). The controller doesn't send any xinput/directinput of its own; everything goes through the Steam mappings.

The default button settings for controller  should probably be "none" for all.  I'd suggest everyone remaps the controller buttons in  FF7's submenu as well and see if that helps.

I'm not sure how to remap the buttons to "none". There doesn't seem to be any way in-game to clear the bindings.

4
Here's the in-game control screen: https://i.imgur.com/nzD09YX.png
For reference, I'm using a Steam controller with its buttons mapped to the relevant keyboard keys, as seen here: https://i.imgur.com/ceZBaV4.png

With 60fps disabled, L2 does not toggle the help window.

I know my way around a debugger, but not quite so far as reading memory directly. What tools do you use for debugging?

5
Hi, I'm also seeing this issue. I've just made this account, so I can't attach to posts, but here's a link to a Google Drive folder with the relevant files: https://drive.google.com/open?id=15IGFhiRgKLIole-4OC12IFcbDeV99nuN

Per the template:

1. An explanation of the bug
Help window in battles is always on and flickering. The flicker happens with 60fps battles enabled, either interpolated or non-interpolated. It does not happen with 60fps battles disabled. It appears to switch between flickering at 15hz and 30hz. When it flickers at 15hz, all battle animations run at half speed. It does not affect the rest of the UI, which still runs at 60fps with no slowdown.

My save file was created in a game running Reunion r06b, which was updated to r06d. It has the help window mapped to Select rather than L2. When 60fps battles are enabled, pressing Select does not turn off the help window, but does interrupt the flicker very briefly, for a frame or two. When 60fps battles are not enabled, pressing Select toggles the help menu as usual.

I did not see this issue in r06b; it only started happening as soon as I installed r06d.

2. Does the bug happen at same point more than once?
It happens in every battle. The issue persists even after restarting the game or rebooting the computer.

3. App.log (found in root folder)
In Google Drive link

4. Reunion.log (found in The_Reunion folder)
also in Google Drive link

5. crash.dmp (found in root folder)
Not a crash, so no crash dump available

6. Your save file from just before the crash or hang
Not a crash, but I've included a save file anyway.

7. Audio.log (found in The_Reunion folder)
Not an audio issue, but I know bugs can turn up in the weirdest places so I've included that as well.

8. Your CPU spec
Intel Core i708650U; 1.9 GHz

9. Your operating system
Windows 10, version 1909

It may also be useful to note that I'm using a Microsoft Surface Book 2 with discrete graphics. I don't know how useful that information may be to triaging the bug, but if anyone else runs into the same problem on the same hardware then at least they'll know it's not just them.

I've also included hext.log in the google drive folder, since you mentioned above that there might be a hext issue. As for the exe file, I have not modified any executables in this installation, so they came straight from Steam.

Pages: [1]