Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not start on some systems #6

Closed
Marat-Tanalin opened this issue Sep 15, 2020 · 1 comment
Closed

Does not start on some systems #6

Marat-Tanalin opened this issue Sep 15, 2020 · 1 comment

Comments

@Marat-Tanalin
Copy link
Owner

@Marat-Tanalin Marat-Tanalin commented Sep 15, 2020

Two users (RichterEX2 via Reddit and Philip via email) reported that bsnes-mt does not start on their systems. This might be related to different default settings, but using settings.bml (renamed to bsnes-mt-settings.bml used by bsnes-mt) from original bsnes v115 seems not to help. This also might be related to certain antivirus software.

Details from RichterEX2:

  • Tested bsnes-mt versions: 1.0, 1.1.1.
  • Restarting computer didn’t help.
  • bsnes v115 does work.
  • Windows 10 x64
  • UI Language: English

Details from Philip:

  • Tested bsnes-mt version: 1.3.
  • bsnes v115 does work.
  • In bsnes v115, all drivers work, regardless of the “Synchronize” video setting.
  • Antivirus: none (probably Windows Defender then).
  • Resetting drivers with --resetdrivers command-line option does not help.
  • System specs:
    • Windows 10
    • Intel Pentium 4415U 2.30GHz
    • 8GB RAM
    • Intel HD Graphics 610
    • Display: 1366×768
    • OS-level zoom: 100%

Information that those who would like to help could provide

  • Does original bsnes v115 work on the same system?
  • System specs (at least GPU).
  • Exact version of Windows 10: e.g. version 1909, build 18363.1082.
  • Graphics-driver version.
  • Desktop resolution and whether it’s equal to display’s native resolution.
  • OS-level zoom (e.g. 100, 150%, or 200%).
  • Name of the antivirus software used.

How to get Windows 10 version information:

  1. Press Win+R keyboard shortcut.
  2. Type winver command.
  3. Press Enter key or OK button.
@Marat-Tanalin
Copy link
Owner Author

@Marat-Tanalin Marat-Tanalin commented Sep 25, 2020

So this was due to the local compilation flag set to true by default that resulted in the executable nonworking on some systems different from the one the executable was built on.

Thanks Philip P. for feedback and testing.

Marat-Tanalin added a commit that referenced this issue Sep 25, 2020
...due to the `local` compilation flag set to `true` by default. Now switched to `false`. Fixed #6.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.