Closed netkan-bot closed 9 years ago
Comment by Farlo Saturday May 09, 2015 at 02:59 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT
I'm getting the same issue.
Comment by mgsdk Saturday May 09, 2015 at 11:02 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT
I am unable to reproduce this on Linux. Is this on Windows with CKAN 1.6.13?
Comment by playful1510 Saturday May 09, 2015 at 11:05 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT
Unsure about 1.6.13, was occurring on windows 1.6.12. Haven't tested .13
Comment by mgsdk Saturday May 09, 2015 at 11:10 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT
I believe there was some launcher code updates in 1.6.13, but it might only have been for OS X. Else, someone on Windows need to dig into this to debug it.
Comment by playful1510 Saturday May 09, 2015 at 11:10 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT
Testing now w/ same arguments.
Comment by playful1510 Saturday May 09, 2015 at 11:12 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT
Still minimizes when clicked out of. Reproduced on windows 1.6.13
Comment by mgsdk Saturday May 09, 2015 at 11:28 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT
Right, will probably need someone who develops on Windows to look into this.
Possibly fixed since 1.6.13. Possibly @playful1510 and @farlo having "Fullscreen" option ticked in graphics settings. Windows 7 64-bit, steam install of KSP. When CKAN given no argument to pass: KSP launches in visible window halfway between 2 monitors, when CKAN is set to pass -popupwindow KSP launches solely on monitor 1 and acts as expected.
I wish KSP had a --nyan-nyan
switch that we could apply to quickly and easily see if switches are being passed correctly. :)
[Hopeful-eyes at @Sarbian ;) ]
I doubt it will eat the --nyan-nyan properly.
The fullscreen issue is most likely related to the upgrade to Unity 4.6. The default fullscreen is not a true fullscreen anymore. They added a "-screen-fullscreen 1" / "-screen-fullscreen 0". Try with those ? http://docs.unity3d.com/Manual/CommandLineArguments.html
Also for @pjf : remind me to add a logline in MM to get the result of string[] System.Environment.GetCommandLineArgs()
I'm in Windows 8.1, CKAN v1.6.16, KSP 1.0.2 and using -popupwindow in the command line works just fine.
Hey there! I'm a fun-loving automated bot who's responsible for making sure old support tickets get closed out. As we haven't seen any activity on this ticket for a while, we're hoping the problem has been resolved and I'm closing out the ticket automaically. If I'm doing this in error, please add a comment to this ticket to let us know, and we'll re-open it!
Issue by playful1510 Monday May 04, 2015 at 23:31 GMT # Sample: Friday Sep 13, 2013 at 22:58 GMT Originally opened as https://github.com/KSP-CKAN/CKAN-support/issues/131
I have noticed that if I try to have CKAN pass arguments to KSP, they don't make it in. For example, my current CKAN command-line arguments are "KSP.exe -popupwindow" without quotes. KSP still doesn't act like it's in a borderless window, even though it should be getting the argument to start as a borderless window.