Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Tools => Topic started by: ngld on October 29, 2017, 10:14:17 am

Title: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on October 29, 2017, 10:14:17 am
Knossos is a new and combined launcher/installer. It can install mods (and FSO) for you.
(https://i.imgur.com/eSZmxjx.png)


Windows Installer (https://fsnebula.org/knossos/stable/Knossos.exe) | macOS Bundle (.dmg) (https://fsnebula.org/knossos/stable/Knossos.dmg)
Other download links and installation instructions (https://fsnebula.org/knossos/)


VERY IMPORTANT: Due to changes in FSO 3.8.0, Knossos will store the engine settings in a new location (%appdata%\HardLightProductions\FreeSpaceOpen on Windows). As a result, once you've used Knossos, all legacy launchers (like 5.5g and YAL) will be unable to start 3.8.0 properly until you delete the new settings folder.

What works:

Known issues:

Stuff planned for the next beta:

Here's a video mjn.mixael did during development, most issues seen here have been fixed:

IMPORTANT NOTE: Since this is a beta, all errors will be automatically reported to me. If you don't want this, go to settings and turn off the automated error reports. In case you're wondering, the only personal information that can be sent here is your username since it often ends up in paths (like C:\Users\someone\AppData\Knossos\...) and your computer name.

Huge thanks to mjn.mixael for the excellent UI work without him Knossos probably would still look like this (https://dev.tproxy.de/knossos/images/screen6.png).
I'm looking forward to your opininons, bug reports and other comments! (We also have a #knossos channel on HLP's Discord)

If you're interested in contributing or want to take a look at the source code, the code is hosted on GitHub (https://github.com/ngld/knossos). Bugs can be reported here or there.
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: mjn.mixael on October 29, 2017, 03:09:49 pm
Concept for First Run wizard that we'll be working on for the next release...

This biggest change here is just adding the default install location. Most people shouldn't have to worry about this.
(https://i.imgur.com/si30T37.png)
Turns out this doesn't need an autodetect button. Instead Knossos does that automatically and we just let the user know if we detected FS2 here instead of all these BUTTONS.
(https://i.imgur.com/dNWjYPI.png)
If you point it towards a way to get Retail, let's give some sort of visual feedback that something is happening, even if it's super fast copying of files.
(https://i.imgur.com/eB86xko.png)
Or the user can skip this step.
(https://i.imgur.com/tL48vFY.png)
Explore should link to the Explore tab, MediaVPs should link to the MediaVPs Details page.
(https://i.imgur.com/10Aht5D.png)
If the user has not installed Retail Freespace 2, let's add a button in Settings that just takes them right back to Page 2 of the Getting Started wizard. It should go on from there including Page 3 to suggest the MediaVPs.
(https://i.imgur.com/E4YUgCK.png)


The other thing I would add (and this would relate to the Last Played data that we don't currently track) is a prompt on the first run of Retail FS2 that says "Looks like you want to play the original Freespace 2 game. We just wanted to let you know that this is exactly the game that was released in 1999. If you want to play graphically updated version, you should install the MediaVPs"

Feedback? Does this cover all the potential hiccups for new players?
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: mjn.mixael on November 13, 2017, 01:45:54 am
I'm just gonna leave this here....

(https://i.imgur.com/n6LoRAl.jpg)
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: m!m on November 13, 2017, 02:37:28 am
Could the mod version numbers be removed from the Home and Explore tabs? It looks weird to see a version number that often has no real meaning since for all mods except maybe the MediaVPs only the latest version matters.

Does the mod.json format and Nebula support changing the mod title for every version? That could be used in this list instead if the version is relevant for the mod (e.g. MediaVPs 3.7.2 would be displayed as MediaVPs 2014).
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: niffiwan on November 13, 2017, 03:38:33 am
Wow guys. Just.. wow, that looks so awesome...
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: Spoon on November 13, 2017, 05:52:08 am
Wow guys. Just.. wow, that looks so awesome...
QFT
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: jr2 on November 13, 2017, 07:45:26 am
Wow guys. Just.. wow, that looks so awesome...
QFT

:nod:
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: Axem on November 13, 2017, 07:15:30 pm
The work done on uploading mods to Knossos over the last few weeks has been nothing but unbelievable. Going from just FSO and the MediaVPs at the start of the month to now a total of 43 downloadable mods! (And there's still lots more to get uploaded)

Everything looks so cool and professional, hats off to ngld and mjn for their tireless work so far!

A second hat off to mjn for all that cool art made/remade for the campaigns, and a third hat off to PIe for uploading a good number of campaigns too. You guys are awesome.

Like really awesome.
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: karajorma on November 14, 2017, 09:49:25 pm
TCs are implemented but haven't been tested. Feel free to report any related bugs!

Okay, Diaspora is now available for people to test whether TCs install correctly. Quite frankly I'm rather surprised we beat Wings of Dawn to be the first TC on Knossos.
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: mjn.mixael on November 15, 2017, 01:54:13 am
I had no issues installing and loading up Diaspora.
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: Spoon on November 15, 2017, 06:24:07 am
Okay, Diaspora is now available for people to test whether TCs install correctly. Quite frankly I'm rather surprised we beat Wings of Dawn to be the first TC on Knossos.
Well, this way Diaspora can be the guinea pig  ;7

I plan on putting WoD on Knossos good and proper when I release episode 2, episode 1 is too old and busted right now.
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: chief1983 on November 15, 2017, 08:52:21 am
Good to hear that's working, hoping for FotG to be the first TC to use ACLs for private beta testing distribution :)
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: Cyborg17 on November 16, 2017, 06:42:45 pm
Totally stupid suggestion: a "Complete" tag or checkmark or something would be very satisfying to mark mods that you have completed.   ;7
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: chief1983 on November 16, 2017, 06:54:47 pm
I don't think there's currently an easy way to determine that from outside of the game engine, if at all.
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: Cyborg17 on November 16, 2017, 06:55:49 pm
I meant one the player could check, themselves.
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: karajorma on November 16, 2017, 09:12:39 pm
When filtering gets added that and unplayed should definitely be options.
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: potterman28wxcv on November 17, 2017, 09:12:26 am
It works fine, but on my end sometimes it takes ages to register my inputs.

For example I will click on "Install". And only 5 minutes after it actually starts installing. Not sure what's the cause of it.

Other than that, it got me back into Freespace :P Currently playing the Ancient-Shivan war campaign !
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: CapellaGoBoom on November 18, 2017, 09:24:32 am
This works really well so far! Also got a curious question: Will you consider adding ship models as downloads? (i.e. revamped apollo, anuket, leviathan, etc). Just wondering if that is at all possible
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: AdmiralRalwood on November 18, 2017, 04:47:08 pm
This works really well so far! Also got a curious question: Will you consider adding ship models as downloads? (i.e. revamped apollo, anuket, leviathan, etc). Just wondering if that is at all possible
It might be possible with the Extension system (which hasn't been implemented yet), but it would be preferable for there to be a newer MediaVPs release incorporating all of them instead.
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: niffiwan on November 18, 2017, 06:50:51 pm
I guess single-ship mods could also be created (with the mediavps as a dependency). That might balloon the number of mods quite quickly though :)
Title: Re: PUBLIC BETA: Knossos 0.6.0 (combined launcher/installer)
Post by: mjn.mixael on November 18, 2017, 11:06:25 pm
Yeah.. I would prefer we stay away from doing that. I've been working on an updated MediaVPs. My time is just limited. I'm shooting for January.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: Crashdown117 on November 30, 2017, 04:31:20 am
Okay, so I got this awesome new launcher/installer, my freshly reinstalled retail FS2 and a couple of mods downloaded via the "Explore" tab (which btw worked really fast even with my ****ty Internet). Only one little problem: My old profile doesn't show up in the pilot selection screen (and yes, I restored my old player data the very second after I had finished reinstalling, it's right where it always has been). I already tried copying everything missing to the new directory, Knossos created within my FS2 folder, but that didn't do the trick either. Does Knossos somehow affect where the game goes looking for player files or am I missing something else here?
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: m!m on November 30, 2017, 04:34:19 am
The pilot file location changed when FSO 3.8 was released. wxLauncher automatically copies all the relevant files but since Knossos only support 3.8 it doesn't do that (at least as far as I know). If you want to continue using your old pilot files then the easiest solution would be to install wxLauncher and launch FSO once. That will copy all the pilot files to the correct folders.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: Crashdown117 on November 30, 2017, 12:04:45 pm
Found the new diretory by searching, but thanks anyway!
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: jr2 on November 30, 2017, 10:43:36 pm
Don't some mods require older versions of FSO to work properly (at least, until FSCRP gets ahold of them)?  In which case, perhaps something should be done with this?  This sounds like something that was already discussed, I must have missed that.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: mjn.mixael on December 01, 2017, 12:54:56 am
Knossos requires FSO 3.8 or newer to work. So any mods that absolutely require < 3.8 are not compatible with Knossos. However, this should be a very small number, if any.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: CT27 on December 02, 2017, 08:38:19 pm
https://www.hard-light.net/forums/index.php?topic=94068.msg1857856#msg1857856

mjn, on this post picture, "The Aeos Affair" is listed as version 1.0.0, but the version I have downloaded (in the past, not from Knossos) says it was version 2.0.  Does Knossos have an earlier version of the campaign or is this a special version for Knossos?
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: mjn.mixael on December 02, 2017, 09:38:35 pm
Knossos mod versions != non-Knossos mod versions in general. At least not when we're mass uploading every mod ever.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: Cyborg17 on December 03, 2017, 07:38:31 am
Can the modder overwrite version numbers?
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: AdmiralRalwood on December 03, 2017, 09:47:50 am
Can the modder overwrite version numbers?
The version number is specified by the modder, if that's what you're asking.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: mjn.mixael on December 03, 2017, 09:52:40 am
You can't change the version number of uploaded mods. Modders can upload new versions of the same mod, which will become the default download/install for users. The old version will always be available.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: Satellight on December 04, 2017, 03:35:08 am
Hello !

I have a problem on the "settings" tab : I select my joystick (T-16000M), then click "save", but Knossos don't remember my choice (evey time I return to the "settings" tab, "no joystick" is selected again).

Any advice ?

Anyway, excellent work on this  :yes:
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: ngld on December 04, 2017, 06:14:31 am
This might be related to a different bug where the saving worked but FSO used a different joystick. I'll release 0.7.2 soon and if that doesn't fix your issue I'll look into this further!
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: CapellaGoBoom on December 06, 2017, 10:44:52 pm
Got another question: Will there be a graphic preset feature similar to wxlauncher in the future?
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: ngld on December 06, 2017, 11:02:39 pm
That depends on whether enough people want something like that and how hard it'd be to implement. 0.7.1 introduced the ability for users to set mod-specific flags 0.7.2 or 0.8.0 will add global flags. Since the lightning presets from wxLauncher are just flags, those could be implemented afterwards using the same mechanism.

However, I can't say anything more specific until those are done. The biggest problem so far is that Knossos doesn't handle flags the same way wxLauncher does. wxLauncher just saves the flags in profiles which the user can save and load. Apart from that there was just a single global list of active flags. Knossos saves flags for every installed mod. By default, the flags supplied by the modder are used and can be changed by the user.
The upcoming global flags won't straight up replace these defaults but rather act as a filter by removing or adding specific flags from the modder default.

The idea is that modders supply sensible defaults and unexperienced users can just install a mod without having to worry about flags. More experienced users can still modify those flags.
Another thing I just remembered; we can't reuse the graphic presets from wxLauncher since 3.8.0 has a different rendering engine and needs new graphic presets.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: Cyborg17 on December 07, 2017, 04:10:43 pm
Having trouble downloading the mac version.  My internet connection is not great, and it says that it will take five hours to finish the 69 MB download. But we can watch netflix here without a problem. :confused:  After a while it tends to fail before it gets to a MB...

Edit: Tried it again, it worked in five minutes....  :wtf: :blah: ;7
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: Novachen on December 07, 2017, 04:53:16 pm
For a german speaking installation manual that will also include Knossos i have to delete it and reinstall it again for Screenshots. But in that process i found out, that i am not able to install one of my own Modification anymore  :banghead:

Knossos is always complaining "I'm sorry, but you won't be able to install "FreiRaum: Stille Bedrohung: Wiedergeboren"  because "FSO" is missing."

But i have also reinstalled FSO of course. I am using the last stable and nightly build and all other modifications are installable and working. But i can not even install that one, to change any settings in the Development tab. I fear, that i have accidentally selected a Nightly build for the default settings back then...and now Knossos has trouble because it want this particular version or something. But i get this message even after i have installed all available nightly versions in the FSO Details.

EDIT:
Quote
INFO:Thread-3:tasks.init2: Nothing to do for this InstallTask!
WARNING:Thread-10:progress.add_task: Added an empty task of type "LoadLocalModsTask". Ignoring it!
ERROR:MainThread:windows.show_packages: Well, I won't be installing that...
Traceback (most recent call last):
  File "C:\knossos\knossos\windows.py", line 385, in show_packages
  File "C:\knossos\knossos\repo.py", line 384, in process_pkg_selection
knossos.repo.PackageNotFound: No version of mod "FSO" found for these constraints: >=3.8.1-20171124,>=3.8.0-2,==3.8.0-2

Well, i even tried to install only the 24th November build and to uninstall every other one... without effect.  :confused:
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: ngld on December 07, 2017, 07:00:42 pm
@Cyborg17: No idea what's going on there. The downloads are hosted on Amazon S3 (thanks to GitHub) so it really shouldn't be causing these problems.

@Novachen: Those constraints are impossible to fulfill (no version can match both ==3.8.0-2 and >=3.8.1-20171124). This might be caused by a bug in earlier Knossos versions. I need to go through the DB and fix all mods affected by this. Unfortunately, I can't take care of that right now but I'll do it tomorrow.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: ngld on December 10, 2017, 04:57:00 am
Should be fixed now.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: xenocartographer on December 10, 2017, 10:22:17 am
There doesn't seem to be a way to repair the download for a mod, short of uninstalling it and trying again. Okay, that's fine, but if mod A depends on mod B and only B's download fails, it seems like both have to be uninstalled... which is fairly suboptimal when A is BPC, like just happened to me.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: ngld on December 10, 2017, 10:52:54 am
Go to the Explore tab and click "Modify" on the relevant mod. Make sure the correct packages are selected and press OK. After that Knossos should repair the mod. It's not particularly obvious but I'm not sure how to explain this without some guide or help text.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: Bryan See on December 10, 2017, 12:18:59 pm
I tried to create total-conversion mod on the Development tab of Knossos launcher. However, the message appeared, saying that: "The chosen parent does not exist! Something went very wrong here!!"

Is this a problem or not?
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: xenocartographer on December 10, 2017, 03:12:07 pm
Go to the Explore tab and click "Modify" on the relevant mod. Make sure the correct packages are selected and press OK. After that Knossos should repair the mod. It's not particularly obvious but I'm not sure how to explain this without some guide or help text.

There doesn't appear to be any way to reinstall the damaged packages without uninstalling the whole thing. The damaged packages are listed as "installed", the checkboxes are disabled, etc.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: ngld on December 10, 2017, 03:33:19 pm
@Bryan See: That's a bug. I'll fix it in the next version but you can try the following workaround: Go to your base folder (the one you selected during the first run) and create a directory named after your mod's ID next to the FS2 and bin directories. Now you should be able to create your TC in Knossos.

@xenocartographer: Did you try clicking on OK? Afterwards it should check all selected mods (even those which are marked as installed) and install any missing files. A better solution would be to modify the "Verify file integrity" option to ask if Knossos should repair damaged or missing files if those were detected. That probably makes more sense than going through the installation dialog a second time.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: xenocartographer on December 10, 2017, 10:03:46 pm
Oh, no, I didn't. I thought I'd have to enable something in the UI that wouldn't let me enable things. It would definitely make more sense in the integrity option, yes.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: Bryan See on December 11, 2017, 04:32:28 am
Thanks for that. Until that bug is fixed, I'll stick to this.
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: chief1983 on December 13, 2017, 12:09:53 pm
First run on my new work El Capitan MBP, thought I would document my experiences with it as I haven't  touched it in quite some time.

It expectedly tells me the app is not authorized to run after trying to run it via Spotlight.  So I right-click -> Open, it asks if I want to run the app, I hit OK, then I get this error dialog:

Code: [Select]
I don't know how to handle "-psn_0_401506"! I only know fso:// .
I suspect that it has something to do with having to do the first run via the Finder to get past the security checks, but not sure.  If I hit ok, then run it again via Spotlight or Finder it starts fine.

On the Welcome screen, there is no suggested path for Knossos game data yet for Macs, and the process to Browse for one doesn't seem to allow creating a new directory, so I chose /Users/home.dir, and then manually typed /Knossos onto the end of that, which worked as expected (it asked if I wanted to create it after hitting OK).

Could not remember exactly how it was supposed to integrate with FS2, so I just clicked 'Install' on FSO, and it asked which binary with the only available one already checked, hit OK, it went to 100% download and then said there was an error installing and to check the error log.  I don't see an option to uninstall it and I was never asked where FS2 was or anything like that.  I was not told where to find the log, but after some educated guess I think I found it at ~/.knossos/log.txt.  The end result seems to be that my Knossos folder has a bin folder, with a FSO-3.8.0-2 folder, with two PNG files and a mod.json file inside of it, but nothing else.

Code: [Select]
INFO:MainThread:launcher.main: Running Knossos 0.7.1 on PyQt5 and Python 3.5.3 (v3.5.3:1880cb95a742, Jan 16 2017, 08:49:46)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)].
WARNING:MainThread:integration.init: No desktop integration active.
WARNING:MainThread:tasks.__init__: A LoadLocalModsTask was launched even though no base path was set!
WARNING:MainThread:progress.add_task: Added an empty task of type "LoadLocalModsTask". Ignoring it!
INFO:MainThread:web.searchRetailData: No SteamPath detected!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20171212 (FSO)> is empty, ignoring it!
INFO:Thread-3:util.download: Downloading "https://fsnebula.org/storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png"...
INFO:Thread-3:util.download: Downloading "https://fsnebula.org/storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png"...
INFO:Thread-3:util.download: Downloading "https://fsnebula.org/storage/d2/2d/ac5f570fdeee977185dfd24e4b59b9ccb8b3031af6db545100487568379a"...
ERROR:Thread-3:tasks.work2: Failed to unpack archive "OS X (Universal).7z" for package "OS X (Universal)" (FSO)!
ERROR:Thread-3:util.get: Failed to load "https://fsnebula.org/api/1/api/1/track/install/FSO"! (404 NOT FOUND)
INFO:Thread-9:tasks.init2: Nothing to do for this InstallTask!
WARNING:Thread-8:progress.add_task: Added an empty task of type "LoadLocalModsTask". Ignoring it!
INFO:Thread-5:repo.add_mod: Mod "FSO" (3.8.0-2) from "None" overwrites an existing mod version!

I am wondering if translations of games could somehow be presented differently, maybe with a dropdown option in the menu, but also defaulting to whatever language Knossos is presented in (if Knossos is ever translated, hoping it will support that in the near future with all the excitement about UTF8 support in FSO now).
Title: Re: PUBLIC BETA: Knossos 0.7.1 (combined launcher/installer)
Post by: ngld on December 14, 2017, 03:55:03 am
Thanks for the detailed feedback!

The first error essentially tells you that it doesn't know that command line flag but I guess I can safely ignore any flags that start with "-psn_" which should solve that.
On the Welcome screen, the default path should've been ~/Documents/Games/FreespaceOpen but due to a stupid mistake on my side that didn't work (I wrote "macos" instead of "darwin" in the platform check).
I'm not sure how much I can influence the Browse dialog since that's part of Qt but I'll look into it.

From your post I suppose you didn't see the rest of the wizard (you can see the mockups in the second post of this thread). Did you run Knossos on that machine before?

The error Knossos encountered when you tried to install FSO was that 7zip failed. However, the output isn't captured so I don't know why. Everything else seems to have worked as expected. Can you open a terminal and run the following command? That should provide us with a better error message.
Code: [Select]
KN_DEBUG=1 /Applications/Knossos.app/Contents/MacOS/Knossos

Knossos already has partial translation support, I just need to find a good solution to translate the templates to complete it. Regarding translated mods: I hope that we can use the tag system once it's implemented for that.
We could add a question at the end of the first run wizard asking the user which languages they want to see with their own selected by default. Based on that selection a tag filter is then applied to the mod list by default.
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: chief1983 on December 14, 2017, 11:09:51 am
I feel like the Qt browse dialog in this instance was missing a button I often see that allows creation of new directories.  Without that, I was wondering if it makes sense to always append /Knossos to whatever was chosen, if they chose a non-empty directory that doesn't look like it ever contained Knossos data.

I don't believe I saw the wizard I guess, no.  It was my first _successful_ run, as I mentioned, the first actual attempt had resulted in the crash I mentioned.  Not sure if that was related or not but Knossos definitely had not existed on this Macbook before.  I did restart Knossos at one point to test whether the error was happening in Finder vs Spotlight, but I can't recall if I did that before or after choosing a data path.  I can give it another try from scratch after 0.7.2 is up for Macs, I would just need to delete ~/.knossos and ~/Knossos in order to reset it right?  Or are there any other property/config file locations to purge?

I have a theory on the failed 7zip.   I believe the CI system told Nebula that the Mac build was successful, however the download for the 12/12 build was corrupt.  We moved it out of the folder to make the Nightly post, which does not contain it, but then I put it back since I wasn't sure I wanted to delete it yet.  The nightly system will now ignore corrupt uploads in the future, so Knossos may need some error handling in this case as well if it wants to be bullet-proofed against this particular issue.  If I had left the file deleted, would Knossos currently have behaved any more intelligently, or would it have still broken due to the missing file?
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: ngld on December 14, 2017, 01:17:58 pm
Deleting ~/.knossos and ~/Knossos should be enough.

I have a theory on the failed 7zip.   I believe the CI system told Nebula that the Mac build was successful, however the download for the 12/12 build was corrupt.  We moved it out of the folder to make the Nightly post, which does not contain it, but then I put it back since I wasn't sure I wanted to delete it yet.  The nightly system will now ignore corrupt uploads in the future, so Knossos may need some error handling in this case as well if it wants to be bullet-proofed against this particular issue.  If I had left the file deleted, would Knossos currently have behaved any more intelligently, or would it have still broken due to the missing file?
Well, the the theory is nice but the log clearly states that Knossos downloaded the 3.8.0 build from the Nebula (this one: https://fsnebula.org/storage/d2/2d/ac5f570fdeee977185dfd24e4b59b9ccb8b3031af6db545100487568379a). So that probably isn't the reason.

Regardless, you're right. If you tried to install the nightly after deleting the file on the server, it would still have failed. Knossos decides on which version to install based on the metadata and doesn't change this decision if the installation fails. It assumes that any mod listed on the Nebula has at least one working download link. The FSO builds are a special case in this regard. Everything else is hosted on the Nebula itself so I don't have to worry about broken download links.
If the nightly script doesn't submit corrupt archives, everything should be fine. I can add a check to remove builds which aren't available anymore, though, since that will probably be useful in case you delete old nightlies.
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: chief1983 on December 14, 2017, 01:21:03 pm
I guess from the log I wasn't sure which one had failed to extract, as it mentioned both 3.8.0 and a 3.8.1 nightly.  If you can tell that it was the 3.8.0 that had failed to extract for sure, that is odd then.  I will  try to rerun with the debug stuff set and see if anything odd happens.
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: chief1983 on December 14, 2017, 01:29:09 pm
Ok I think I have much more useful information now.  Reran with the debug argument you suggested, and got these two tidbits.

The wizard did appear to go to another step after I chose my data directory.  I saw a screen with a couple more one line text input boxes I think, but only for a split second before that disappeared and took me to the Explore tab of the interface.  The console output up to that point was as follows (I think  this was where it cutoff before I clicked the next thing):

Code: [Select]
INFO:MainThread:launcher.main: Running Knossos 0.7.1 on PyQt5 and Python 3.5.3 (v3.5.3:1880cb95a742, Jan 16 2017, 08:49:46)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)].
DEBUG:MainThread:launcher.main: Loading resources from data/resources.rcc.
DEBUG:MainThread:launcher.main: Loading settings...
DEBUG:MainThread:base.set_dsn: Configuring Raven for host: <raven.conf.remote.RemoteConfig object at 0x11e2c82b0>
DEBUG:MainThread:util.call: Running ['/Applications/Knossos.app/Contents/MacOS/7z', '-h']
WARNING:MainThread:integration.init: No desktop integration active.
Path override failed for key ui::DIR_LOCALES and path '/Applications/Knossos.app/Contents/Resources/qtwebengine_locales'
[1214/132155.866837:WARNING:resource_bundle_qt.cpp(115)] locale_file_path.empty() for locale
Path override failed for key ui::DIR_LOCALES and path '/Applications/Knossos.app/Contents/Resources/qtwebengine_locales'
[1214/132155.975771:WARNING:resource_bundle_qt.cpp(115)] locale_file_path.empty() for locale
DEBUG:MainThread:windows.watch_task: Task "Checking for updates..." (4805491160, <class 'knossos.tasks.CheckUpdateTask'>) started.
DEBUG:Thread-1:connectionpool._new_conn: Starting new HTTPS connection (1): dev.tproxy.de
WARNING:MainThread:tasks.__init__: A LoadLocalModsTask was launched even though no base path was set!
DEBUG:MainThread:windows.watch_task: Task "Loading installed mods..." (4806508760, <class 'knossos.tasks.LoadLocalModsTask'>) started.
WARNING:MainThread:progress.add_task: Added an empty task of type "LoadLocalModsTask". Ignoring it!
DEBUG:MainThread:windows._forget_task: Task "Loading installed mods..." (4806508760) finished.
DEBUG:MainThread:windows.watch_task: Task "Fetching mod list..." (4806508904, <class 'knossos.tasks.FetchTask'>) started.
INFO:MainThread:web.searchRetailData: No SteamPath detected!
DEBUG:Thread-1:connectionpool._make_request: https://dev.tproxy.de:443 "GET /knossos/stable/version?me=0.7.1 HTTP/1.1" 200 5
DEBUG:MainThread:windows._forget_task: Task "Checking for updates..." (4805491160) finished.
DEBUG:Thread-4:connectionpool._new_conn: Starting new HTTPS connection (1): fsnebula.org
DEBUG:Thread-4:connectionpool._make_request: https://fsnebula.org:443 "GET /storage/repo.json HTTP/1.1" 200 None
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20171212 (FSO)> is empty, ignoring it!
DEBUG:MainThread:windows._forget_task: Task "Fetching mod list..." (4806508904) finished.
DEBUG:MainThread:windows.watch_task: Task "Loading installed mods..." (4845047096, <class 'knossos.tasks.LoadLocalModsTask'>) started.
DEBUG:MainThread:windows._forget_task: Task "Loading installed mods..." (4845047096) finished.

Next I attempted to re-install the SCP build again.  The output of that mentions not being able to find the 7z.dll file in the Knossos build.  Which makes sense, Macs don't use DLLs.  The relevant chunks of the log are below, I skipped what looked like a lot of redundant and unnecessary messages for this purpose:

Code: [Select]
DEBUG:MainThread:windows.watch_task: Task "Installing mods..." (4848932760, <class 'knossos.tasks.InstallTask'>) started.
DEBUG:Thread-3:progress._next_step: Entering step 1 of 4 in task InstallTask.
DEBUG:Thread-3:tasks.work1: Folder <Mod "FSO" 3.8.0-2 (FSO)> for /Users/cliff.gordon/Knossos/bin/FSO-3.8.0-2 does not yet exist.
DEBUG:MainThread:windows.watch_task: Task "Uninstalling mods..." (4848932904, <class 'knossos.tasks.UninstallTask'>) started.
DEBUG:Thread-2:progress._next_step: Entering step 1 of 2 in task UninstallTask.
DEBUG:Thread-2:progress._next_step: Entering step 2 of 2 in task UninstallTask.
DEBUG:Thread-3:tasks.work1: OS X (Universal): ./README-SDL.txt is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
DEBUG:Thread-3:tasks.work1: OS X (Universal): fs2_open_3_8_0_x64-FASTDBG.app/Contents/Info.plist is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
...
DEBUG:Thread-3:tasks.work1: OS X (Universal): fs2_open_3_8_0_x64-FASTDBG.app/Contents/PkgInfo is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
DEBUG:Thread-2:progress._next_step: Entering step 3 of 2 in task UninstallTask.
DEBUG:Thread-3:tasks.work1: OS X (Universal): fs2_open_3_8_0_x64-FASTDBG.app/Contents/MacOS/fs2_open_3_8_0_x64-FASTDBG is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
DEBUG:Thread-3:tasks.work1: OS X (Universal): fs2_open_3_8_0_x64-FASTDBG.app/Contents/Frameworks/libswresample.2.1.100.dylib is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
DEBUG:Thread-3:tasks.work1: OS X (Universal): fs2_open_3_8_0_x64-FASTDBG.app/Contents/Frameworks/SDL2.framework/Versions/A/Headers/SDL_mouse.h is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
DEBUG:MainThread:windows.watch_task: Task "Loading installed mods..." (4845047240, <class 'knossos.tasks.LoadLocalModsTask'>) started.
DEBUG:MainThread:windows._forget_task: Task "Uninstalling mods..." (4848932904) finished.
DEBUG:Thread-3:tasks.work1: OS X (Universal): fs2_open_3_8_0_x64-FASTDBG.app/Contents/Frameworks/SDL2.framework/Versions/A/Headers/SDL_opengl.h is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
...
DEBUG:Thread-3:tasks.work1: OS X (Universal): fs2_open_3_8_0_x64.app/Contents/Frameworks/SDL2.framework/Versions/A/Headers/SDL_system.h is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
DEBUG:MainThread:windows._forget_task: Task "Loading installed mods..." (4845047240) finished.
DEBUG:Thread-3:tasks.work1: OS X (Universal): fs2_open_3_8_0_x64.app/Contents/Frameworks/SDL2.framework/Versions/A/Headers/SDL_main.h is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
...
DEBUG:Thread-3:tasks.work1: OS X (Universal): fs2_open_3_8_0_x64.app/Contents/Resources/English.lproj/InfoPlist.strings is missing/broken for <Mod "FSO" 3.8.0-2 (FSO)>.
INFO:Thread-3:util.download: Downloading "https://fsnebula.org/storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png"...
DEBUG:Thread-3:connectionpool._make_request: https://fsnebula.org:443 "GET /storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png HTTP/1.1" 200 35713
INFO:Thread-3:util.download: Downloading "https://fsnebula.org/storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png"...
DEBUG:Thread-3:connectionpool._make_request: https://fsnebula.org:443 "GET /storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png HTTP/1.1" 200 190310
DEBUG:Thread-3:progress._next_step: Entering step 2 of 4 in task InstallTask.
INFO:Thread-3:util.download: Downloading "https://fsnebula.org/storage/d2/2d/ac5f570fdeee977185dfd24e4b59b9ccb8b3031af6db545100487568379a"...
DEBUG:Thread-3:connectionpool._make_request: https://fsnebula.org:443 "GET /storage/d2/2d/ac5f570fdeee977185dfd24e4b59b9ccb8b3031af6db545100487568379a HTTP/1.1" 200 9004957
DEBUG:Thread-3:util.gen_hash: Calculating checksum for /var/folders/17/vh61x78s41n5nfxcz09fdh1w0000gq/T/tmpkrshi1xx/OS X (Universal).7z...
DEBUG:Thread-3:tasks.work2: Extracting OS X (Universal).7z into /Users/cliff.gordon/Knossos/bin/FSO-3.8.0-2
DEBUG:Thread-3:util.call: Running ['/Applications/Knossos.app/Contents/MacOS/7z', 'x', '-o/var/folders/17/vh61x78s41n5nfxcz09fdh1w0000gq/T/tmpkrshi1xx/content', '/var/folders/17/vh61x78s41n5nfxcz09fdh1w0000gq/T/tmpkrshi1xx/OS X (Universal).7z']

7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=utf8,Utf16=on,HugeFiles=on,64 bits,8 CPUs x64)

Can't load '/Applications/Knossos.app/Contents/MacOS/7z.dll' ()


ERROR:
7-Zip cannot find the code that works with archives.
ERROR:Thread-3:tasks.work2: Failed to unpack archive "OS X (Universal).7z" for package "OS X (Universal)" (FSO)!
DEBUG:Thread-3:base.send_remote: Sending message of length 530 to https://sentry.gruenprint.de/api/9/store/
DEBUG:Thread-3:progress._next_step: Entering step 3 of 4 in task InstallTask.
DEBUG:Thread-3:progress._next_step: Entering step 4 of 4 in task InstallTask.
DEBUG:raven.AsyncWorker:connectionpool._new_conn: Starting new HTTPS connection (1): sentry.gruenprint.de
DEBUG:Thread-3:connectionpool._make_request: https://fsnebula.org:443 "GET /api/1/api/1/track/install/FSO HTTP/1.1" 404 None
ERROR:Thread-3:util.get: Failed to load "https://fsnebula.org/api/1/api/1/track/install/FSO"! (404 NOT FOUND)
DEBUG:Thread-3:base.send_remote: Sending message of length 866 to https://sentry.gruenprint.de/api/9/store/
DEBUG:Thread-3:progress._next_step: Entering step 5 of 4 in task InstallTask.
DEBUG:MainThread:windows._forget_task: Task "Installing mods..." (4848932760) finished.
DEBUG:raven.AsyncWorker:connectionpool._make_request: https://sentry.gruenprint.de:443 "POST /api/9/store/ HTTP/1.1" 200 None
DEBUG:raven.AsyncWorker:connectionpool._new_conn: Starting new HTTPS connection (1): sentry.gruenprint.de
DEBUG:raven.AsyncWorker:connectionpool._make_request: https://sentry.gruenprint.de:443 "POST /api/9/store/ HTTP/1.1" 200 None
DEBUG:MainThread:windows.watch_task: Task "Loading installed mods..." (4849164792, <class 'knossos.tasks.LoadLocalModsTask'>) started.
DEBUG:MainThread:windows._forget_task: Task "Loading installed mods..." (4849164792) finished.
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: chief1983 on December 14, 2017, 01:32:00 pm
There _is_ what appears to be a 7z library binary inside the .app, but it has no dll extension as expected.  It lives at Contents/Resources/7z and there is a symlink to it at Contents/MacOS/7z that points to ../Resources/7z.  So it appears that it is just a problem that it thinks it needs a DLL extension on the library on the Mac.
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: ngld on December 14, 2017, 01:44:13 pm
The warning is unrelated to the installation, it'll happen whenever a new mod list is loaded from fsnebula.org. If a mod is "empty", then that means it doesn't contain any packages for the current platform. Usually it only happens for nightlies and can be ignored for them. If it happens for any other mod/engine build, then something went wrong. Release builds should obviously contain builds for all platforms and other mod types shouldn't be platform specific or empty.
In this case it actually means that no macOS build is available for the 12/12 nightly. I'm not sure if the nightly script didn't submit it in the first place or if the script resubmitted that nightly without the macOS build when you ran it a second time. So... you can safely delete that corrupted file if you want to, Knossos doesn't even know about it.

There _is_ what appears to be a 7z library binary inside the .app, but it has no dll extension as expected.  It lives at Contents/Resources/7z and there is a symlink to it at Contents/MacOS/7z that points to ../Resources/7z.  So it appears that it is just a problem that it thinks it needs a DLL extension on the library on the Mac.
Does it have an .so extension? If not, then that's the binary itself. It's most likely missing the 7z.so. I'll modify the packaging script to include that file which should fix this.

The fact that the second screen of the wizard quickly disappears probably means that I (once again) broke the way Knossos updates the mod list in the UI... It should be easy to fix though. (Knossos updates the list and the UI then thinks it needs to switch tabs which then leads to it hiding the wizard because that's actually just another tab.)

Thanks a lot for the help! Now I just need to figure out what the actual library name for p7zip is (I doubt it's 7z.dll) and then I should be able to fix all of the mentioned bugs.
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: chief1983 on December 14, 2017, 01:54:44 pm
I did not see a 7z.so anywhere in the app yet.  'locate' has probably run a scan since I installed Knossos the other day and there is no 7z.so reported by the locate command yet either.

I was under the impression that the nightly script simply sends the files it was notified of by the CI platforms to Nebula.  It then downloads them and tries to generate hashes for the files.  I thought this because I thought the nebula release of the nightly build happened before the nightly script was fixed.  But I might be confusing that with the ones that happened when it was the forum post process that had broken.  So perhaps when the download was corrupted, that delayed the Nebula push as well, and it was only when that was fixed, and the Mac build had been omitted that it was pushed to Nebula sans the Mac build.  Come to think of it, I don't remember a duplicate tag error in the nightly script this last time, compared to earlier this week when the forum post had failed due to some sort of transient error.
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: ngld on December 14, 2017, 02:08:47 pm
The build is only submitted after the hashes have been generated since Knossos requires those. Maybe it didn't submit the build since it failed to extract the corrupted archive?
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: chief1983 on December 14, 2017, 02:21:00 pm
Yes, it was crashing during extraction so that makes sense, in this last case it never got to the point of submitting builds to Knossos until the corrupted build was removed from the directory.  So that all adds up now.  I assume  that with the patch, a corrupted build won't crash now but I doubt it will get submitted to Knossos now either.  Can Knossos be modified to go back to the last nightly with a successful build for a given platform?
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: ngld on December 14, 2017, 02:29:54 pm
Knossos already picks the latest available build for the platform it's running on (as the log warning says, it's ignoring the 12/12 nightly). If you want it to try to install older versions if an installation fails then that's going to be complicated since we need to check if the installation was triggered by a dependency (in which case we can't do that) or if it was triggered by a user. Even then I'd try to avoid that since you probably don't want 3.7.4 if you're telling Knossos to install 3.8.0. Finally, adding a special case for nightlies doesn't seem like the best solution either.
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: chief1983 on December 14, 2017, 02:32:36 pm
Ah ok I didn't think it was trying to go to an earlier nightly, gotcha.  And nah, I don't think going back to earlier release versions makes much sense.
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: xenocartographer on December 15, 2017, 11:51:41 am
After a recent update, Knossos fails to launch with a Qt error:

"The application was unable to start correctly (0xc0000142). Click OK to close the application."
Title: Re: PUBLIC BETA: Knossos 0.7.2 (combined launcher/installer)
Post by: chief1983 on December 15, 2017, 12:05:48 pm
Yup that is being addressed at this moment.  Hopefully a 0.7.3 will be out shortly to fix that.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: ngld on December 15, 2017, 04:56:52 pm
0.7.4 has been released (0.7.3 was skipped due to problems with the new CI setup).

This version fixes the reported problems on Windows 7 and macOS. From now on releases for Windows, macOS, Ubuntu and Arch Linux will be built automatically which (hopefully) means that I'll be able to make new releases more frequently.

The Windows problem was that the bundled MSVCRT DLLs were incompatible with Windows 7 and I didn't notice because they aren't used on Windows 10. The macOS build was missing a required file for 7z which caused mod installations to fail because Knossos couldn't extract the downloaded archives. Finally, there was a problem which caused the first run wizard to be hidden after the first page.
There've been a lot of other fixes in 0.7.2 which are listed over on GitHub (https://github.com/ngld/knossos/releases).
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: chief1983 on December 18, 2017, 02:29:41 pm
Things are looking much better on the Mac.  No -psn_* crash, and the wizard doesn't disappear.  Although, I think it should at some point.  When I get to Suit Up, Pilot!, and log in as a mod developer, it pops up a Login Successful dialog box, and then I hit OK, and nothing changes.  Should a successful login be treated the same as clicking 'Finish'?  Or should it remove the central section of that page so you can't try to log in again?  I'm not getting any cues that logging in actually did anything is all.

Also, with all the various remote operations related to the account on that page (login, register, reset pass), some sort of spinner or graying of the screen while there are background tasks underway might be helpful, if high latency was ever encountered it could lead to confusion on the user's part as to whether they even clicked the button or not.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Satellight on December 18, 2017, 04:09:59 pm
A big THANK YOU for resolving the joystick problem  :yes: :yes: :yes:

Now, back to seat ! Soooo much campaigns to play  :pimp:
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: OverDhill on December 18, 2017, 10:16:22 pm
I have pointed it to the GOG installer EXE but do I need to install the actual game itself after that? I don't have the GOG version installed anymore.  If it doesn't really need to be installed and pointing to the GOG installer EXE is enough then should the HOME screen have the Retail FS2 button listed?

Downloaded the Media files and FSO and FSPort and they all downloaded 100%.  On the HOME screen there are no images for either MediaVP icons.

It seems that the TrackIR file is not installed (scptrackir64.dll). I copied the file to the FS2 folder and it now works.

Where are custom MOD's added and is there any chance we can get a new cockpit mod made that works with Knossos?
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: ngld on December 19, 2017, 10:30:23 am
@chief: I'll replace the Nebula login screen once the Nebula's website is done. The login/register/password reset UI will be part of the Nebula website and Knossos will probably just display it as an iframe or something like that. That'll allow me to change the login process later on without having to update Knossos.

@OverDhill: Did Knossos display any errors? You don't need to have FS2 installed, just pointing Knossos to the GOG installer is enough, although it can detect GOG and Steam installations if you have them.
Do you see anything listed on the Home tab? If the retail install worked, both FSO and Retail FS2 should be listed.

I just looked through the error reports I got. I assume you selected "K:\Games\Freespace 2" as your data directory.
In that case, the retail installation failed because another program (most likely your AV) interfered and deleted a required exe file (innoextract.exe). The FSPort Mission Upgrade Pack installation failed because Knossos got a permission denied error (it wasn't allowed to write to the target directory). If that's true, it should've displayed an error message...

The cockpit mod isn't currently supported although I do plan adding support for mods which extend other mods later on. The idea is that you can select any mod you have installed and tell Knossos that you want to run an extension (like the Cockpit Mod) with that other mod. It's fairly low on my todo list since AFAICT demand for other things like tags or private mods is much higher.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: OverDhill on December 19, 2017, 12:41:13 pm
Here is the Home screen and you can see that the images for the MediaVP's are missing (I did a file verify on each also).

The next question:

Should the FSO Settings have any default settings after the install? I just installed Destiny of Peace and like all the other installs I did they are all blank as shown below.

Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: ngld on December 19, 2017, 02:09:14 pm
The FSO Settings problem is a UI bug which I discovered yesterday. That'll be fixed in the next version.
The missing images are related to the fact that the mod installation failed. Since verifying the files didn't throw an error I'll have to make sure that isn't broken either. Can you go to the explore tab, click on modify for the MVPS and screenshot the window?
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: OverDhill on December 19, 2017, 05:39:30 pm
Here they are
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: ngld on December 19, 2017, 06:14:56 pm
Do the mods work properly? If they do then Knossos only failed to save the tile image. I'll make the download logic for that more reliable and have Knossos retry the download if it fails. Hopefully that'll resolve the issue.
All the packages are marked as installed and if verifying the files didn't complain, then the actual mod files should be fine.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: OverDhill on December 20, 2017, 09:26:24 am
Fs2 seems to be working fine. The image files have zero bytes. It seems that the verify files do not include those files.

Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: OverDhill on December 20, 2017, 09:31:41 am
I told it to download Cardinal Spear then walked away. I checked this morning and got an error message. It would not even try to verify the files. So I told it to uninstall and then will try to re-install it.


Update: Second attempt was successful.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: ngld on December 20, 2017, 10:58:44 am
If you go to the Explore tab and click Modify > OK for each mod with broken tile images, does that fix them?

The last screenshot shows that it did verify the files and found that some were either missing or corrupted which is why it told you to reinstall them.
That installation problem might've been the result of me changing the download links. Downloads should now go through CloudFlare which seems to increase the download speed for some people.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: OverDhill on December 20, 2017, 12:40:50 pm
I have tried the Modify with no luck. The weird part is that the tiles show up in the Development screen but not on the Home screen.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Novachen on December 22, 2017, 08:44:06 pm
Mhh.. well, i think that i am doing something wrong with this program...  :sigh:

First, i was not able to use the full install of my FSPort translation modification, because one of the included VP was write-protected by accident (no idea why this one was write-protected in the first place...). Got an error message about an incomplete installation.

So i tried to fix this with a new version... and now i am not able to test this, because i get once again the "FSO is missing" error, i mentioned previously. Because it tries to use a version that is impossible to exist.

Quote
knossos.repo.PackageNotFound: No version of mod "FSO" found for these constraints: >=3.8.1-20171221 (FSO),==3.8.0-2 (FSO),>=3.8.0-2 (FSO)

I do not know why this happened again...
And yes, i have selected the 20171221 nightly build in the mod settings in the development tab if this one matters.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Asteroth on December 23, 2017, 01:59:41 pm
So I didn't really know a lot about Knossos, aside from that it's a combined launcher and installer. So allow me to walk you through my thought process as a completely new user.

When I started to install it and it asked me where to put it I did the intuitive thing I've done with literally every other mod or freespace-related tool I've ever gotten and tried to put it in my Freespace folder, but of course it said don't do that! ...Ook? Well, I guess I'll just put it in Program Files, but that's kind of confusing, why won't it let me keep all my Freespace stuff together? Whatever. So it otherwise installed nicely, but when it finished it said I had no mods! What? I have dozens of them! It know where my Freespace directory is, why isn't it detecting them? So as a test I downloaded BP. Which worked and played fine, but I saw that it had installed it to the Knossos folder. OK, so it keeps mods in Knossos, and retail FS2 in Freespace? Wait, no FS2 is in here too, along with copies of the builds I have. Does it just copy everything? Mods take up a lot of space, can I just move all my old mods into the Knossos folder?

And that's about where I am, now. Don't get me wrong, I'm sure there's great reasons to have all this stuff this way, technically I'm sure it's more rigorous and bug-free or whatever. But, I think some more should be done to explain the structure of how Knossos works, especially if you have a big existing install with a bunch of mods 'the old way' and you want to transition. The old way is comforting and I understand it well, but Knossos has done a bunch of weird things I didn't expect and it didn't explain well, so I get turned off of it.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: mjn.mixael on December 23, 2017, 02:10:01 pm
Knossos was built with new non-legacy FS players in mind. Turns out it confuses the hell out of people who've been playing/modding freespace for years.

There are reasons it does what it does and I'll leave that to ngld to explain. Basically, the short version is that Knossos is a fresh start. I can work with your previous mods, but it's not meant to.. and there's some work involved in getting that done. I would encourage people to not copy mods that exist in Knossos and just have Knossos reinstall them. Other mods that don't exist in Knossos? Get them uploaded into it!

Knossos is designed to manage all your FSO things, including TCs, without you having to mess with the files ever. (Unless you're modding, of course.) Want to play Wings of Dawn? We got you covered. One sec, while we install. Then just press play. Want to play ST:R with it's web of dependencies? We can do that, too. Just press Play when we're done getting it ready.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Asteroth on December 23, 2017, 02:41:16 pm
That was definitely the impression I got, and again I'm glad you guys are doing it. The only question I have left, is that I am modding, creating a new mod, that is. I've already noticed some differences with the way mods are handled, most notably with mod.json, and at least based on a cursory look through BP's mod.json, its quite a bit more complicated than mod.ini. Is there a particular spot where I can see what Knossos expects to find/needs in mod.json?
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: chief1983 on December 23, 2017, 02:49:21 pm
I'm glad you were willing to give it a stab, and hopefully from the early version number you understood that it wasn't expected to be completely polished yet.  I think by 1.0 a lot of what you're talking about will be ironed out, but feedback from early adopters such as yourself will be helpful in figuring out how to help other newcomers make the transition, those who waited until an official stable release, etc.  There may be need to have some included help system for those with large existing installations desiring to migrate to the Knossos platform, but right now it is backseat to focusing on the new paradigm of a pure ecosystem management platform catered toward newcomers.  Someone else should be able to help with your mod.json question, I can't recall if it is designed to be manually edited or if Knossos is supposed to already manage it for you.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: m!m on December 23, 2017, 02:54:16 pm
I'm pretty sure that the mod.json system is not meant to be edited manually. If you switch to the Development tab on Knossos you can create your own mod and develop it with full Knossos support without having to edit your mod.json manually. I think there is a tutorial on how to use that interface somewhere but I'm not sure if that is finished yet.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Asteroth on December 23, 2017, 03:44:26 pm
Ah, yes, I had assumed that was for uploading a completed project so that others could access it. I guess its to compile a mod for knossos locally and then you can upload it later?
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: mjn.mixael on December 23, 2017, 04:32:10 pm
I have already switched to using Knossos as my dev launcher. Create a mod with the Dev tab.. put your files in there and you're good to go. When you're ready to release, click upload!
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: ngld on December 27, 2017, 10:13:21 am
I'm back after the christmas holidays and it looks like I missed a few posts. Let's see...

@Novachen: That shouldn't happen with the latest version (0.7.4), can you upload your mod.json so I can take a look at it?

@Asteroth: The idea is that you can create/edit/upload and delete your mod through the dev tab. It should allow you to do everything without learning how the mod.json stuff works. The dev tab already has a lot of help texts which hopefully explain the various fields and how packages work. If anything there is still unclear or missing, feel free to tell me so I can fix that!
I'm not sure how to handle the initial introductions for HLP veterans. It should be clear enough for new people but I guess we'll need a migration guide for everyone else. Maybe we can integrate that into Knossos but I currently have no idea how to do that.

The most confusing thing about Knossos is probably the directory structure which is designed to make managing multiple versions of mods and TCs side-by-side easier. The most important part is that Knossos can automatically manage it (which simply wasn't possible with the old structure everyone used in the past).
Importing mods has been requested several times but so far we haven't figured out a sane way to make that possible. The core problem is that there is no way for Knossos to detect which mod and version the existing files belong to while also making sure that the files haven't been modified and nothing is missing.
As mentioned before, this only matters if you develop mods and in that case you should be using the dev tab which explains at least part of it.

@chief: Axem was working on a tutorial for Knossos but I think he stopped because we keep changing Knossos.   :lol:


Just as a heads up: There's a bug which might cause trouble if you try to update an installed mod which will be fixed by 0.7.5. I should be able to release that before the end of the year.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: jr2 on December 27, 2017, 04:45:35 pm
Perhaps put a quick FAQ section for previous users, and have Knossos ask if the user has used FSO before.  If they answer yes, it will then ask them to please check out that FAQ section for their own sanity (explicitly state that some fundamentals have changed).
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: ngld on December 27, 2017, 04:58:05 pm
Sounds like a good idea. I'm currently working on a proper website for fsnebula.org and I'll probably include the FAQ in that. At the end of the first run wizard I could add something like:
"If you've used FSO before, you should read this short FAQ to learn about a few important differences between other launchers like wxLauncher and Knossos." with a link to the FAQ on fsnebula.org
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Novachen on December 28, 2017, 06:16:25 am
@Novachen: That shouldn't happen with the latest version (0.7.4), can you upload your mod.json so I can take a look at it?

I completely recreated my mods in the meantime from scratch. If i select the 3.8.0-2 build in the development tab it seems to work. Interestingly i always get an error message if i want to play it, after i save the command line with a selected nightly build in the development tab. But when 3.8.0 is selected in the mod.json  i can play it even with the latest nightly.

So i get rid of this error at the moment as it seems.


But another topic, actually i would like have the possibility to setup a proper loading preference of invidual packages of a modification. For example, i have included the extended ancients 4 cutscene (Ancients 4 monologue + Lucy attack Vasuda Prime) as an optional downloadable package in my FSPort translation... but this cutscene only works if i create the package BEFORE the package that includes all the other movie files. If i create the Addon after the main video package... only the shorter video of the main package is used. Actually it seems, that Knossos loads the packages in reverse order as they are created... so the last one is loaded first and all files will be overwritten by packages that were created before.
That does not make much sense IMO.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: ngld on December 28, 2017, 04:07:23 pm
I'll keep looking into the executable error.

The second problem only affects mods in dev mode but I think it should be fairly easy to fix. Knossos doesn't reverse the order anywhere. It seems this way due to how FSO works: It goes through the list passed to -mod and uses the first file it finds. As a result, all files in earlier packages "overwrite" files in later packages.
I plan to sort the packages by folder name. I'll also change the name of the generated .vp files to be based on the folder name instead of the package name. This should make load order and precedence consistent between dev mode and normal mode.
This won't make the load order more logical but more consistent with already established FSO behaviour. This way you could name the folder for the cutscenes "5_cutscenes" and the folder for the extended ancients cutscene "4_ancient_cutscene".
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Cyborg17 on December 30, 2017, 10:04:41 am
Just thought I would let you know that I figured out what was wrong on my end.  It turns out the download from gog I had was incomplete, but my connection sucks, so my computer thought it was a valid download.  I downloaded it on another connection, and no problem installing with innoextract.

Using the other installer, however, innoextract downloaded, and then was failing.  My guess from the log is that it was trying to read the temporary location of innoextract.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Eratharon on January 03, 2018, 03:20:31 pm
Hello! I just returned to FSO to play Retail, JAD, Derelict and Wings of Dawn (the original) a little and decided to try out Knossos (awesome work) but I have 2 questions. First my HUD is all messed up. The windows overlap each other and are really big (my res is 1366x768) but that was never a problem before. Is there a way to resize them? Second I'd like to know if you can add mods not on the Explore tab like the original Wings of Dawn which I would like to play. Thanks in advance!
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: ngld on January 03, 2018, 03:59:57 pm
First of all thanks for testing Knossos! I haven't heard of that HUD issue before. Could you please post a debug log? (Open the dropdown on the mod that causes the problem, then click on "Run Fast Debug". FSO should now start. Enter a mission, exit and back in Knossos open the dropdown again and click "Upload Debug Log". Finally post the link Knossos gives you.)

Everyone can add new mods, that's what the Dev tab is for. However, I think Spoon intentionally removed all download links for old WoD. Unless I'm wrong about that and you can point me to a download link for it, I can't add it.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Spoon on January 03, 2018, 07:53:34 pm
First of all thanks for testing Knossos! I haven't heard of that HUD issue before. Could you please post a debug log? (Open the dropdown on the mod that causes the problem, then click on "Run Fast Debug". FSO should now start. Enter a mission, exit and back in Knossos open the dropdown again and click "Upload Debug Log". Finally post the link Knossos gives you.)

Everyone can add new mods, that's what the Dev tab is for. However, I think Spoon intentionally removed all download links for old WoD. Unless I'm wrong about that and you can point me to a download link for it, I can't add it.
There are still working links here: https://www.hard-light.net/forums/index.php?topic=71092.0 but I'd rather not have old WoD on Knossos
Old WoD was made for 3.6.12 which are kind of ancient builds by today's standards, I'm not even sure it runs on new builds... I'm going to assume there's going to be a lot of errors when you try.

Hello! I just returned to FSO to play Retail, JAD, Derelict and Wings of Dawn (the original) a little and decided to try out Knossos (awesome work) but I have 2 questions. First my HUD is all messed up. The windows overlap each other and are really big (my res is 1366x768) but that was never a problem before. Is there a way to resize them? Second I'd like to know if you can add mods not on the Explore tab like the original Wings of Dawn which I would like to play. Thanks in advance!
Is the hud issue, something that happens with every mod you try and play on Knossos? Can you rule out if it's related to just using new builds
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Eratharon on January 04, 2018, 12:29:52 am
Okay, thanks for replying. Spoon had the right idea in that I tryed Derelict, the Retail campaign with MediaVPs and FSport also with MediaVPs and the HUD was ok in them. I am going to work soon and after getting home I will try other mods also. So the problem at the moment seems to only show up in JAD being overly large and overlapping. Here's the link to the log and while loading the mission it wrote out some errors for me that it did not in the non-debug build:

https://fsnebula.org/log/5a4dc771cb8db11ef566acd1

Quote
There are still working links here: https://www.hard-light.net/forums/index.php?topic=71092.0 but I'd rather not have old WoD on Knossos
Old WoD was made for 3.6.12 which are kind of ancient builds by today's standards, I'm not even sure it runs on new builds... I'm going to assume there's going to be a lot of errors when you try.
I am very sad to hear that cause it's one of my favourite campaigns in existence along with the other classics. :(
Hm, maybe I can scrounge up ye olde MediaVPs for it from somewhere on the forums.
Title: Re: PUBLIC BETA: Knossos 0.7.4 (combined launcher/installer)
Post by: Eratharon on January 04, 2018, 03:22:10 pm
Oh, aside from the previous I have another question! Does Knossos have a Global FSO settings (maybe I'm blind as a bat) or do I have to turn on different options for each mod?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 04, 2018, 03:43:00 pm
I'm not sure what's causing the bug. You don't seem to be missing any file and I don't see any obvious issue with the flags passed to FSO. I'll keep looking though.

Global FSO settings are planned but haven't been finished, yet. Unfortunately, you have to set the options for each mod for now.

In other news 0.7.8 has been released. I haven't announced the versions between 0.7.4 and 0.7.8 because there were a few embarrassing bugs.  :nervous:
Since the last release, mod updates have been fixed (they no longer abort during the "Copying old files" step), downloads for macOS users have been fixed and debug information has been improved which should help me catch more bugs.
A few smaller issues and UI bugs have been fixed as well. See the commits (https://github.com/ngld/knossos/compare/v0.7.4...v0.7.8) for the full details.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Eratharon on January 05, 2018, 02:32:08 am
Quote
I'm not sure what's causing the bug. You don't seem to be missing any file and I don't see any obvious issue with the flags passed to FSO. I'll keep looking though.

Thank you your help but I think you can leave it as is. I tried the other JAD 2.21 and 2.22 where HUD layout is the same but it when I play those two campaigns the HUD is the right size and not too big. On other mods there aren't any problems either. This only occurs on JAD original and it gets some getting used to but other than that it's perfectly playable. If there is a way to resize it please let me know but other than that I will just chalk it up on my computer either trolling me or having momentary insanity.

BTW how can you make FSO screenshots? When I printscreen and paste it on paint it's always completely black.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Spoon on January 05, 2018, 05:36:35 am
BTW how can you make FSO screenshots? When I printscreen and paste it on paint it's always completely black.
There's a screenshots folder in where you installed Freespace, with older builds they're saved as .tga, with newer builds they'll be .png
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: m!m on January 05, 2018, 05:38:38 am
Since 3.8 FSO saves the screenshots in the same %AppData% folder the log gets written to and not the FreeSpace installation directory. Knossos actually has a button for opening the correct folder automatically. It's the small picture icon in the top right corner.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Eratharon on January 05, 2018, 05:53:04 am
Just 2b clear I attached a screenshot of how the HUD is. Keep up the good work and thanks for all the help.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Novachen on January 05, 2018, 07:39:35 am
Looks like Axems 2_ HUD modification that is intended for use in higher resolutions.

So i think that JAD use this modification by default... you are using a resolution that is too low for that unfortunately.

The only Knossos compatible solution seems to be the use of Downsampling technologies... so to speak Dynamic Super Resolution in nVidia or Custom Resolution (or how is it called) in AMD.
With that you can select and play Resolutions like 1920x1080 on your monitor.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Spoon on January 05, 2018, 08:13:05 am
Since 3.8 FSO saves the screenshots in the same %AppData% folder the log gets written to and not the FreeSpace installation directory. Knossos actually has a button for opening the correct folder automatically. It's the small picture icon in the top right corner.
  :confused:
When I hit printscreen on any of the new builds, it just saves the screenshot in the Freespace2\Screenshots folder, like it always has. Thankfully. Because I wouldn't appreciate it at all if it for some random reason it would suddenly start saving the screenshots in bloody AppData of all places. Or am I misunderstanding you in someway? Actually hitting the screenshot button in knossos says the folder doesn't exist. Is this just a Knossos thing?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 05, 2018, 08:17:00 am
It's a change introduced in 3.8.0 and isn't influenced by which launcher you use. However, FSO will still use the old path if the new folder doesn't exist or if you're using the portable mode.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Spoon on January 05, 2018, 08:23:14 am
Okay but, I don't want it to use the new path, ever. Screenshots&logs saved somewhere deep on my C: drive is really inconvenient imho, this is one of those changes I wish would get discussed rather than just implemented. Can Knossos' screenshot button be configured to take any other path instead?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Spoon on January 05, 2018, 08:25:59 am
(P.s. I know I've said this before, but it cannot be overstated, Knossos is really nice, neat and cool)
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 05, 2018, 08:43:04 am
I could make it configurable but that would be rather pointless since the path is hardcoded in FSO. The fact that FSO still uses the old path for you most likely means that it also ignores the settings and flags Knossos tries to pass to FSO since they're all in AppData. I could implement support for FSO's portable mode but I think that's still marked as experimental...
Could you run a debug build and check where the debug log is written?

(P.s. I know I've said this before, but it cannot be overstated, Knossos is really nice, neat and cool)
Thanks a lot! :)

Hopefully, I'll be able to implement global FSO settings (instead of mod-specific) soon. There's still a lot of other stuff left to work on but I think that's one of the few things that's stopping people from using it as a default launcher.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: pim on January 06, 2018, 07:51:00 am
Hi ngld. I like your approach. Really hassle free, easy to use design. I tried hard to find something to nitpick about but failed miserably:-).
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: chief1983 on January 06, 2018, 10:56:58 am
For some reason I can't find the knossos config folder anymore, it doesn't seem to be at ~/.knossos on my Macs now.  I blew away the data folder, which did remove its knowledge of my mods, but it did not re-run the first launch wizard to find FSO.  Ok, I did manage to find that under Settings -> Install Retail or whatever it was called.  But given that I ran it manually, the dialog did not make much sense as it said I was trying to install a mod that required FS2 retail data (I was just trying to install FS2 retail data though so that text is confusing I think).  Also, after selecting the folder to copy the data from and hitting continue, the dialog closed but nothing else happened.  No "copy complete", etc, and the button didn't disappear until I reloaded the settings page after checking the Home page to see Retail FS2 had indeed appeared.  So, everything worked well enough, but the process was a little confusing.  And where _is_ that config folder/file now if I want to reset this thing completely?  I could have sworn I'd found it once before but it seems like it moved on me. :P

Also should mention, the reason I blew away the data directory is that the SCP mod had been installed in a broken state while SSL was broken, and after updating Knossos and checking file integrity, it did download files, but the mod metadata still seemed messed up, the images in both Home and Explore were still broken.  Blowing away the data directory and starting it over seemed to be the only way to fix it.  Probably a really edge case thing, but I thought you might want to know that the file integrity check didn't seem to 100% fix a broken mod install at the moment.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Satellight on January 07, 2018, 09:16:34 am
Hello ! Just got an error while playing Burning Heaven, during a mission (don't remember which one : it's the one I have to "dive ! dive ! dive !" while crossing the path of an Hecate destroyer).

My log is uploaded here :

https://fsnebula.org/log/5a52313ecb8db13e6821cc94

Seems to have corrupted my player file  :blah: It's related to a radar problem ? ("Player file has invalid radar range -1")

If I delete the current player file in the appdata/roaming folder, I can play normally again. If not, the error appear in every mod I launch.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: mjn.mixael on January 07, 2018, 09:19:11 am
Satellight, that sounds like a mod/FSO issue and not related to Knossos. Might want to post the same thing in the FSO Support forum.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Satellight on January 07, 2018, 09:24:19 am
Satellight, that sounds like a mod/FSO issue and not related to Knossos. Might want to post the same thing in the FSO Support forum.

Hi ! You're right, I'm doing it now. I was confused while testing  :lol:
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 08, 2018, 01:44:46 pm
@pim: Thanks for the great review. :lol:

@chief: The settings should be stored in ~/Library/Preferences/knossos on macOS. The retail install dialog is still the same one we used before the new first run assistant and the "Install Retail" button was a quick solution. I need to rewrite that dialog but as so many other things, it wasn't as important as the other stuff I'm currently working on.  ;)
The file validation only covers the mod's own files so it wouldn't detect corrupted screenshots, banners, etc.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: OverDhill on January 08, 2018, 11:25:52 pm
I am curious as to why Knossos Blue Planet Complete download is quite a bit smaller than the Freespace Open Installer files.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 08, 2018, 11:38:34 pm
It shouldn't be. I just checked and the archives the installer downloads seem to be as big as the download size Knossos lists. What sizes do you see?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: OverDhill on January 09, 2018, 12:06:33 am
Maybe there are some old files in my install. I have a bpc-advanced1.vp, bpc-advanced21.vp and bpc-advanced3.vp files that are quite large. Do they now belong anymore?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: mjn.mixael on January 09, 2018, 12:55:34 am
It's the BP team, themselves, that put BP Complete on Knossos. Presumably, it would be the most up-to-date and complete option, regardless of whatever anyone downloaded before from anywhere.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: OverDhill on January 09, 2018, 01:49:33 pm
It's the BP team, themselves, that put BP Complete on Knossos. Presumably, it would be the most up-to-date and complete option, regardless of whatever anyone downloaded before from anywhere.

They are the optional high-resolution textures that and are not downloaded by the newest Freespace 2 Installer or the Knossos installer from what I have tested.  I have posted in the Blue Planet forum about asking if it was an oversight or these are not used anymore.

Looking forward to seeing The Babylon Project being added to Knossos
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: OverDhill on January 09, 2018, 02:14:13 pm
I have been using Reshade/SweetFX on Freespace 2 Open using the wxLauncher with success. It does add to the graphics IMO.  With the way the folder structure is for Knossos I have not had much success getting it to work.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 09, 2018, 05:34:01 pm
Where did you put the .dll files? You could try these locations: <basefolder>\bin\FSO-3.8.0-2, <basefolder>\FS2 and C:\Program Files (x86)\Knossos (or wherever you've installed it). The base folder is the folder you selected during the first run and defaults to C:\Games\FreespaceOpen. If you use a different FSO version, then you might need to copy your .dlls into the other subfolders in bin as well.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: jr2 on January 09, 2018, 05:42:57 pm
Where did you put the .dll files? You could try these locations: <basefolder>\bin\FSO-3.8.0-2, <basefolder>\FS2 and C:\Program Files (x86)\Knossos (or wherever you've installed it). The base folder is the folder you selected during the first run and defaults to C:\Games\FreespaceOpen. If you use a different FSO version, then you might need to copy your .dlls into the other subfolders in bin as well.

Would it be easily possible to add ReShade/SweetFX support to Knossos?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 09, 2018, 05:57:36 pm
It should be fairly simple but I'm not certain if what I have in mind would work or not.

My solution would be the following: I create a new empty folder called addon_dlls (or something like that) in Knossos' directory. Whenever Knossos launches FSO, it'll put that folder as the first item in the PATH. This should cause Windows to find the ReShade DLLs and load them instead of the stock DirectX DLLs. (ReShade provides a wrapper around the real DirectX DLLs which is how it hooks into games).
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: jr2 on January 09, 2018, 11:12:22 pm
It should be fairly simple but I'm not certain if what I have in mind would work or not.

My solution would be the following: I create a new empty folder called addon_dlls (or something like that) in Knossos' directory. Whenever Knossos launches FSO, it'll put that folder as the first item in the PATH. This should cause Windows to find the ReShade DLLs and load them instead of the stock DirectX DLLs. (ReShade provides a wrapper around the real DirectX DLLs which is how it hooks into games).

Wat.  FSO uses OpenGL, not DirectX.  DX was canned a long time ago.  Am I missing something?  How are people using ReS/SFX then?  Or do they also have an OGL wrapper?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: OverDhill on January 10, 2018, 12:15:23 am
These are the files I have been using for Freespace 2 Open for awhile now. They were used for IL-2 1946 OpenGL as well.

https://www.dropbox.com/s/vyvs05h4z9letip/ReShade-SweetFX_2.0-FS2.zip?dl=0

Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 10, 2018, 12:38:39 am
@jr2: Sorry, I always used ReShade with DirectX games which is why I immediately thought of that. ReShade also has an OGL wrapper which works the same way.

@OverDhill: Thanks, I'll see if I can get that to run with Knossos.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: jr2 on January 10, 2018, 12:57:21 am
@ngld: might want to check the newest version (3.1.0) as well, can't hurt to poke at it:  https://reshade.me/

EDIT: Oh, hey!  ReShade is Open Source now, didn't know that!
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Firesteel on January 10, 2018, 10:02:12 pm
Couple things that have been on my mind for a while regarding Knossos (that I'm sure are buried somewhere).

First is regarding the command line arguments/settings. (Aside from not working from what I can tell) are they intended to be implemented on a per mod basis? Like if I have different arguments on FSPort, FSPort MediaVPs, MediaVPs, and ST:R, which would be used?

Second are there any plans in the future to allow updating dependencies through the GUI? For example letting people hook up Homesick to the 2014 mediaVPs? The ini files were fairly easy to do that for compared to the new jsons.

Amazing progress on this project though you guys!
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 10, 2018, 10:11:58 pm
The command line flags should be working. The way it currently works is that Knossos saves the enabled flags for each mod and uses them whenever you start that mod. This means that the dependencies can't influence the flags at all (that'd make this waaay too complex to handle).
You can see (and edit) the currently enabled flags by going to your Home tab, clicking on the little arrow on any of your installed mods and clicking on "FSO Settings".
I'm currently working on implementing global flags which will allow you to set the flags on your settings screen for all mods while still allowing you to set mod-specific command lines.

The question about modifying mods has been brought up before on Discord and I plan to add an option which will allow you to switch a mod into dev mode. That will cause it to show up on your dev tab where you can change everything related to the mod including dependencies.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Firesteel on January 10, 2018, 10:29:55 pm
Awesome thanks!

I don't know how the command line stuff works under the hood, but would there be a way to do a global one similar to wxLauncher that could then be overriden on a per mod basis?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 11, 2018, 12:08:56 am
I'm currently working on implementing global flags which will allow you to set the flags on your settings screen for all mods while still allowing you to set mod-specific command lines.

Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: PIe on January 11, 2018, 12:08:27 pm
Second are there any plans in the future to allow updating dependencies through the GUI? For example letting people hook up Homesick to the 2014 mediaVPs? The ini files were fairly easy to do that for compared to the new jsons.
For the time being, the best workaround is to create a new blank mod and add Homesick and MVPs 3.7.2 (aka 2014) as dependencies.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: mjn.mixael on January 11, 2018, 12:48:38 pm
I think we covered this on Discord already.

I am very against creating a special UI for users to mod a mod by altering dependencies. If you want to do that, that's what the Dev tab is for.

Outside of user preferences (command line flags), no modding should be built into the Home or Explore tabs.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 13, 2018, 09:45:18 pm
I have good news and bad news: ReShade works fine if you copy the files into the same directory as fs2_open...exe. The bad news is that nothing else (short of injecting the DLL which I'd like to avoid) seems to work.
This means that you'll have to copy the files for every FSO version installed and every time Knossos updates FSO.
The best solution that I've been able to come up with is to copy everything from a special override_dlls folder into FSO's folder whenever Knossos launches FSO. However, if I implement that, I'll make Knossos delete the files once FSO quits to avoid leaving clutter. I'll also prevent anything in override_dlls from overwriting FSO's files (like the FFmpeg DLLs) because I couldn't reverse that without making backup copies which would make this even more complicated.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: jr2 on January 16, 2018, 01:28:08 am
I have good news and bad news: ReShade works fine if you copy the files into the same directory as fs2_open...exe. The bad news is that nothing else (short of injecting the DLL which I'd like to avoid) seems to work.
This means that you'll have to copy the files for every FSO version installed and every time Knossos updates FSO.
The best solution that I've been able to come up with is to copy everything from a special override_dlls folder into FSO's folder whenever Knossos launches FSO. However, if I implement that, I'll make Knossos delete the files once FSO quits to avoid leaving clutter. I'll also prevent anything in override_dlls from overwriting FSO's files (like the FFmpeg DLLs) because I couldn't reverse that without making backup copies which would make this even more complicated.

Is there anyone at ReShade that can work around that from their end?  Probably too busy or whatever, but you never know..
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 16, 2018, 01:39:06 am
I don't think this is something the ReShade devs can fix. For ReShade to work Windows has to load ReShade's DLL instead of the "official" OpenGL32.dll (which in most cases is in C:\Windows\System32). If you take a look at MS' documentation (https://msdn.microsoft.com/en-us/library/windows/desktop/ms682586(v=vs.85).aspx#standard_search_order_for_desktop_applications), you'll see that Windows first checks the EXE's folder and then the system directory. The result is that unless you want to inject the DLL, you'll have to place it in the EXE's directory.
You could use the current working directory or the PATH to modify this in the past, however, some malicious software abused this fact which is why it's not possible anymore.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: eisberg on January 16, 2018, 06:06:52 pm
Norton Security Suite keeps on deleting the files

Filename: knossos.exe
Threat name: Heur.AdvML.BFull Path: d:\games\knossos\knossos.exe

____________________________

____________________________


On computers as of 
1/16/2018 at 5:59:46 AM

Last Used 
1/16/2018 at 6:01:47 AM

Startup Item 
No

Launched 
No

Threat type: Heuristic Virus. Detection of a threat based on malware heuristics.


____________________________


knossos.exe Threat name: Heur.AdvML.B
Locate


Very Few Users
Fewer than 5 users in the Norton Community have used this file.

New
This file was released 10 days ago.

High
This file risk is high.


____________________________


Source: External Media

Source File:
knossos.exe

____________________________

File Actions

File: d:\games\knossos\ knossos.exe Removed
File: c:\users\ryann\appdata\roaming\knossos\ mods.json Threat Removed
File: c:\users\ryann\appdata\roaming\knossos\ settings.json Threat Removed
File: c:\users\ryann\appdata\roaming\knossos\ log.txt Threat Removed
File: c:\users\ryann\appdata\roaming\hardlightproductions\freespaceopen\data\ cmdline_fso.cfg Threat Removed
File: c:\users\ryann\appdata\roaming\hardlightproductions\freespaceopen\ fs2_open.ini Threat Removed
Directory: c:\users\ryann\appdata\local\temp\ comtypes_cache Removed
Directory: c:\users\ryann\appdata\local\temp\comtypes_cache\ knossos-36 Threat Removed
____________________________

Registry Actions

Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_0A5D\ DeviceInstances->8&8655AF1&0&0001:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1532&PID_0037\ DeviceInstances->7&2AADE4A5&0&0001:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1532&PID_0037\ DeviceInstances->7&2AADE4A5&0&0002:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1532&PID_0037\ DeviceInstances->7&2AADE4A5&0&0003:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C31C\ DeviceInstances->9&17779FC4&0&0000:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1532&PID_0037\ DeviceInstances->7&2AADE4A5&0&0004:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C31C\ DeviceInstances->9&17779FC4&0&0001:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_0A5B\ DeviceInstances->7&394501CC&0&0000:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C31C\ DeviceInstances->9&17779FC4&0&0002:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_0A5B\ DeviceInstances->7&394501CC&0&0001:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_0A5B\ DeviceInstances->7&394501CC&0&0002:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_0A5B\ DeviceInstances->7&394501CC&0&0003:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_0A5D\ DeviceInstances->8&8655AF1&0&0000:..., Registry Hive: 64 bit Repaired
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_FFFF\ DeviceInstances->2&1A4798ED&0&0000:..., Registry Hive: 64 bit Repaired
____________________________


File Thumbprint - SHA:
6820d53c5b2b0360fc6740576026e6c433eb1c93babf690e9492a05337f879 cf
File Thumbprint - MD5:
a5183c07622ebc1f071d7fd09f443f56
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Spoon on January 16, 2018, 06:10:34 pm
Avast also likes deleting the Knossos files
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: chief1983 on January 16, 2018, 06:12:06 pm
is there a voluntary method to submit to these companies the source and binary examples so they stop doing that?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 16, 2018, 07:25:12 pm
Threat type: Heuristic Virus. Detection of a threat based on malware heuristics.
Heuristic means that Norton thinks that Knossos could be a virus due to a few indicators, which are:


Very Few Users
Fewer than 5 users in the Norton Community have used this file.
Not suprising given that only some people on this forum have installed Knossos and I'm not sure how many of those even use Norton.

New
This file was released 10 days ago.
Not actually true. The file was released 12 days ago (https://github.com/ngld/knossos/releases/tag/v0.7.8) but I guess Norton saw it for the first time 10 days ago.

High
This file risk is high.
Not exactly sure why it thinks the file is risky.

File: d:\games\knossos\ knossos.exe Removed
File: c:\users\ryann\appdata\roaming\knossos\ mods.json Threat Removed
File: c:\users\ryann\appdata\roaming\knossos\ settings.json Threat Removed
File: c:\users\ryann\appdata\roaming\knossos\ log.txt Threat Removed
File: c:\users\ryann\appdata\roaming\hardlightproductions\freespaceopen\data\ cmdline_fso.cfg Threat Removed
File: c:\users\ryann\appdata\roaming\hardlightproductions\freespaceopen\ fs2_open.ini Threat Removed
Directory: c:\users\ryann\appdata\local\temp\ comtypes_cache Removed
Directory: c:\users\ryann\appdata\local\temp\comtypes_cache\ knossos-36 Threat Removed
Well, those are all harmless text files. Those aren't threats but they were created by Knossos.

Registry Actions

Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_0A5D\ DeviceInstances->8&8655AF1&0&0001:..., Registry Hive: 64 bit Repaired
[...]
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_FFFF\ DeviceInstances->2&1A4798ED&0&0000:..., Registry Hive: 64 bit Repaired
Knossos doesn't actually use these registry keys. However, it uses SDL2 which uses DirectInput.


File Thumbprint - SHA:
6820d53c5b2b0360fc6740576026e6c433eb1c93babf690e9492a05337f879 cf
Now, if you take that hash and go to VirusTotal, you get this page: https://www.virustotal.com/#/file/6820d53c5b2b0360fc6740576026e6c433eb1c93babf690e9492a05337f879cf/detection
Which will tell you that only a few (7 out of 67) AV scanners think that this file is suspicious. Hell, even Symantec (the company which owns Norton) marks the file as clean.


So... nothing I can really do about that. If possible, you should report it as a false positive and add an exception but otherwise... that's it. AVs nowadays just hate rare unknown files.
One solution would be to sign the executables because that'd prove that they came from me but... honestly? I don't see why I should verify my identity and pay a bunch of money just to have some AVs not mark my program as suspicious.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: mjn.mixael on January 16, 2018, 11:01:08 pm
Or people should stop using bloatware anti-virus like Norton....

...
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: eisberg on January 17, 2018, 12:17:42 am
Threat type: Heuristic Virus. Detection of a threat based on malware heuristics.
Heuristic means that Norton thinks that Knossos could be a virus due to a few indicators, which are:


Very Few Users
Fewer than 5 users in the Norton Community have used this file.
Not suprising given that only some people on this forum have installed Knossos and I'm not sure how many of those even use Norton.

New
This file was released 10 days ago.
Not actually true. The file was released 12 days ago (https://github.com/ngld/knossos/releases/tag/v0.7.8) but I guess Norton saw it for the first time 10 days ago.

High
This file risk is high.
Not exactly sure why it thinks the file is risky.

File: d:\games\knossos\ knossos.exe Removed
File: c:\users\ryann\appdata\roaming\knossos\ mods.json Threat Removed
File: c:\users\ryann\appdata\roaming\knossos\ settings.json Threat Removed
File: c:\users\ryann\appdata\roaming\knossos\ log.txt Threat Removed
File: c:\users\ryann\appdata\roaming\hardlightproductions\freespaceopen\data\ cmdline_fso.cfg Threat Removed
File: c:\users\ryann\appdata\roaming\hardlightproductions\freespaceopen\ fs2_open.ini Threat Removed
Directory: c:\users\ryann\appdata\local\temp\ comtypes_cache Removed
Directory: c:\users\ryann\appdata\local\temp\comtypes_cache\ knossos-36 Threat Removed
Well, those are all harmless text files. Those aren't threats but they were created by Knossos.

Registry Actions

Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_0A5D\ DeviceInstances->8&8655AF1&0&0001:..., Registry Hive: 64 bit Repaired
[...]
Registry change: HKEY_USERS\S-1-5-21-1795443936-2587830784-1468899020-1001\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_FFFF\ DeviceInstances->2&1A4798ED&0&0000:..., Registry Hive: 64 bit Repaired
Knossos doesn't actually use these registry keys. However, it uses SDL2 which uses DirectInput.


File Thumbprint - SHA:
6820d53c5b2b0360fc6740576026e6c433eb1c93babf690e9492a05337f879 cf
Now, if you take that hash and go to VirusTotal, you get this page: https://www.virustotal.com/#/file/6820d53c5b2b0360fc6740576026e6c433eb1c93babf690e9492a05337f879cf/detection
Which will tell you that only a few (7 out of 67) AV scanners think that this file is suspicious. Hell, even Symantec (the company which owns Norton) marks the file as clean.


So... nothing I can really do about that. If possible, you should report it as a false positive and add an exception but otherwise... that's it. AVs nowadays just hate rare unknown files.
One solution would be to sign the executables because that'd prove that they came from me but... honestly? I don't see why I should verify my identity and pay a bunch of money just to have some AVs not mark my program as suspicious.

yeah, I didn't have any doubts about it, and knew it was done through the Heuristics system.  It happened to me yesterday as well, and then I did an exception for it, but for some reason it still did the same thing today.  So now I told Norton to not even bother scanning the folder and the file, so hopefully that will prevent it from happening again.

I wanted to let you know cause I am not sure if there was something you could possibly do or not.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: eisberg on January 17, 2018, 12:20:31 am
Or people should stop using bloatware anti-virus like Norton....

...

meh, I got it free from Comcast.  This is the first time I ever had a problem like this.  This is the first time that telling it to exclude it in future scans didn't work.  No reason to not keep using Norton.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: jr2 on January 20, 2018, 01:05:15 am
I don't think this is something the ReShade devs can fix. For ReShade to work Windows has to load ReShade's DLL instead of the "official" OpenGL32.dll (which in most cases is in C:\Windows\System32). If you take a look at MS' documentation (https://msdn.microsoft.com/en-us/library/windows/desktop/ms682586(v=vs.85).aspx#standard_search_order_for_desktop_applications), you'll see that Windows first checks the EXE's folder and then the system directory. The result is that unless you want to inject the DLL, you'll have to place it in the EXE's directory.
You could use the current working directory or the PATH to modify this in the past, however, some malicious software abused this fact which is why it's not possible anymore.

mklink?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 20, 2018, 08:34:33 am
mklink needs admin rights. I'd also have to call it for every single file at which point I could just copy those files instead of linking them.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: jr2 on January 20, 2018, 11:47:58 am
mklink needs admin rights. I'd also have to call it for every single file at which point I could just copy those files instead of linking them.

mklink /d , and have the program look for that folder.    I use mklink /d to link my user folders from my spinny disk to my user profile on my SSD.

However that does leave the problem of admin rights.  I mean, you could prompt for it, and have the description of the ReShade mod state that it will need admin permissions.

Wait, can you link to a dll in a subfolder as long as the .exe is in the parent?  if not this wouldn't work.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 21, 2018, 08:09:32 pm
Wait, can you link to a dll in a subfolder as long as the .exe is in the parent?  if not this wouldn't work.
No, that doesn't work. The .dll has to be in the same folder as the .exe.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Farkas on January 25, 2018, 04:46:19 am
Hey guys!
I have a problem with the downloading. When I click on the download links, the fsnebula.org isn't able to load. After a while it says: The webpage can't be reached. fsnebula.org takes too long to respond.
Can somebody upload the latest version of the launcher somewhere if it won't/can't be repaired?
Many thanks!
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 25, 2018, 06:52:41 am
Weird... fsnebula.org loads just fine for me. Is a program on your computer blocking it or something?
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Farkas on January 25, 2018, 11:07:37 am
Well, it seems somehow the university's IT blocked the page. I used VPN and loaded just fine and was able to download the Knossos. Sadly a bunch of ports are blocked in my dormatory, so no online playing and torrenting without VPN servers. However I didn't experienced that pages were locked apart from some porn sites (as said, I don't know ofc :Đ).
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: chief1983 on January 25, 2018, 11:14:20 am
And I thought colleges were supposed to be bastions of free information :P  At least my alma mater (UMR) was pretty chill about that.  Gaming galore.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Nyctaeus on January 25, 2018, 04:46:25 pm
Is there any progress regarding private mod/collab option? Or are there other, more important stuff to be done? I need it. Badly :P
Title: Re: PUBLIC BETA: Knossos 0.7.9 (combined launcher/installer)
Post by: ngld on January 25, 2018, 06:04:41 pm
I'm currently finishing the global flags stuff and fixing a few bugs I've introduced recently. Once that's done, I'll get to the private mods/staff tab/acl feature.
Progress has been slow the last few weeks because I was busy with exams. Those are done now and I hope to make some progress on this over the weekend.
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: ngld on January 29, 2018, 02:50:29 am
Well, I managed to finish the global flags and a few critical bugs but I got sick over the weekend and haven't managed to start work on the staff tab, yet.
Anyway, 0.8.0 has been released and as mentioned above, it finally implements global flags (click on the cogwheel on the upper-right corner and you should see them). You still have to set your global flags for each version of FSO since each version supports a slightly different set of flags. I want to simplify this in the future (i.e. allowing you to copy flags from one version to another or creating a general list of flags that are supported by every version after 3.8.0) but this should make everyone's life easier in the meantime.

Next on my list of stuff to work on is a simple updater for macOS users (It will just download the latest .dmg, open it and quit Knossos. You still have to overwrite the old version yourself), fixing FSO build installation on macOS and the staff tab. I'm currently not aware of any critical bugs so tell me if you find some! Bugs can be reported here, on Discord or on GitHub (https://github.com/ngld/knossos/issues). You can also see all current feature requests over on GitHub. Feel free to add your own.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: Rogue Assassin04 on January 31, 2018, 08:33:47 am
hello people.

Its a very innovative and a useful launcher.

But here i am facing a problem. i do not see any settings for anti aliasing.

I'm asking this because i have an old PC and cannot really handle anti aliasing very well.

any solutions to tweak about the anti aliasing? my frame rate is very low. hence i am asking.

Thank you.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: ngld on January 31, 2018, 09:14:29 am
FSO doesn't have antialias options (apart from the flags). However, disabling Deferred Lighting might give you better performance.
To change the FSO flags, go to the settings screen (click the cogwheel in the upper-right corner) and open the flags section there. If you only want to change the flags of a single mod, go to the home tab, hover over the mod tile, click on the little arrow on the bottom and go to "FSO Settings". That screen allows you to change the flags for that specific mod.

There was an option for antialias but it was removed in 3.8.0.
Title: Re: PUBLIC BETA: Knossos 0.7.8 (combined launcher/installer)
Post by: AdmiralRalwood on January 31, 2018, 09:00:38 pm
There's a command-line option for FXAA, but it's disabled by default.
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: Rogue Assassin04 on February 01, 2018, 06:45:43 am
Ohk... Thanks for letting me know..

Btw, disabling deferred lighting helped

:)
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: Novachen on February 03, 2018, 11:20:05 am
The person that uploaded the new Inferno release with the version 1.3.1-classic and deleted the old 1.3.1 one, should also update the Sol - A History release, because Sol - A History can not be downloaded anymore, because InfR1 is missing, now.

Actually i am curious, why there is a complete new Inferno entry in the first place? Why not a simple update to the older one? Also a few weeks ago, i had suddenly two complete different Cardinal Spear releases on Knossos... because there were also a complete new upload with a new mod ID...  unfortunately the older one that had more effort in a Knossos compatible Logo and Banner and looked nicer in the Explore tab, was deleted ^^.
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: PIe on February 03, 2018, 11:41:46 am
The person that uploaded the new Inferno release with the version 1.3.1-classic and deleted the old 1.3.1 one, should also update the Sol - A History release, because Sol - A History can not be downloaded anymore, because InfR1 is missing, now.
Actually they were uploaded by different persons.  JSRNerdo updated INFR1 and I uploaded SAH.  I'll fix SAH.


Actually i am curious, why there is a complete new Inferno entry in the first place? Why not a simple update to the older one? Also a few weeks ago, i had suddenly two complete different Cardinal Spear releases on Knossos... because there were also a complete new upload with a new mod ID...  unfortunately the older one that had more effort in a Knossos compatible Logo and Banner and looked nicer in the Explore tab, was deleted ^^.
Old Inferno was merely updated, in preparation for the upcoming Inferno release.  The second Cardinal Spear was the FSCRP version, and it now has the prettier images.
Edit:  apparently Inferno Classic apparently is a new mod, but the reasoning stands.
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: Rae2005 on February 03, 2018, 06:32:40 pm
So how do i get text to speech working for this since most mods seems to not have voice (probably due to lack of voice actors) :banghead:
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: ngld on February 03, 2018, 06:46:57 pm
Go to settings (the cog icon in the upper-right corner), open the speech section, check the appropriate boxes next to "Use Speech In" and press the big save button at the top. The setting is global and should apply to all mods.
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: OverDhill on February 03, 2018, 07:12:32 pm
Go to settings (the cog icon in the upper-right corner), open the speech section, check the appropriate boxes next to "Use Speech In" and press the big save button at the top. The setting is global and should apply to all mods.

My 'Voice' drop down menu has no selections (I have IVONA 2 Amy installed and it works fine with the wxLauncher)
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: Novachen on February 04, 2018, 06:32:25 am
Go to settings (the cog icon in the upper-right corner), open the speech section, check the appropriate boxes next to "Use Speech In" and press the big save button at the top. The setting is global and should apply to all mods.

My 'Voice' drop down menu has no selections (I have IVONA 2 Amy installed and it works fine with the wxLauncher)

I never used this feature, but i actually can confirm that. Even the default Cortana TTS speech on Windows 10 is not selectable.


Additionally i do not have any connection to the database, as it seems. I am unable to log in as well i can not create and upload new Mods, because i can not verify the mod ID.
I wanted to upload some Mods on Knossos that are not there already.

EDIT:
"Shivans" is not playable, because it does not have any exe configuration in the mods.json by default. So it requires a user configuration before.
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: PIe on February 04, 2018, 10:23:45 am
"Shivans" is not playable, because it does not have any exe configuration in the mods.json by default. So it requires a user configuration before.
Try deleting and redownloading it.  I believe that issue was fixed some time ago.
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: ngld on February 04, 2018, 02:43:14 pm
Looks like the Voice selection issue was caused by a packaging problem (some generated code for COM interaction is missing =/). Will be fixed in the next version!

The Nebula should work fine again, there was an issue with the database server.
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: Rae2005 on February 04, 2018, 03:57:42 pm
Go to settings (the cog icon in the upper-right corner), open the speech section, check the appropriate boxes next to "Use Speech In" and press the big save button at the top. The setting is global and should apply to all mods.

My 'Voice' drop down menu has no selections (I have IVONA 2 Amy installed and it works fine with the wxLauncher)
excactly my issue  well hopefully this will be fixed in the next update. :mad:
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: ngld on February 07, 2018, 10:44:32 pm
0.8.1 has been released. It fixes CPU feature detection (AVX, SSE, etc.), verifies dependencies during mod upload, implements a fix for macOS builds (which will only work once the metadata has been updated) and should have fixed the voice selection. However, the CI failed to generate the necessary code (if I build it locally, everything works) and I currently don't have the necessary time to figure out why.
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: Rae2005 on February 07, 2018, 11:59:40 pm
nope still no voice do i need to download one or something?
Title: Re: PUBLIC BETA: Knossos 0.8.0 (combined launcher/installer)
Post by: ngld on February 08, 2018, 12:28:46 am
Sorry, I wasn't clear enough. I tried to fix the bug but that didn't work due to the way the CI builds the releases. I'll have to think of another solution to the problem (probably generating the necessary code at runtime).
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Rae2005 on February 08, 2018, 03:57:31 am
I see, well good luck, i guess.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: oljo on February 08, 2018, 07:32:12 am
Hi.

I have tried Knossos on ubuntu 16.04 and kubuntu 17.10 but when i start it up after installasion i get a error, that its has stopped working, what to do? 
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: ngld on February 08, 2018, 12:47:47 pm
Can you please run KN_DEBUG=1 knossos in a terminal and post the output?
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: oljo on February 09, 2018, 04:17:38 pm
Traceback (most recent call last):
  File "/usr/bin/knossos", line 10, in <module>
    load_entry_point('knossos==0.6.0', 'gui_scripts', 'knossos')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 542, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2569, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2229, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2235, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/share/knossos/knossos/launcher.py", line 41, in <module>
    from . import center
  File "/usr/share/knossos/knossos/center.py", line 103, in <module>
    from . import util # noqa
  File "/usr/share/knossos/knossos/util.py", line 30, in <module>
    import semantic_version
ImportError: No module named 'semantic_version'



heres the file
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: ngld on February 09, 2018, 05:59:51 pm
I guess that's from your Ubuntu 16.04 system? The version you have (0.6.0) is outdated but the latest version (0.8.1) isn't available for Ubuntu 16.04 because a dependency (python3-pyqt5.qtwebengine) is missing there. I think you currently need at least Ubuntu 17.10 to install Knossos. Sorry.
I had hoped Ubuntu would backport or adopt the package much quicker than it has because the software has been available elsewhere literally for years (Qt 5 which introduced WebEngine was released in 2012).

So... yeah. Your only choice at this point is to update to 17.10 or wait until 18.04 releases and update to that.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Rae2005 on February 10, 2018, 12:32:07 am
 Sometimes I get error: The application was unable to start correctly. 0xc000007b  error when trying to run any game from Knossos.


 System specs as far as I know.

Windows 7 home premium (x64) SP1
 Processor: AMD FX-6300
Ram: 4GB


My FS2 installation is from GOG if that changes anything
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Farkas on February 10, 2018, 03:38:11 am
Sometimes I get error: The application was unable to start correctly. 0xc000007b  error when trying to run any game from Knossos.


 System specs as far as I know.

Windows 7 home premium (x64) SP1
 Processor: AMD FX-6300
Ram: 4GB


My FS2 installation is from GOG if that changes anything
I had the same message until I reinstalled (or installed) the Open AI. May be that will be your problem too.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: jr2 on February 10, 2018, 08:58:29 am
Sometimes I get error: The application was unable to start correctly. 0xc000007b  error when trying to run any game from Knossos.


 System specs as far as I know.

Windows 7 home premium (x64) SP1
 Processor: AMD FX-6300
Ram: 4GB


My FS2 installation is from GOG if that changes anything
I had the same message until I reinstalled (or installed) the Open AI. May be that will be your problem too.

Open AL

Open AI (https://openai.com/about/) in FreeSpace would be really cool, though.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Novachen on February 10, 2018, 09:05:20 am
Maybe another project for Bryan See or woutersmits?  :lol:
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Nightmare on February 10, 2018, 09:07:39 am
Better not. They already have so much stuff to do...
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: jr2 on February 10, 2018, 11:52:07 am
Maybe another project for Bryan See or woutersmits?  :lol:
Better not. They already have so much stuff to do...

You don't understand.  You don't take Open AI and put Open AI in FreeSpace.  Open AI takes you and puts itself in FreeSpace.  You just have to follow directives.  Never mind that they look like nuclear launch codes and the coordinates to every place Elon Musk has been spotted over the last 24 hours...
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Novachen on February 10, 2018, 01:34:37 pm
Maybe another project for Bryan See or woutersmits?  :lol:
Better not. They already have so much stuff to do...

You don't understand.  You don't take Open AI and put Open AI in FreeSpace.  Open AI takes you and puts itself in FreeSpace.
Well, i know that. But somebody have to play Freespace very much to create a very good OpenAI profile :).

Maybe they can even use OpenAI with FRED2 to create Generated Campaigns.
Or.. well.. three of the four ambitions mod projects by Bryan See can also be finished by OpenAI, if he is able to finish one of them during OpenAIs recording  :D
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: xenocartographer on February 10, 2018, 08:37:56 pm
Guys, let's not derail another thread with Bryan-snarking, please?
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: ngld on February 11, 2018, 03:07:53 am
Let's get back to the original problem...

@Rae2005: That error in general means that a 64bit application is trying to load a 32bit DLL (or the other way round). In this case your 64bit FSO is probably trying to load the 32bit OpenAL DLL packaged with Knossos. If you install OpenAL from Creative or put OpenAL Soft's DLL in the FSO directory, your problem should be solved. The latest nightlies and the next FSO release will include the OpenAL DLL as well so this should more or less fix itself in the future. I could add a warning if the OpenAL DLL is missing though...
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Rae2005 on February 12, 2018, 01:17:59 pm
Let's get back to the original problem...

@Rae2005: That error in general means that a 64bit application is trying to load a 32bit DLL (or the other way round). In this case your 64bit FSO is probably trying to load the 32bit OpenAL DLL packaged with Knossos. If you install OpenAL from Creative or put OpenAL Soft's DLL in the FSO directory, your problem should be solved. The latest nightlies and the next FSO release will include the OpenAL DLL as well so this should more or less fix itself in the future. I could add a warning if the OpenAL DLL is missing though...
Thank you that has appeared to fix the problem. funny detail though is sometimes it worked and sometimes it didn't
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: jr2 on February 13, 2018, 11:43:34 pm
Thank you that has appeared to fix the problem. funny detail though is sometimes it worked and sometimes it didn't

Ah, Windows...
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Viriatus79 on February 15, 2018, 10:35:57 am
Greetings,

Firstly I’d like to commend you guys for this tool. I’ve tried it and despite some of the new aspects of the Knossos (extra folder outside of the main FS2, mods being installed at the new Knossos folder instead of the FS2, layout...) I’ve sticked with it. I understand the intent of what is being done with Knossos. I’ve used mainly the YAL launcher with the mods being installed at the main FS2 folder. I’m running on a Windows 7 SP1, on a i5 with 2.4 GHZ. But (oh man here it comes) today I’ve installed the 0.8.1 update via the Knossos. When I tried to run it I received an error message, saying that it couldn’t find the game executable. So I go and do a full review on the options selected, because with was working fine until the update. On the next instance I’ve received a message saying that I had to reboot the Knossos, which I did and rebooted my pc as well. However the error messages kept on going the same and couldn’t run FS2 or any of the mods already installed. Furthermore, I tried to run FS2 again from the YAL launcher and now the game loaded the original retail version only, none of the mods installed in the main FS2 folder run anymore, not even the MediaSVPs_2014 mod. It must be something I’ve done wrong, or at least I tend to normally think that way immediatly. But I feel at a loss since everything I’ve done doesn’t work (reselecting the build, the exe in the options, etc...). Could you possibly point me out on a solution please? This is the game that I play the most...

PS - Sorry for the loooong description, just trying to provide as much info as possible.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: chief1983 on February 15, 2018, 10:48:59 am
Well, I can say that, Knossos _should_ not modify an existing FS2 install whatsoever.  It only asks for its location so it can copy the retail data into its own storage location.  It'd be like if Steam could have copied the pak files for Half-Life 1 instead of having to download them, except since they could verify license keys they didn't need to bother with copying data.  But you still had to install a Steam-ified Half-Life even if you already had the old 1.1.0.0 install laying around with your Counter-Strike and whatever mods, and other less popular mods did all have to go through the pains of being modified to work with Steam installs, etc.  It's really no different here, trying to move to a new paradigm can be a temporary pain but in the long run I think everyone can agree that a unified distribution and launching system is easier to work with these days, even if it does have to replace an existing setup to move forward.

But, if you never modified your own old install, Knossos should not have either, and I don't know why it would no longer work.  The item shared between the two would be your user data folder.  You could look into Users\<yourname>\AppData\Roaming\HardLightProductions\FreeSpace2Open\ folder but I'm not sure what I would recommend to check.  As a test, you could try simply renaming that folder and seeing if your YAL version creates a new one and runs successfully.  Don't delete it as it has your pilots, etc, but if that fixes anything then it can narrow down where the problem might lie.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: m!m on February 15, 2018, 10:53:14 am
Knossos didn't change anything about your existing install but it changed where the engine expects the configuration data (which is also what chief1983 mentioned). YAL is pretty outdated and hasn't been updated to handle the new way FSO stores its configuration (and I am a bit proud that it still worked :p) so if you want to continue using both your Knossos install and the old install you will need to use wxLauncher. That has full support for the new configuration system.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Viriatus79 on February 15, 2018, 02:03:32 pm
Thank you so much for the quick reply guys! I didn’t do anything and the Knossos launcher is now working!  :confused: I think I’m going to stick with the Knossos Launcher anyhow, I’ve tried the wx launcher (also on a separate folder from the main FS2 game folder) and it was easy to configure. Despite this I tried to load with the Media SVP’s 2014 mod and it didn’t loaded the hi-res textures again (pressing F3 at the main menu and checking the ship models, they show the old 1999 textures)... Ran through the configurations (HUD, Graphics, Gameplay, Audio, etc) and set the ones I’ve been using for the last 10 months without change, those that worked fine before installing Knossos. And still no cigar...  :hammer: Funny thing is that I’ve only noticed now that my old pilots are ALL gone!  :banghead: I was playing the SG 2017 mod (from the YAL launcher) and I was in the 20th mission or so, now it is gone! Now only the new pilots created from the Knossos launcher are displayed, even if I go back to launch FS2 with the wxlauncher or yal. Well, at least it was the only mod I was playing now, I had just finished the Exile mod!  :lol: Gonna start all over again...  :nono: I’m gonna give up on the “old” launchers and stick with the Knossos, I’m getting the hang of it now (I think...). Once again, thank you for the fast reply guys!  :D
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Cyborg17 on March 01, 2018, 12:42:01 pm
I installed around ten mods successfully and then whenever I run knossos my computer crashes in a "kernel panic".
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: core1401 on March 02, 2018, 12:16:32 am
how do you know what change in the updates? of the mods?
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Novachen on March 02, 2018, 03:06:44 am
No, so far there is any changelog.

But i did some changes and reuploads yesterday:
A Walk in the Sun 1.0 -> 1.0-A
This was only a repackaging from one Complete download to several individual downloadable VPs, because that would make updates much easier, because in following versions only the VP file have to be redownloaded that was changed. So you do not have to redownload the whole mod.

Dimensional Eclipse 1.1-b -> 1.1-B
The same change. All VPs are own packages now.

Dusk Wars Act 1 2.0 -> 2.0-A
Mostly the same change, but also some smaller Table fixes for DWA1.

Dusk Wars Act 2 1.0 -> 1.0-A
Repackaging mostly, but some of the tbms are smaller, because some of the DWA2 fixes were moved into the DWA1 files.

Friends and Foes: Retribution 1.1 -> 1.1-A
Repackaging only

Into the Halls of Valhalla 1.3.1-Nova -> 1.3.2-Nova
Repackaging. I also made some additional mission and table fixes.

Luyten Civil War 1.1-Nova -> 1.1.1-Nova
Repackaging. I created a LCW-specific flashes configuration for its ships and weapons.

Renegade Resurgence 1.1 -> 1.1.1
Repackaging. But you can also find some smaller mission fixes in this version.

Rogues! 1.0 -> 1.0.1
Repackaging. I also added some debriefing stages in a few missions

Shadow Genesis 2.1.2017 -> 2.1.2017-A
Repackaging only

VeniceMirror 1.4-Nova -> 1.4.1-Nova
Repackaging. I also include one additional bugfix for one mission aswell i created a complete flashes configuration for all VM ships and weapons
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: ngld on March 02, 2018, 01:36:49 pm
I installed around ten mods successfully and then whenever I run knossos my computer crashes in a "kernel panic".
... That shouldn't be related to Knossos itself. Can your run Chromium or other applications that use OpenGL? What's the callstack for the kernel panic?

how do you know what change in the updates? of the mods?
Unless the mod author puts a changelog in the mod's description, there isn't a way, yet. I'm planning to implement changelogs eventually.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Cyborg17 on March 02, 2018, 05:10:29 pm
... That shouldn't be related to Knossos itself. Can your run Chromium or other applications that use OpenGL? What's the callstack for the kernel panic?

It wouldn't stop happening even when I wasn't running Knossos, so I uninstalled everything and now everything is fine.  This computer is pretty ancient, so I'm chalking it up to that.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Zehlayer on March 07, 2018, 09:05:34 pm
Just Downloaded this software and trying to run the program through my files in my x86 folder. Knossos will download mods but when I try to run the program it comes up with an error message. Help! Return code 3221225595. No idea what this means
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: niffiwan on March 08, 2018, 03:28:08 am
Could you post a screenshot of the error?
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Zehlayer on March 08, 2018, 03:25:08 pm
I'll see what I can do.


edit** I've tried taking a screenshot but my print screen button isn't working for some reason. it says

fs2_open_3_8_0x64_AVX.exe - Application error


The application was unable to start correctly (0x000007b). click ok to close the application.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: niffiwan on March 08, 2018, 04:07:16 pm
What sort of CPU does your computer have? And what which anti-virus program are you running, Freespace Open can be affected by some anti-virus applications.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: ngld on March 08, 2018, 07:11:19 pm
0x000007b means that a 64bit program is loading a 32bit DLL or the other way round. The problem here is probably the OpenAL32.dll.

You can either install a recent nightly by switching to Knossos' settings, selecting "Nightly" as your preferred stability and updating your FSO installation (go to Home and click UPDATE on the FSO tile).

Or you can fix it by copying the missing DLL into FSO's folder: Download this archive (http://kcat.strangesoft.net/openal-binaries/openal-soft-1.18.2-bin.zip) and copy the openal-soft-1.18.2-bin\bin\Win64\soft_oal.dll into your FS folder\bin\FSO-3.8.0-2\x64\OpenAL32.dll.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Zehlayer on March 09, 2018, 05:31:12 pm
OK.....not sure what I am doing wrong. I bought the game through steam and yet Freespace open installer can't detect my retail version of the game. I am at a loss as when I do the GOG setup I can't find the files even though when I search my computer I can find my Freespace 2 game in the directory on my hard disk....
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: niffiwan on March 09, 2018, 09:53:08 pm
There seems to be a bit of confusion in your post - and hence in me :)

GoG FS2 Retail vs Steam FS2 Retail? (neither will search for retail files because they're installing the retail files?)
FreespaceOpen Installer vs Knossos? (I can't recall what retail file search the FreespaceOpen installer runs, but Knossos should search & find the install, if it's in the default/standard location - I think)

In theory you just need to:
Install FS2 retail via Steam
Install Knossos & install at least the FSO mod (you probably want MediaVPs 3.7.2 as well)
Fix the 0x000007b by following the instructions in ngld's post.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Zehlayer on March 10, 2018, 02:45:24 am
OK. Progress has been made. I  can now get the program to operate but when FS2 loads there is no audio and nothing is clickable via mouse and keyboard... Can't engage in missions either...


edit*** Updated SCP on knossoss. Got audio audio and system working but my screen is zoomed WAY far in on the screen and I can't see what I am doing.

Edit #2 .......I GOT IT TO WORK!!!! Thanks guys for all your help. Greatly appreciated and the game look phenomenal!
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: Novachen on March 15, 2018, 04:20:23 am
Well i have a developer question.

Some mods have their VP files directly in the root folder and do not have folders with the content of the respective package.
Actually i am curious how i can create that? Because i always got an error message if i try to change the folder for the respective files in the mod.json.

So i have to place all VPs in individual folders so that they are individually selectable.


Also i am missing a function to download and so to test the own uploads. I already encountered some problems with own mods that were unable to extract due to write-protected VPs or simply by upload errors (interrupting a upload to restart it later is a very bad idea). But i encountered these problems only by the installation on a second system. But there should be another possibilities to test your mods for that kind of errors.
Title: Re: PUBLIC BETA: Knossos 0.8.1 (combined launcher/installer)
Post by: ngld on March 15, 2018, 12:36:50 pm
First of all: The issues you encountered with corrupted uploads were all bugs in Knossos itself. Resuming uploads shoild work fine and write-protected files shouldn't cause issues either.

IIRC the case with the write-protected VPs happened at the same time Knossos corrupted all uploads for existing mods. AFAICT I managed to fix all of these (these bugs are one of the reasons I still consider Knossos to be in beta state).

To actually answer your question: You can create a second base folder. By switching your base folders in Knossos' settings, you can test your mods but as I pointed put earlier, this ideally shouldn't be necessary.
Mods only have package subfolders if you're authorized to change/upload them. I call this "dev mode". Whenever you install a mod, Knossos checks if you have write acceess and installs the mod in dev mode if you do. If you logout of your Nebula account (I'm actually not sure if this is possible right now), Knossos won't install your mod in dev mode but you also won't be able to upload it.


I should probably write some unit tests for the upload code to make sure that I catch these bugs before they end up in a release. That, however, requires time I currently don't have...

I want to eventually create a portable version of Knossos; that would make maintaining two installations on the same machine easier.
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: ngld on April 08, 2018, 07:03:33 pm
0.9.1 has been released! Download links are in the OP as always.

This version introduces the mod teams and private mods! This means that you can (finally) grant others access to your mod and upload private releases which won't be visible to anyone except your team members.
This release should also fix the install dialog looking like Windows 98 and the TTS settings. I've also fixed a bug which might've caused broken uploads in the past. Sometime during the next week, I'll check the currently released mods and fix any issues I'll find.

EDIT: TTS settings still aren't fixed.
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: CapellaGoBoom on April 08, 2018, 07:06:06 pm
The exploration tab in 0.9.1 seems broken...it says no mods found. Is that a bug?
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: ngld on April 08, 2018, 07:16:22 pm
Are you talking about the Home or the Explore tab? Everything's working fine for me...

Also, when Knossos asked for a game data directory (during your first launch), did you select "C:\Program Files (x86)\Knossos" ?
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: Rhymes on April 08, 2018, 07:47:56 pm
I'm also having the same problem. When I open the Explore tab, Knossos reports no mods found. Something's busted--it was working fine just before I updated.
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: ngld on April 08, 2018, 07:59:44 pm
Which Windows version are you using?
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: CapellaGoBoom on April 08, 2018, 08:09:31 pm
Which Windows version are you using?

10. I meant the mod exploration tab not the home tab
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: ngld on April 08, 2018, 08:15:49 pm
Please upload your Knossos debug log (%appdata%\knossos\log.txt).

I just did a fresh Knossos install on Windows 10 and everything's working fine. I also haven't seen anything in the automated error reports so right now I have no idea where the error might be.
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: Rhymes on April 08, 2018, 08:59:38 pm
Here's my log. Also running Win10.

Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: CapellaGoBoom on April 08, 2018, 10:49:36 pm
Attached is my debug
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: ngld on April 10, 2018, 03:08:59 pm
I've found the bug. Apparently the bug only occurred if you had no private mods, were logged in and the private mod list loaded faster than the public one. I'll fix it in 0.9.2 which will be released sometime this week. Until then you'll see a mod called "0.9.1 BugFix Workaround" if you're logged in which also fixes the bug by just being there (it's marked as private).
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: Iskandryu on April 11, 2018, 07:21:59 pm
I seem to have the same problem a previous user encountered. When trying to select voices from the Speech tab, none show up. There's no drop-down menu. I can use all the voices well and good in wxLauncher, but not in this one. Could it be a problem with Windows10? I've tested it on a Win7 computer, and the Speech drop down menu worked there.
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: ngld on April 11, 2018, 07:36:36 pm
I don't think this is related to the Windows version you use. The COM interface (which is necessary for TTS stuff and progress display in the taskbar) has been broken for a while. I thought I'd finally fixed it in this release but apparently it's still broken. I'll try fixing it in the next version (it's kinda hard to test since the bug only affects released versions).
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: Iskandryu on April 12, 2018, 09:24:16 am
But is there a way to activate TTS by a command line or something? Without the graphical interface?
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: ngld on April 12, 2018, 09:33:26 am
You can enable TTS by directly editing the fs2_open.ini. On Windows, it's in %APPDATA%\HardLightProductions\FreeSpaceOpen\.
Look for the SpeechTechroom, SpeechBriefings, SpeechIngame and SpeechMulti lines and replace "=0" with "=1" to enable TTS in the given area.
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: Iskandryu on April 12, 2018, 11:40:42 am
It worked, thanks a lot! Keep up the good work
Title: Re: PUBLIC BETA: Knossos 0.9.1 (combined launcher/installer)
Post by: Chaotic Entropy on April 15, 2018, 08:25:59 am
Thanks for this, very helpful in getting to play the campaigns through again.

I did notice that the mods that have dependencies on other mods seem to really like downloading the same packages over and over. So if I already have the mod it depends on installed, it knows I do and says so, but then downloads the same package all over again anyway.

E.g. FreeSpace Port MediaVPs is installed and FreeSpacePort Mission Upgrade relies on it, highlights in the download pop up that it is installed and then wants to download it again as part of the Mission Upgrades installation process.
Title: Re: PUBLIC BETA: Knossos 0.9.2 (combined launcher/installer)
Post by: Iskandryu on April 15, 2018, 05:22:42 pm
Umm... ok, after updating to the 0.92 version, i can't open the program anymore. It gives me an error: "Failed to execute script __main__", and that's it.
Title: Re: PUBLIC BETA: Knossos 0.9.2 (combined launcher/installer)
Post by: ngld on April 15, 2018, 05:23:33 pm
I know. I'm working on fixing that.
Title: Re: PUBLIC BETA: Knossos 0.9.3 (combined launcher/installer)
Post by: ngld on April 15, 2018, 06:19:42 pm
I've managed to fix the bug. If you've installed 0.9.2, here's the update link (https://fsnebula.org/knossos/stable/update.exe). Only Windows was affected.
Title: Re: PUBLIC BETA: Knossos 0.9.3 (combined launcher/installer)
Post by: Iskandryu on April 15, 2018, 06:44:44 pm
Thanks, but this doesn't work either. Now it fails to execute script fix-comtypes-rthook
Title: Re: PUBLIC BETA: Knossos 0.9.3 (combined launcher/installer)
Post by: Chaotic Entropy on April 15, 2018, 06:47:16 pm
It does this for me too with the script hook error.
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: ngld on April 15, 2018, 08:16:44 pm
Alright, this update has been tested by a few people on the Discord channel so it should actually work. Also the TTS settings are FINALLY working.

If you have a broken install and can't launch Knossos, download the updater manually (https://fsnebula.org/knossos/stable/update.exe) and run it. Afterwards, everything should be fine again.
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: hirmuolio on April 18, 2018, 05:48:28 am
Is there any way to set custom flags in Knossos?

I'm trying to change the -bloom_intensity value. There is no way to input custom flags in the launcher. If I add it to the cmdline_fso.cfg it gets overwritten when the game launches. If I add it to the settings.json of Knossos it gets overwritten when Knossos launches.

Also would it be possible to have truly global launcher flags? The current global flags effect only one FSO version at a time so every time.

And by all the FSO settins are on "default". Wether this is "on" or "off" is big mystery.

Also is there a way to ignore dependancies? Some mods have 3.8.0 set as dependancy so they will refuse to run on nightlies.
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: Novachen on April 18, 2018, 06:26:42 am
You can set custom flags for every mod individually if you use the "FSO Settings" option in the Mod Detail -> Options.

The Global Flags are for all mods. Default means, that the predefined setting by the mod is used. On deactivates this option regardless of the mod setting, off deactivates it.
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: ngld on April 18, 2018, 08:39:41 am
@hirmuolio Did you read the help text on the Global Flags section? IMO, it clearly explains what Default means.

Hm... I could've sworn I implemented the custom flags field for global flags as well. Looks like I forgot that. Will add it later.
Global flags have to be set for each version since each version has its own list of supported flags. You can set global flags for multiple versions though.

Dependencies are only used to select the default build. They don't influence the build selection. You probably need to change your preferred stability in Knossos' settings the see the nightly builds. (They'll only show up after being installed).
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: hirmuolio on April 18, 2018, 10:56:13 am
Seems like some mods have the FSO dependancey as ""version": ">=3.8.0-2",". These will run the nightlies just fine.

Some have the dependancy as ""version": "3.8.0-2",". These will run on 3.8.0-2 even if 3.8.1 is selected. (well this is from testing three mods: FSPort, BtA and FSPort MVP)
Edit: Seems like they just ignore the preferred engine set in Knossos settigs. If I set them to use nightly on mod specific setting they will use nightly. Or something like that, having mod specific settings and Knossos settings separately and neither talks to the other is confusing.

Majority of the flags that can be set are same for all FSO versions. Things like windowed, v-sync, frame limiter. The setting screen could do with some facelift anyways. A list of flags isn't very user friendly and few of them are useful.
And at least the -bloom_intensity flag didn't cause any issues even if it was used with older version that had no bloom.

The global flag setting could mention that by default everything is off unless the mod enables it or you enable it. Just saying "Default tells Knossos to use the setting the modder chose" won't make the end user realize that most mods will have nothing enabled unless you enable them.
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: ngld on April 18, 2018, 11:25:57 am
Some have the dependancy as ""version": "3.8.0-2",". These will run on 3.8.0-2 even if 3.8.1 is selected. (well this is from testing three mods: FSPort, BtA and FSPort MVP)
Works fine for me. If I select a nightly in the mod's FSO settings, it uses the selected build.

Majority of the flags that can be set are same for all FSO versions. Things like windowed, v-sync, frame limiter. The setting screen could do with some facelift anyways. A list of flags isn't very user friendly and few of them are useful.
Sure, the majority are the same but that doesn't help if even one of the flags might cause issues. Besides, I need an FSO version to fetch the flags. Regarding the facelift: Feel free to suggest a better design. My approach was to let modders set the default flags so that new users wouldn't have to worry about them. Experienced users would recognize the flag list and know how to use them from previous launchers.

The global flag setting could mention that by default everything is off unless the mod enables it or you enable it. Just saying "Default tells Knossos to use the setting the modder chose" won't make the end user realize that most mods will have nothing enabled unless you enable them.
Eh, that's only true as long as most modders don't enable flags. I don't want to put assumptions into the help text which I might have to change depending on what people upload.

Edit: Seems like they just ignore the preferred engine set in Knossos settigs. If I set them to use nightly on mod specific setting they will use nightly. Or something like that, having mod specific settings and Knossos settings separately and neither talks to the other is confusing.
... "neither talks to the other"? What?
Anyway, a mod can define an acceptable FSO version through its dependencies. Usually, the mod author should use something like ">=3.8.0-2" to allow future builds. Knossos respects that setting as long as the user doesn't override it through their mod specific settings. The preferred engine stability applies to all mods and thus has a lower priority than a mod's dependencies (otherwise the mod dependencies would be pointless).
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: hirmuolio on April 18, 2018, 12:00:09 pm
The global flag setting could mention that by default everything is off unless the mod enables it or you enable it. Just saying "Default tells Knossos to use the setting the modder chose" won't make the end user realize that most mods will have nothing enabled unless you enable them.
Eh, that's only true as long as most modders don't enable flags. I don't want to put assumptions into the help text which I might have to change depending on what people upload.

This mean that every time some new feature is added to FSO every single mod would need to update their included flags for it to be on. Seems rather backwards to set the baseline from individual mods.
I think better way would be to have some feature presets in the launcher settings like in the older launcher (all features on, low requirement features on, etc.). And then have the mods include only flags that they really need. Maybe even have a toggle in mod specific settings to overwrite global flags with flags provided by the mod if the mod requires something that you would like to not have in other mods (3d weapons on/off comes into mind). Or just a mark saying that defaults from mod are being overwritten by your flags.
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: ngld on April 18, 2018, 01:52:59 pm
That's not exactly true. Most features which are safe for all mods are enabled by default in FSO (i.e. lightshafts, deferred rendering, etc.). As such, FSO itself already provides a baseline and I see no reason to replace that in my launcher.
The presets (all features on, ...) weren't implemented because I didn't want to do bitwise math in JavaScript. IIRC they never worked completely anyway.

Maybe even have a toggle in mod specific settings to overwrite global flags with flags provided by the mod if the mod requires something that you would like to not have in other mods (3d weapons on/off comes into mind).
Well, first of all, a mod doesn't "require" flags. AFAIK all important mod settings were moved to tables. Even the 3d weapons option isn't required. If a weapon doesn't have an icon associated to it, FSO automatically uses the 3d model. Thus the mod works fine even without the flag.
At this point, the flags are supposed to be used to tweak the way FSO looks. In this context, allowing a mod author to set the default (i.e. the way they want players to experience their mod) seemed to be the best way to handle this. I still wanted to give the user the ability to override these flags which is why I added the FSO settings screen and the global flags. Since the mod author's selection is supposed to be the default, the global flags setting is applied to those flags and serves as an override. The mod-specific flags finally allow you override all flags with your own choice.

I don't see a reason to change this. If mod authors are only supposed to include the flags they "need", then no flags will be left since all of them depend on taste.
I agree though that the Knossos could use some more documentation.
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: hirmuolio on April 19, 2018, 10:38:03 am
Is it Knossos' doings that each campaign uses different settings? All kaybindings and audio settings are unique to a campaigns. Even in same mod each campaign uses different settings. I don't remember this happening before but my old settings were some kind of odd buggy mess before...

Is there any way to copy the settings from one campaign to another. it is really annoying to have to rebind every single key when switching campaign.
Title: Re: PUBLIC BETA: Knossos 0.9.4 (combined launcher/installer)
Post by: AdmiralRalwood on April 19, 2018, 11:53:38 am
Is it Knossos' doings that each campaign uses different settings? All kaybindings and audio settings are unique to a campaigns. Even in same mod each campaign uses different settings. I don't remember this happening before but my old settings were some kind of odd buggy mess before...

Is there any way to copy the settings from one campaign to another. it is really annoying to have to rebind every single key when switching campaign.
It is not unique to Knossos; those settings are stored in the .csg file (campaign-specific save game). There's also no really easy way to copy those settings; it's a bit of a usability issue, for sure.
Title: Re: PUBLIC BETA: Knossos 0.10.0 (combined launcher/installer)
Post by: ngld on May 14, 2018, 11:40:31 pm
Knossos 0.10.0 has been released. This release contains mostly bug fixes and implements custom flags globally (you can finally apply your lighting settings to all installed mods).

Issues with HiDPI on both Windows and macOS have been reported. However, I don't know too much about that and can't test. As such I'd be glad if anyone could look into a solution for this (GitHub ticket (https://github.com/ngld/knossos/issues/123)).

Unless someone discovers a critical bug in this release, I'll release it as 1.0.0. After that, I'll probably start releasing nightlies and only release new versions once they've been tested enough. This will take a bit of work since I'll have to change the integrated updater.

I'll also overhaul how the Neblua login and internal handling of the mod list works after 1.0.0. Most of this won't be visible but it'll make working with the code easier. New features that are planned are (still) the tag system and smaller updates for mods.
Title: Re: PUBLIC BETA: Knossos 0.10.0 (combined launcher/installer)
Post by: jr2 on May 17, 2018, 07:29:16 am
Incoming jump signature, 1.0 configuration!  Yay!  :D
Title: Re: PUBLIC BETA: Knossos 0.10.0 (combined launcher/installer)
Post by: Nightmare on May 19, 2018, 07:09:45 pm
Quote
Opened log 'data/fs2_open.log', Sun Mar 25 23:54:28 2018 ...
  Initializing SDL...
FreeSpace 2 Open version: 3.8.1.20180217_0178374
Passed cmdline options:
  -spec_exp 9
  -ogl_spec 100
  -spec_static 2
  -spec_point 0.3
  -spec_tube 0.7
  -ambient_factor 80
  -nomotiondebris
  -no_emissive_light
  -soft_particles
  -post_process
  -bloom_intensity 10
  -nolightshafts
  -cache_bitmaps
  -ballistic_gauge
  -dualscanlines
  -orbradar
  -rearm_timer
  -targetinfo
  -3dwarp
  -warp_flash
  -mod Inferno/R2,Inferno,MediaVPs_2014
  -fps

What about a privacy option for uploaded logs as well? :D (Not my log btw)
Title: Re: PUBLIC BETA: Knossos 0.10.0 (combined launcher/installer)
Post by: Venicius on May 21, 2018, 12:53:58 pm
Just downloaded this now and this is AMAZING! Keep up the good work!  :pimp:
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on May 23, 2018, 12:28:27 pm
Knossos 0.10.1 has been released. It fixes a few bugs which were reported on Discord and asks the user which packages to install during mod updates if optional or recommended packages have been added.

@Nightmare: Well... uploaded logs are supposed to be public. If someone doesn't want them to be, they shouldn't upload them. Besides, the log doesn't seem to contain any kind of secret information.

@Venicius: Thanks!
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nightmare on May 23, 2018, 12:41:47 pm
Admitted, none of the logs in question contained any secret information, but since your tool is obviously useful for many people and will be used in the future for development/beta testing, I wanted to post it atleast; so there's a limited chance that something slips by that shouldn't been out (like which models are being loaded, stuff like that).
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on May 23, 2018, 12:50:34 pm
Hm... I could either add a warning to make it more obvious that the log will be public or disable the log search. Not sure how useful it is, anyway. It was intended as an easy way for coders to search for logs but since I never really mentioned/advertised it, I doubt anyone's using it.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nightmare on May 23, 2018, 01:00:30 pm
Maybe just disabling uploading logs atleast for private/beta tested mods? Most people doing beta testing should know what they're doing anyway, or atleast get in contact with the devs of the mod then.
The problem I'm seeing is that due to the death flash script being logged, one of the INF logs contains the entire ship list for R1, R2 and probably R3. Not that the list wouldn't be out soon with R1 anyway, and most ships are known by their name (so nothing new), but I thought "better mention that". :)
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on May 23, 2018, 01:21:05 pm
The logs aren't uploaded automatically. The user has to click on "Upload debug log" to trigger that.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nightmare on May 23, 2018, 01:23:51 pm
The logs aren't uploaded automatically. The user has to click on "Upload debug log" to trigger that.

Didn't doubt that. Than the users should be told that the logs for private mods are publical visible?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on May 23, 2018, 01:32:21 pm
Sounds like a good idea.

"The log you're trying to upload belongs to a private mod. Please be aware that this log (and any information in it) will be public. Do you want to continue?"
[Yes] [No] [Open Log]

The last button would open the log but keep the dialog open. This way the user could censor any secrets and still upload the log.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nightmare on May 23, 2018, 01:46:08 pm
That sounds good to me. Yet I don't know what the qualification standards for beta tester are, and hence if everyone uploading a log would be capable of removing all secrets. It might be better if only the 'owner' could view such things or the users that are members of the respective testing group. But I don't know if that'd cause too much work for you, and there're other methods of doing this? Also, when you're a beta tester you should have other methods of getting in touch with the devs anyway.

Maybe I'm overwhelming cautious, but it would be sad if the great work you're doing gets bad publicity for spoiling classified things. :)
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on May 23, 2018, 02:09:13 pm
I'm not going to try and stop people from revealing secrets. That'd be futile anyway (if someone really wants to, they could just upload the whole mod somewhere).
I want to prevent accidental leaks which the prompt should achieve.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: chief1983 on May 23, 2018, 03:05:39 pm
I think the issue is, in the spur of the moment a tester may not be qualified to know if anything he is uploading is secret or not, but a mod owner might be able to later look and make that decision.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: themac7212 on May 23, 2018, 10:48:46 pm
Hi. So probably stupid question. I have installed retail Freespace 2 from GOG. In Launcher I have FSO, MediaVP's, and FS2 Retail available. When I click play on any of them it gives me error saying I need to move FSO.exe to Freespace 2 folder. But when I do this and click play it the gives me error cant find FSO.exe. Im runnin on windows 8 x84. And thnx in advance for any help.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Bryan See on May 24, 2018, 02:46:49 am
Hi. So probably stupid question. I have installed retail Freespace 2 from GOG. In Launcher I have FSO, MediaVP's, and FS2 Retail available. When I click play on any of them it gives me error saying I need to move FSO.exe to Freespace 2 folder. But when I do this and click play it the gives me error cant find FSO.exe. Im runnin on windows 8 x84. And thnx in advance for any help.
And what of Total Conversions?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on May 24, 2018, 03:18:13 am
@themac7212: Can you please post a screenshot of the error messages? I can't tell which one you're talking about.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ssmit132 on May 26, 2018, 02:40:40 am
Hi,

I downloaded 0.7.9 from the Knossos site, installed it and then said "yes" when it asked me if I wanted to update to 0.10.1. However, when the installation starts, it gets part way through and then cuts out with no message after getting to a certain point. When I try to run Knossos again after that, I get the below error and can't run it.

(https://i.imgur.com/Vih2ATj.png)

It seems like it's choking on not being able to install a certain file? It makes me wonder whether the old version is still using it while the update is going, and the installer terminates itself when it can't replace the old file.

How should I go about allowing it to update properly?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: AdmiralRalwood on May 26, 2018, 09:58:43 pm
How should I go about allowing it to update properly?
Should be able to grab the latest version here: https://github.com/ngld/knossos/releases
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on May 27, 2018, 12:31:54 am
Interesting. Haven't seen that problem before. Which AV do you use?

It makes me wonder whether the old version is still using it while the update is going, and the installer terminates itself when it can't replace the old file.
That can't happen. The updater waits until Knossos' process quits before it starts replacing files.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ssmit132 on May 28, 2018, 10:44:55 am
Interesting. Haven't seen that problem before. Which AV do you use?

I use Bitdefender Anti Virus Free Edition. Though after you asked about it I tried disabling it, installed 0.7.9 and then updated, and it worked fine. So maybe the AV stopped it for some reason. Thanks for that :)
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Novachen on May 29, 2018, 11:01:52 am
Ah well.. it seems there is a character limit for the description of a mod, because i got an unknown error during my upload. The look into the log files say this:
Code: [Select]
4.description.String value is too long: ['releases']
Well, because the description is shown completely offline, i have to ask... how long can a description be?
Because i wrote them in two languages (tabs or something like that would be helpful, additionally to the planned changelog tab ^^) the description in question is 20279 characters long.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on May 30, 2018, 10:28:36 pm
The current limit is 10240. I've added limits to all text input to make sure that I never accidentally store more data than expected in them. I never thought someone would reach that limit which is the reason you didn't get a proper error message. I could probably raise the limit. Does 100000 sound reasonable?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Novachen on May 30, 2018, 10:52:54 pm
Does 100000 sound reasonable?

I also think that this 20k+ would be a very very rare exception because there are so many changes and additions in this mod... even the description in one language would be already problematic with 10k characters. But if i had knew this sooner, i would had simply reduced the description to the most important points and had added a forum thread link for the respective language for all the other information instead.

So well.. i am not sure if it is really necessary to make the limit higher. I could simply try to reorganize the description, though. Most important information for me is, character limit is 10240. That is a number i can work with in the future :).
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Bryan See on June 06, 2018, 09:27:23 am
Why can't we have internal video hosting of our own?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nightmare on June 06, 2018, 09:37:30 am
Why can't we have internal video hosting of our own?

Because there's already this thing called YouTube? Apart from that, the number of mods that have trailers is rather limited.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 06, 2018, 09:40:25 am
We could... but why? Why would you even try to implement a new hosting service when there are several free ones around? Especially given how much work it would take and money (since you'll need to buy servers in several geographic locations or rent a CDN), it's not even worth the effort.
Besides, that's completely out of scope for a mod installer/launcher.

If you create your own video service, we can talk about this again. Otherwise, it's pointless to bring up.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nightmare on June 06, 2018, 10:18:24 am
Also, as far as I can see that (I don't use Knossos myself), you already can watch trailers/other mod-related videos on YT, so there isn't any need for some custom platform.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Bryan See on June 07, 2018, 01:26:23 am
OK. I consider.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ShadowOwl on June 08, 2018, 11:00:16 am
Hm, tried running Knossos on my Mint 18.3 (64 bit) system and this is what I get:
Code: [Select]
~ $ knossos
Traceback (most recent call last):
  File "/usr/bin/knossos", line 10, in <module>
    load_entry_point('knossos==0.6.0', 'gui_scripts', 'knossos')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 542, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2569, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2229, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2235, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/share/knossos/knossos/launcher.py", line 41, in <module>
    from . import center
  File "/usr/share/knossos/knossos/center.py", line 103, in <module>
    from . import util # noqa
  File "/usr/share/knossos/knossos/util.py", line 30, in <module>
    import semantic_version
ImportError: No module named 'semantic_version'
Any help or hints would be much appreciated.

Edit: it also looks like Knossos is a billion versions behind the latest release in the PPA for xenial (version 0.6.0 instead of 0.10.1):
https://fsnebula.org/knossos/
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Bryan See on June 08, 2018, 11:25:17 am
Check whether a module named 'semantic_version' exists.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 08, 2018, 12:05:37 pm
@ShadowOwl: You're probably missing the python3-semantic-version package.
The packages for every Ubuntu release before artful are outdated because the python-pyqt5.qtwebengine package is missing there but required for newer Knossos versions. I have no idea why Ubuntu decided to delay the release of that Qt component for that long (it's been literally years since Qt released it) but it's the only platform missing it and as such I saw no reason to keep using the outdated QtWebKit. This means you'll either have to upgrade your Ubuntu installation to artful or bionic, or you backport python-pyqt5.qtwebengine for xenial at which point I could release the current version there.

In the meantime I should probably delete the outdated packages to avoid further confusion. If you're feeling adventurous, you can try building Knossos from source (https://github.com/ngld/knossos). It still contains the code to support QtWebKit but I can't guarantee that it's still working since it's been quite some time since I last tested it.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Bryan See on June 08, 2018, 01:59:00 pm
Try the latest version available.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: OverDhill on June 10, 2018, 04:39:44 pm
Is there a way to install Reshade/Sweetfx so that Knossos uses it? Also how do you add any table mods to a campaign or MOD's like the cockpit one?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: AdmiralRalwood on June 10, 2018, 11:58:32 pm
Also how do you add any table mods to a campaign or MOD's like the cockpit one?
This is supposed to be done through a special kind of mod that I don't think has actually been implemented yet...
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 11, 2018, 12:15:25 am
ReShade/SweetFX have been brought up before (https://www.hard-light.net/forums/index.php?topic=94068.msg1861928#msg1861928). TL;DR: You can get it to work manually by copying the DLLs to FSO's exe folder but you'll have to do that after every FSO update. If anyone wants to automate that by making Knossos copy the DLLs, feel free to submit a PR. AFAIK no other solution (except directly injectiong the DLLs into FSO) would work.

I considered cockpit mods (and table mods) when designing Knossos' metadata schema. Knossos could support them, however as AdmiralRalwood said, the necessary code hasn't been written, yet. For now you'll have to modify the mod's files manually the same way you would have done it before (or you could create a new mod through the dev tab for that purpose which uses the mod you want to modify as a dependency).
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Fire888 on June 11, 2018, 12:51:41 am
So...
I have an issue, a major one:

Whenever I try to run a mod, Knossos always starts retail FS2, with the FSO exe, mind you. Aka: It tells me, in the text down below, that it is FSO 3.8.1 etc, but it doesn't start MediaVPs, so, no enhanced graphics, and for any mod, no campaigns to select other than the standard FS2 one.

 Anything I might be doing wrong here?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 11, 2018, 01:42:51 pm
Can you run a Fast Debug build and upload the debug log?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Kazan on June 11, 2018, 08:47:15 pm
I still moderate this? :P
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nightmare on June 11, 2018, 08:53:57 pm
I still moderate this? :P

 :yes: but there're more of bryans posts.

Do your job more often :p
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Fire888 on June 12, 2018, 04:04:43 am
Can you run a Fast Debug build and upload the debug log?

I tried to, but it doesn't create a log to upload...

I've tried to run it several dozen times, no log that was created anywhere D:
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 12, 2018, 04:24:55 am
Try to run a debug build again (once) and then upload your %appdata%\knossos\log.txt.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Fire888 on June 12, 2018, 04:50:06 am

Try to run a debug build again (once) and then upload your %appdata%\knossos\log.txt.

Here you go.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 12, 2018, 05:59:47 am
Weird, at first glance it looks like everything's working the way it should... I'll have a look again later when I have more time.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Novachen on June 12, 2018, 06:39:15 pm
Mhh.. i encountered a strange error.

Actually i am not able to create a mod that has one of some other mod as a dependency.

I get a "requires 'FSO' which is missing" error message. But this one disappear if i delete the Mod as an Dependency, so it has nothing to do with the FSO package. The change between the last nightly and last official executable made no difference.

I can create and start mods that has mods like Dusk Wars, Exile, Burning Heaven, FreeSpace Port, Shadow Genesis or Scrolls of Antankharzin as an dependency, but i get the error message with Mods like Blue Planet Complete, Between The Ashes or even The Aeos Affair.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 13, 2018, 07:18:41 am
@Fire888: Can you check if your %appdata%\HardLightProductions\FreeSpaceOpen directory exists? If it does, please post the data\fs2_open.log and data\cmdline_fso.cfg files.

@Novachen: Sounds like the version requirements on FSO are conflicting. I should improve that error message. In the meantime, can you open the %appdata%\knossos\log.txt and check if it contains a message like "No version of mod "FSO" found for these constraints: ..." ?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Fire888 on June 13, 2018, 07:28:06 am
@Fire888: Can you check if your %appdata%\HardLightProductions\FreeSpaceOpen directory exists? If it does, please post the data\fs2_open.log and data\cmdline_fso.cfg files.

@Novachen: Sounds like the version requirements on FSO are conflicting. I should improve that error message. In the meantime, can you open the %appdata%\knossos\log.txt and check if it contains a message like "No version of mod "FSO" found for these constraints: ..." ?

There is only a fs2_open.ini, not a .log

Code: [Select]
[Default]
VideocardFs2open=OGL -(1920x1080)x32 bit
TextureFilter=1
Language=English
CurrentJoystick=No Joystick
CurrentJoystickGUID=None
EnableHitEffect=0
SpeechVolume=100
SpeechVoice=0
SpeechTechroom=0
SpeechBriefings=0
SpeechIngame=0
SpeechMulti=0

[Sound]

The config file is attached.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 13, 2018, 08:17:32 am
Hm... do you have a log in C:\Games\FreespaceOpen\FS2\data\fs2_open.log ?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Fire888 on June 13, 2018, 08:33:48 am
Hm... do you have a log in C:\Games\FreespaceOpen\FS2\data\fs2_open.log ?

Yep! Here it is.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 13, 2018, 09:15:44 am
Is there a fs2_open.ini in the same folder as the log file? If there is, delete it and try running FSO through Knossos again.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Fire888 on June 13, 2018, 09:25:59 am
Is there a fs2_open.ini in the same folder as the log file? If there is, delete it and try running FSO through Knossos again.

There isn't. The .ini is in appdata. I tried to delete that and then Knossos tells me "Failed to save the configuration" and crashes.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Novachen on June 13, 2018, 09:45:19 am
@Novachen: Sounds like the version requirements on FSO are conflicting. I should improve that error message. In the meantime, can you open the %appdata%\knossos\log.txt and check if it contains a message like "No version of mod "FSO" found for these constraints: ..." ?

No, unfortunately there is no entry in the log for this problem.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nikogori on June 13, 2018, 02:06:21 pm
I can't use my joystick with Knossos. What am I missing?
I have attached fs2_open.log and fs2_open.ini. Please let me know if you need any further information.

Code: (fs2_open.ini) [Select]
[Default]
VideocardFs2open=OGL -(1920x1080)x32 bit
TextureFilter=1
Language=English
CurrentJoystick=0
CurrentJoystickGUID=6d0415c2000000000000504944564944
EnableHitEffect=0
SpeechVolume=100
SpeechVoice=0
SpeechTechroom=0
SpeechBriefings=0
SpeechIngame=0
SpeechMulti=0
LastPlayer=test
ScreenshotNum=8

[Sound]

Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nikogori on June 13, 2018, 03:42:09 pm
It seems 3.8.1-20171118 (Revision dfdfd59) is OK. Latest Nightly 3.8.1-20180611 (Revision 15bda8c) doesn't work.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 13, 2018, 05:06:59 pm
@Fire888: Not sure what's going on in with your problem... Knossos is doing exactly what it's supposed to but for some reason FSO is trying to load its configuration from the wrong location. I've asked the FSO devs about it but they didn't have any ideas either... Sorry.

@Novachen: I'll look into it.
@Nikogori: At some point the nightlies got a newer SDL version which uses different GUIDs for the joysticks. Now I have to update Knossos to automatically detect which GUIDs to use based on the SDL version. It'll get solved eventually (I already have a solution in mind) but it'll take some time unit it's done. Until then you can either use an older build or put the correct GUID infs2_open.ini manually (your joystick's GUID appears in fs2_open.log).
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Fire888 on June 14, 2018, 02:14:47 am
That sucks... D:

I've tried uninstalling and reinstalling, too, but to the same results. I guess I gotta use the old launchers ^^;
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nikogori on June 14, 2018, 12:24:40 pm
@Nikogori: At some point the nightlies got a newer SDL version which uses different GUIDs for the joysticks. Now I have to update Knossos to automatically detect which GUIDs to use based on the SDL version. It'll get solved eventually (I already have a solution in mind) but it'll take some time unit it's done. Until then you can either use an older build or put the correct GUID infs2_open.ini manually (your joystick's GUID appears in fs2_open.log).

Thank you! I have modified fs2_open.ini and now I can use my joystick with latest Nightly. Keep up the good work.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Spoon on June 17, 2018, 01:17:53 am
So I installed the latest and greatest knossos to get inferno from it. And sure enough, it all works so nicely and smoothly. Exceeeeept...

For reasons I don't really understand, it somehow overwrites where the engine looks for all of its pilot and config files? Even in my completely seperate WoD dev folder where I use the good old 5.5g launcher, it somehow stops looking in the local installation but in effing AppData\Roaming\HardLightProductions\FreeSpaceOpen\data which is 7 folders deep onto my c: drive (which is a completely seperate drive from where I have any and all of my freespace stuff installed). This is super inconvenient and made me just uninstall knossos completely, because it messes with my workflow and it seemingly can't be configured anywhere.
Not to mention I just plain old hate having to look for things in appdata, its so far removed from everything and is just straight up inferior to just having things nicely in the local installation.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 17, 2018, 02:13:02 am
That was a change introduced in FSO 3.8.0. I never was involved in that decision. IMO it was a very bad idea to silently introduce it and keep support for the old location.
I had to explain the same stuff so many times by now that I'm getting tired of it.
The FSO devs changed the settings location and Knossos (just like wxLauncher) uses the path dictated by the engine. If you don't like it, complain to the SCP. There's nothing I can do about it.

EDIT: Updated warning in the first post to make this fact clearer.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: m!m on June 17, 2018, 10:39:43 am
Well, I submitted a change which fixes that behavior over a month ago but no one approved the code so it was never merged. I merged the change just now so it should appear in the next nightly build.
The engine will then select the config location which was changed most recently.

Just FYI, there is a good reason for keeping the config data in AppData since that location is always writable by the engine which may not be the case for the local installation directory. I can understand why that change might be annoying to some users so the changes I merged should make FSO work more consistently if a user still wants to use an outdated launcher.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Spoon on June 17, 2018, 11:48:00 am
That was a change introduced in FSO 3.8.0. I never was involved in that decision. IMO it was a very bad idea to silently introduce it and keep support for the old location.
I had to explain the same stuff so many times by now that I'm getting tired of it.
The FSO devs changed the settings location and Knossos (just like wxLauncher) uses the path dictated by the engine. If you don't like it, complain to the SCP. There's nothing I can do about it.

EDIT: Updated warning in the first post to make this fact clearer.
Well you don't have to feel personally attacked or anything. I posted it here because I sort of assume that most of the relevant SCP members would look at this thread too.
You've done amazing work with knossos.

Well, I submitted a change which fixes that behavior over a month ago but no one approved the code so it was never merged. I merged the change just now so it should appear in the next nightly build.
The engine will then select the config location which was changed most recently.

Just FYI, there is a good reason for keeping the config data in AppData since that location is always writable by the engine which may not be the case for the local installation directory. I can understand why that change might be annoying to some users so the changes I merged should make FSO work more consistently if a user still wants to use an outdated launcher.
Sure, I get why appdata is picked, but I don't really get why this isn't just a thing the user can configure somewhere.
Either way, thanks for working on it.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: m!m on June 17, 2018, 12:22:44 pm
Sure, I get why appdata is picked, but I don't really get why this isn't just a thing the user can configure somewhere.
Either way, thanks for working on it.
When I wrote that code I underestimated how many people would be using old and new launchers at the same time. My thought process was that someone would use an old launcher and then upgrade to a new one and never switch back. That was accurate for most (but not all) users until Knossos appeared which supported the new location but some users still wanted to use their old launcher at the same time. Since, in my mind, the situation was that everything would be done automatically, there would be no reason to have a config option to customize this behavior.

Also, since FSO needs to determine from where to read the configuration data before actually reading that data it was impossible to check what the user specified in the launcher.

Anyway, this should hopefully be fixed now. Please let me know if the next nightly still shows the buggy behavior.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 17, 2018, 04:55:41 pm
@Spoon: Sorry, I was in a bad mood yesterday and the frustration got to me.
You've done amazing work with knossos.
Thanks!

If I added support for FSO's "-portable_mode" in Knossos, wouldn't that also solve the problem? The config files would once again be stored in FSO's root directory (which is already managed by Knossos anyway). I would just need to figure out how this would affect TCs since they use a different root directory than FS2 mods. Most likely I can just solve this by copying the config files.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Spoon on June 17, 2018, 05:01:03 pm
When I wrote that code I underestimated how many people would be using old and new launchers at the same time. My thought process was that someone would use an old launcher and then upgrade to a new one and never switch back. That was accurate for most (but not all) users until Knossos appeared which supported the new location but some users still wanted to use their old launcher at the same time. Since, in my mind, the situation was that everything would be done automatically, there would be no reason to have a config option to customize this behavior.

Also, since FSO needs to determine from where to read the configuration data before actually reading that data it was impossible to check what the user specified in the launcher.

Anyway, this should hopefully be fixed now. Please let me know if the next nightly still shows the buggy behavior.
Gotcha, I understand your thought process.
I'll let you know.

@Spoon: Sorry, I was in a bad mood yesterday and the frustration got to me.
You've done amazing work with knossos.
Thanks!

If I added support for FSO's "-portable_mode" in Knossos, wouldn't that also solve the problem? The config files would once again be stored in FSO's root directory (which is already managed by Knossos anyway). I would just need to figure out how this would affect TCs since they use a different root directory than FS2 mods. Most likely I can just solve this by copying the config files.
No worries, I understand it can be frustrating when you keep hearing the same issue that you can't do anything about.
When I tried the portable mode in the 5.5g launcher it didn't solve anything for me. No idea how or what it would do when added to knossos.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: AdmiralRalwood on June 18, 2018, 03:21:40 pm
If I added support for FSO's "-portable_mode" in Knossos, wouldn't that also solve the problem?
-portable_mode is kind of not working right; it should work if you combine it with -parse_cmdline_only, though.

EDIT:
When I tried the portable mode in the 5.5g launcher it didn't solve anything for me. No idea how or what it would do when added to knossos.
It can't work with the 5.5g launcher, because portable mode still doesn't use the registry; in fact, FSO being in portable mode will specifically make sure it doesn't use the registry.