search

dmix90 / StoreAppLauncher

Windows Store application launcher for Steam
MIT License
31 stars 2 forks source link

App is no longer generating UWP application files #4

Open squatch04 opened 6 years ago

squatch04 commented 6 years ago

Hello,

I cannot get StoreAppLauncher to generate UWP apps. If i manually set the app ID the UWP app will only launch if I run the executable directly in explorer. If I launch the executable through Steam it no longer works.

I know the app has not been updated in a long time but it has been working great for me until recently. I know there are alternatives (UWPHook) but I rely on downsampling a lot for my games.

Any assistance would be appreciated.

dmix90 commented 6 years ago

Hey! Thanks for letting me know, should be able to look at it soon. Have not touched C++ and Windows 10 APIs in years.... will see how it goes.

dmix90 commented 6 years ago

Sorry for super late reply. Got caught up in UWP stuff. Thinking that it might be possible to publish something presentable to Windows Store. If you don't need gamepad support you can try to use this super dirty version. Parameters for downsampling "-ds" for maximum available res or "-ds:2560x1440" if you want to limit res, "-ffs" to try maximize app window on launch, "-mi" multi instance app, "-cf:60" custom display refresh rate value.

https://mega.nz/#!Hk0WVQaI!o4Yl6MfM1dp_rAjhdI8nXBEYcSt_DrEfMzpHfKj-CZA

I am on 1809 build and it works for me. Should generate executables automatically to "Apps" folder if no appId parameter is provided. Admin rights are not required this time. Should have time soon to make it more presentable and add stuff like gamepad support.

Let me know if it works at all though lol.

squatch04 commented 5 years ago

Hey, just tried out the version that you uploaded and this works for me. The app created the exes and I was able to run them. The only issue I am having is when I exit the app (eg. Forza Horizon 4), I get a popup message error "Failed to set display resolution to specified bounds."

If there's anything that I can do to fix this please let me know. Thanks for taking the time to update the app, I really appreciate it.

All the best for the new year.

dmix90 commented 5 years ago

Thanks for confirmation that it works(...kinda). I can't seem to reproduce the issue so it would be really helpful if you provided some more details.

What is your Windows 10 build version? What is your native desktop resolution and what is your maximum downsampling res? What downsampling parameter or combination of params are you using? What GPU is in your machine? +Anything else you think might help.

Have a feeling this is something related to non standard aspect ratios or stuff like that. Let me know a bit more about your setup, i only tested this version on my native 1920x1080 display with max DSR set in NVIDIA control panel to 3840x2160.

Happy New Year to you as well! :)

squatch04 commented 5 years ago

Hi,

I did a bit more testing and the error is definitely related to VSR, AMD's equivalent to NVIDIA's DSR. If I run the app with no parameters and VSR enabled in AMD Settings, the error will occur on exiting the app. If I disable VSR, the error goes away completely. If I enable VSR, and use the down-sampling parameter (eg. "-ds:2560x1440") the app also exits with no error.

My setup: Windows 10 Pro 1809 build 17763.195 AMD Adrenalin Driver 18.12.3 My native resolution is 1920x1080

Thanks again for looking into it.

dmix90 commented 5 years ago

Ok, thank you. Pretty sure it was my dumb mistake which i actually fixed on my build months ago but forgot to publish . . .

Please try this one -> https://mega.nz/#!HpsHnSJb!WuCRVYxo_PWuNeiCm8MYBn1_548sB0V7U3aO0dxim00

squatch04 commented 5 years ago

Hey dmix90,

I tried this version and unfortunately it displays the same error. The error is only displayed for about 2 seconds before it closes.

dmix90 commented 5 years ago

Damn. No clue, and not much time to figure out and more importantly, no modern AMD GPU with VSR support in drivers to test this on my machine.

Did the worst thing and just made this error only appear in debug builds in console window heh.

Download here -> https://github.com/dmix90/ClassicLauncher/releases

squatch04 commented 5 years ago

Good news. This version is not displaying the error. I can also use additional parameters like -ffs and -ds, with no issues.

I really appreciate that you took the time away from your work to get this fixed.

Thanks