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

Gupax won't launch #78

Open
kurpav00 opened this issue Jan 26, 2024 · 12 comments
Open

Gupax won't launch #78

kurpav00 opened this issue Jan 26, 2024 · 12 comments
Labels
bug Something isn't working

Comments

@kurpav00
Copy link

OS & Version:

Windows 10 Home, Gupax v1.3.5

Bug

When I try running Gupax.exe, nothing happens. It does not matter if I try launching it by double clicking or in a command prompt. In command prompt, the program simply terminates after a few seconds returning the %errorlevel% 0, but no GUI is opened.

Steps

Steps to reproduce the behavior:

  1. Go to the downloaded and unpacked Gupax folder (added among the virus protection exceptions)
  2. Double click Gupax.exe (or run Gupax.exe from command prompt)
  3. See nothing happening, no errors, no messages, nothing

Screenshots

Capture
no GUI opened

Crash report

No crash.txt file is generated.

@kurpav00 kurpav00 added the bug Something isn't working label Jan 26, 2024
@hinto-janai
Copy link
Owner

What is your CPU & GPU?

@kurpav00
Copy link
Author

kurpav00 commented Feb 1, 2024

Intel Celeron B830 CPU @ 1.80GHz
Intel HD Graphics

@hinto-janai
Copy link
Owner

Can you see if using v1.3.3 works?

@kurpav00
Copy link
Author

kurpav00 commented Feb 9, 2024

Yes, v1.3.3 works. V1.3.4 and 1.3.5 don't. Thank you.

@Cyrix126
Copy link

Cyrix126 commented Apr 4, 2024

@kurpav00

Hello can you try my fork ? specially for windows it is using a different backend for rendering (glow instead of wgpu) and it's using more up to date deps. Let me know if it works for you.

@kurpav00
Copy link
Author

@Cyrix126 I tried both the version 1.0.0 and 0.1.10, but none of them works, demonstrating the same behavior - the program does not launch at all, returning the exit status 0.

@Cyrix126
Copy link

Cyrix126 commented Apr 15, 2024

@kurpav00 ,
Would you like help me debug your issue ? we can talk over matrix or session, whichever you prefer. I will give you a build that will create a log file at runtime. That should help knowing what's going on.

matrix id

@lm:matrix.baermail.fr

session id:

05847cdfbefe4616e902b1692d58c0cd2c3b8fc27dc66154b8da593282c186355e

@Cyrix126
Copy link

After having the log file, here is the relevant part.

DEBUG [eframe] Using the glow renderer
DEBUG [eframe::native::glow_integration] Event::Resumed
DEBUG [eframe::native::glow_integration] trying to create glutin Display with config: ConfigTemplateBuilder { template: ConfigTemplate { color_buffer_type: Rgb { r_size: 8, g_size: 8, b_size: 8 }, alpha_size: 8, depth_size: 0, stencil_size: 0, num_samples: None, min_swap_interval: None, max_swap_interval: None, config_surface_types: ConfigSurfaceTypes(WINDOW), api: None, transparency: false, single_buffering: false, stereoscopy: None, float_pixels: false, max_pbuffer_width: None, hardware_accelerated: None, max_pbuffer_height: None, native_window: None } }
DEBUG [eframe::native::glow_integration] using the first config from config picker closure. config: Wgl(Config { inner: Config { hdc: 1057034209, pixel_format_index: 2 } })
DEBUG [eframe::native::glow_integration] successfully created GL Display with version: WGL and supported features: DisplayFeatures(FLOAT_PIXEL_FORMAT | SWAP_CONTROL | MULTISAMPLING_PIXEL_FORMATS | SRGB_FRAMEBUFFERS)
DEBUG [eframe::native::glow_integration] creating gl context using raw window handle: Some(Win32(Win32WindowHandle { hwnd: 0xe073a, hinstance: 0x7ff77dca0000 }))
WARN [eframe::native::glow_integration] Failed to create context using default context attributes ContextAttributes { release_behavior: Flush, debug: false, robustness: NotRobust, profile: None, api: None, shared_context: None, raw_window_handle: Some(Win32(Win32WindowHandle { hwnd: 0xe073a, hinstance: 0x7ff77dca0000 })) } due to error: [ffffffffc0072095] OS Error -1073274731 (FormatMessageW() returned error 317) (os error -1073274731)
DEBUG [eframe::native::glow_integration] Retrying with fallback context attributes: ContextAttributes { release_behavior: Flush, debug: false, robustness: NotRobust, profile: None, api: Some(Gles(None)), shared_context: None, raw_window_handle: Some(Win32(Win32WindowHandle { hwnd: 0xe073a, hinstance: 0x7ff77dca0000 })) }
ERROR [eframe::native::run] Exiting because of error: glutin error: extension to create ES context with wgl is not present during event Resumed
DEBUG [eframe::native::run] Asking to exit event loop…
DEBUG [eframe::native::run] Received Event::LoopExiting - saving app state…
DEBUG [eframe::native::run] eframe window closed

@Cyrix126
Copy link

It seems that the cpu is limited to OpenGL 3.1. Maybe glow/glutin is trying to create a context with a newer version. I'll investigate this further.

@Cyrix126
Copy link

using wgpu instead of glow output this warning:

WARN [wgpu_hal::gles::adapter] Returned GL context is 3.1, when 3.3+ is needed

@hinto-janai
Copy link
Owner

@Cyrix126 thanks for investigating this, does this mean CPUs pre-2010 are not supported? Is there a simple fix or is there a tradeoff in supporting OpenGL <3.3?

@Cyrix126
Copy link

Cyrix126 commented May 3, 2024

@hinto-janai you can see a simple fix here Cyrix126@bf74131
You need to bring wgpu dependence with the same version that eframe use and enable the angle feature.
See the issue I mentioned if you want to know the details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants