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.13.3 (combined launcher/installer)
Post by: ngld on October 29, 2017, 10:14:17 am
Get ready for a new kind of FSO launcher!

Never heard of FSO, the SCP or mod.ini files?
Download Knossos and you'll be playing new mods within minutes! Just don't forget to tell us if Knossos helped you or if you had problems.

You've used wxLauncher for years, can write a mod.ini file in your sleep or have been using 5.5g since it was new?
Forget everything you know about launchers and embrace Knossos' new approach! It might be scary at first but trust me, change can be good. Knossos should be pretty self-explanatory if you use the dev tab to add mods and read the integrated help texts. Just know that we're here to help if you run into issues, get confused by all of the new stuff or get frustrated.
Don't use your existing FS2 installation as Knossos' data directory (where mods will be installed) since Knossos uses a new directory structure and isn't compatible with existing installations. It also doesn't support mod.ini files.



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. This issue is fixed in recent nightlies. If you want to use Knossos together with legacy launchers, use them!

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.
ALSO IMPORTANT if you're on macOS: Change your preferred stability in Knossos' settings to "nightly". The currently uploaded stable FSO build is broken.

Please keep an eye on your free disk space. If you try to install all available mods, you can easily end up with more than 100 GiB of files. If a mod installation fails, make sure you have enough free disk space left.

Another note: If you upload mods, please don't change your mod dependencies between minor versions (i.e. between 0.3.6 and 0.3.7) to avoid dependency conflicts. Whenever you change your dependencies, please increase either of the first two version numbers (according to the previous example, you'd end up with either 0.4.0 or 1.0.0).

If you're going to create or upload mods through Knossos, here's a helpful guide (https://docs.google.com/document/d/1oHq1YRc1eXbCgW-NqqKo1-6N_myfZzoBdwZuP16XImA/edit?pli=1#) which explains the whole process. If you have questions or problems, feel free to post here or on Discord.

Huge thanks to mjn.mixael for the excellent UI work without him Knossos probably would still look like this (https://dev.tproxy.de/kn/images/screen6.png).
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, there or in the #knossos channel on HLP's Discord (https://discord.gg/YNVP3WR).

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

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:

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.



[attachment stolen by Russian hackers]
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

[attachment stolen by Russian hackers]
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.



[attachment stolen by Russian hackers]
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.

[attachment stolen by Russian hackers]
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.

[attachment stolen by Russian hackers]
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.



[attachment stolen by Russian hackers]
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

[attachment stolen by Russian hackers]
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.

[attachment stolen by Russian hackers]
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.


[attachment stolen by Russian hackers]
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.

[attachment stolen by Russian hackers]
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]


[attachment stolen by Russian hackers]
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.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: m!m on June 20, 2018, 04:46:20 pm
I'm trying to play Trimurti but I get the following error message:
Code: [Select]
"<Mod "Trimurti" 1.1.0 (shv)>" requires "FSO" which is missing!
I definitely have an FSO build installed but I use the nightly stability in the settings so it may be related to that. Where does Knossos store its log file on Linux? I looked for it in ~/.local/share/knossos but that directory does not exist in my case.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on June 26, 2018, 01:57:03 am
Sorry for the late reply... The log should be in ~/.config/knossos. Solving the problem will be much easier with a proper log. My guess would be that either you no longer have the stable version of FSO installed (3.8.0) or Knossos somehow got confused with the various FSO versions and their stabilities.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: m!m on June 26, 2018, 07:24:39 am
I do have both versions of 3.8 installed but my stability setting is "nightly". When I set it to "Stable" the same error appears.

Here is the log:
Code: (log.txt) [Select]
INFO:MainThread:launcher.main: Running Knossos 0.11.0-dev+61b73bf on PyQt5 and Python 3.6.5 (default, Mar 29 2018, 18:20:46)
[GCC 8.0.1 20180317 (Red Hat 8.0.1-0.19)].
INFO:MainThread:launcher.main: OpenSSL version: OpenSSL 1.1.0h-fips  27 Mar 2018
DEBUG:MainThread:launcher.main: Loading resources from data/resources.rcc.
DEBUG:MainThread:launcher.main: Loading settings...
DEBUG:MainThread:util.call: Running ['7z', '-h']
WARNING:MainThread:integration.init: Failed to specify Unity version. Most likely Unity is not available.
INFO:MainThread:integration.init: Activating generic Linux integration...
DEBUG:MainThread:windows.watch_task: Task "Loading installed mods..." (139718982286792, <class 'knossos.tasks.LoadLocalModsTask'>) started.
DEBUG:MainThread:windows.watch_task: Task "Fetching mod list..." (139718982286936, <class 'knossos.tasks.FetchTask'>) started.
DEBUG:MainThread:windows._forget_task: Task "Loading installed mods..." (139718982286792) finished.
DEBUG:Thread-10:connectionpool._new_conn: Starting new HTTPS connection (1): fsnebula.org
DEBUG:Thread-10:connectionpool._make_request: https://fsnebula.org:443 "GET /storage/repo.json HTTP/1.1" 200 None
INFO:Thread-10:repo.add_mod: Mod "DWA1" (2.0.0-A) from "https://fsnebula.org/storage" overwrites an existing mod version!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20171029 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180302 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180419 (FSO)> is empty, ignoring it!
DEBUG:MainThread:windows._forget_task: Task "Fetching mod list..." (139718982286936) finished.

EDIT: I ran Knossos in a debugger and saw that in runner.py, line 301 an exception is thrown with the error message "No version of mod "FSO" found for these constraints: >=3.8.0-3 (FSO),* (FSO),>=3.8.0-2 (FSO),==3.8.0-2 (FSO)". It looks like there may be an invalid version specifier somewhere.

EDIT2: I found the package with the wrong configuration. The fsport "Content" package has a version specifier for FSO which says "3.8.0-2" but Trimurti has a specifier which says ">=3.8.0-3". Setting the fsport version requirement to ">=3.8.0-2" fixes the issue I reported.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: perihelion on July 03, 2018, 04:13:27 am
@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).
@ngld: Has there been any luck incorporating the fix for joysticks and SDL2 into Knossos?  I've tried to follow your instructions, but I must be doing it wrong somehow.  I found an old fs2_open.log and copied the GUID from there, but it is exactly the same as it is listed in my fs2_open.ini.  Only things I can think of is that this log file isn't as old as I thought it was, or that I'm not modifying the correct fs2_open.ini.  Is there a particular location I should be looking for these files?  I'm just using search and looking at whatever turns up.

Sorry, this is probably pretty basic stuff, but it has stopped me in my tracks.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on July 04, 2018, 02:40:59 am
I haven't been able to fix the joystick issue, yet. You need to copy the GUID from a new fs2_open.log. After all, the problem is that the newer builds use a different GUID than the old builds and Knossos still generates the old GUID. That's why the old log matches what your fs2_open.ini already had.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: perihelion on July 04, 2018, 04:23:12 am
 :banghead:
I knew it was going to be something obvious like that!
So, I should run a debug build in Knossos? Or do I need to run one from the wxlauncher?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on July 04, 2018, 04:25:57 am
Either will work.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: perihelion on July 04, 2018, 07:38:32 pm
That worked!  Thanks!
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nightmare on July 09, 2018, 08:58:42 pm
Is it possible to add something like "File was last updated on:" for those who are using the FSNebula links for regular (non-Knossos) installing?
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on July 09, 2018, 09:20:49 pm
Done. I've also added the version number.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Nightmare on July 09, 2018, 09:26:25 pm
Wow, that was quick! :)

Is it possible to have the dates also for the individual files? Because there are questions like this here: https://www.hard-light.net/forums/index.php?topic=94378.msg1870434#msg1870434 , and I remember that I had to re-DL Exile some time ago, while only a few files had been updated.
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: ngld on July 09, 2018, 09:36:10 pm
Both values (version and last updated) are already stored in the database as such it was easy to display them on the page (less than 20 lines change).
I don't store when individual files are uploaded. I'd have to check past releases and then check if the package was changed since then. I'll probably add it but it might take a while.
Title: Re: PUBLIC BETA: Knossos 0.11.1 (combined launcher/installer)
Post by: ngld on July 09, 2018, 11:45:11 pm
So... I finally got another release done. This one fixes a the usual bugs that were reported and also adds a bunch of new things:


This release is 0.11.1 (with no 0.11.0 announced here) because I ran into a problem with the Windows build of Knossos:
The Windows build has been 32bit so far to ensure compatiblity with both 32bit and 64bit computers. One of Knossos' dependencies (PyQt5) is missing a few components in its latest 32bit release. I can't find any official announcement so I'm not sure if it's intentional or an accident. However, if it's intentional, I won't be able to provide 32bit Windows builds in the future. For the time being, I've solved the issue by staying on an older version. Now my questin is: Would this actually be an issue for anyone here? I plan on having the next version of Knossos automatically report the system's architecture (32/64bit) to see how many would be affected by this change but I wanted to ask beforehand.
Title: Re: PUBLIC BETA: Knossos 0.11.1 (combined launcher/installer)
Post by: Airborne2 on July 10, 2018, 03:26:41 pm
I'm having an issue with in game resolution. After updating Knossos yesterday it doesn't matter which mod I run, the game will always run at my native desktop resoultion (2560 x 1440) no matter what I set it to in Knossos options. I scale down my in game resolution so I can read the text much easier. Any ideas on how to fix this? it worked before updating.
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: ngld on July 12, 2018, 02:27:02 am
@Airborne2: Can you tell me what VideocardFs2open is set to in your %appdata%\HardLightProductions\FreeSpaceOpen\fs2_open.ini?

I've released 0.11.2 which fixes a few UI bugs, allows you to save packages once again (weird bug caused by outdated dependencies on the CI) and reports your processor's architecture.
Since no one complained about it since my last post, I'm assuming that 64bit builds won't be a problem but I'll wait a few weeks before I make any decision on that matter.
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: Airborne2 on July 12, 2018, 04:03:48 am
It says OGL -(1360x768)x32 bit which is what I'm trying to run it at but it doesn't seem to be working.

On a side note is sorting mods using the option in the upper right of knossos not fully implemented yet?

 Edit:After some more testing it actually does seem to be running at the proper resolution but the UI isn't scaling properly in every mod. For reference I first installed Inferno: nostos and finished that, then Exile and finished that followed by blue planet complete. I recently installed between the ashes and that's when I first noticed it. I thought it was just that mod but exiles UI is small now as well where it wasn't before. It's also possible exiles UI was always that small and I've just already forgotten that. either way this issue seems to with the UI itself and not the games resolution which might not even be related to knossos.
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: ngld on July 12, 2018, 04:12:54 am
It says OGL -(1360x768)x32 bit which is what I'm trying to run it at but it doesn't seem to be working.
Not sure why it's not working then. Knossos is doing exactly what it should. FSO is just ignoring it. You can try putting -res 1360x768 in Settings > Global Flags > Custom Flags and hit "Apply to all".

On a side note is sorting mods using the option in the upper right of knossos not fully implemented yet?
No, it's one of the things that aren't finished, yet. I also have a tagging system planned which will allow you to filter the mod list by TC, engine builds and other stuff (like language).
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: Airborne2 on July 12, 2018, 04:25:48 am

No, it's one of the things that aren't finished, yet. I also have a tagging system planned which will allow you to filter the mod list by TC, engine builds and other stuff (like language).

I'll be looking forward to that. I was interested because it seems at least one new mod was added to the list but I don't know which one.

Also I edited my previous post if you could look at that.
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: ngld on July 12, 2018, 04:49:04 am
Mods can tweak the HUD (including its size). Here's one example that might help you (https://www.hard-light.net/forums/index.php?topic=91197.0).
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: wistler on July 14, 2018, 11:41:46 am
Hi,

I've come back to FreeSpace after a long time and wanted to say that Knossos looks dope! You guys have done a great job.
I had an issue with downloading Knossos as it was flagged by Norton and Windows Defender as being unsafe (and auto deleted). This might new people off from downloading and proceeding past that point.
This point might have been raised earlier in the thread (I wouldn't know as i never learnt how to read!  :shaking: )

Keep up the good work.
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: ngld on July 14, 2018, 07:26:08 pm
AFAICT most AV programs consider Knossos "unsafe" or w/e because it's a "rare" file (which means that not too many people used it).
According to virustotal only 2/65 AV programs consider the installer suspect (https://www.virustotal.com/#/file/91962b481f04ef7705bda36933e29e3d166345a26c7dec34d94ed298e3e197d0/detection) and 4/68 think that Knossos itself (https://www.virustotal.com/#/file/d1302508cd27df90f35175019a08eff68d08fb4da260ea3e1f7ba5435d70150f/detection) looks suspicous.

Some of the tools I used to package Knossos (NSIS and PyInstaller in particular) have been used by malware authors as well but that alone shouldn't be enough to make a file supicious. The best way to find out why your AV flagged Knossos would be to ask your AV vendor. In any case, I can't really do anything about it...
Title: Re: PUBLIC BETA: Knossos 0.10.1 (combined launcher/installer)
Post by: Novachen on July 14, 2018, 08:14:31 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.

@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: ..." ?

The new error message is much clearer.
The problem for the said mods is, that all of them require a ==3.8.0-2 version of FSO... so they do not support a newer version, which is conflicting if i create a mod for them that is using a Nightly one, not to say about, that Knossos uses 3.8.0-3 by default now.
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: ngld on July 14, 2018, 11:49:40 pm
I'll reach out to the mod uploaders and tell them to fix that. I guess we'll need some proper guidelines on dependencies (as a rule of thumb, you should always allow newer versions of FSO but keep most mod dependencies locked to their current version).
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: jr2 on July 16, 2018, 01:41:05 am
Hi,

I've come back to FreeSpace after a long time and wanted to say that Knossos looks dope! You guys have done a great job.
I had an issue with downloading Knossos as it was flagged by Norton and Windows Defender as being unsafe (and auto deleted). This might new people off from downloading and proceeding past that point.
This point might have been raised earlier in the thread (I wouldn't know as i never learnt how to read!  :shaking: )

Keep up the good work.

I think there's a way to submit the file for review or somesuch.  If not you could just contact the AV vendor and tell them it's a false positive.
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: kylekatarn77 on July 16, 2018, 03:56:45 am
For FSPort MediaVPS, the field where video should play during briefings in-between missions (As in story events, introducing new weapons, etc) is blank and there is no voice audio. There is also no voice audio during the level briefing or the level itself- sound effects work just fine though.
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: mjn.mixael on July 16, 2018, 02:58:23 pm
For FSPort MediaVPS, the field where video should play during briefings in-between missions (As in story events, introducing new weapons, etc) is blank and there is no voice audio. There is also no voice audio during the level briefing or the level itself- sound effects work just fine though.

The voice files and animation files are separate optional downloads. If you go to FSPort MediaVPs, click the dropdown, click Modify, then check the boxes for the option VPs, they should start working for you.

EDIT: FSPort is a confusing piece of **** mess. I may have been wrong. You should follow the steps to modify your FSPort install as well. Make sure to install all the optional VPs there.
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: Bryan See on July 17, 2018, 11:36:54 am
Is there any permanent fix on this?
Title: Re: PUBLIC BETA: Knossos 0.11.2 (combined launcher/installer)
Post by: ngld on July 17, 2018, 12:45:30 pm
For what problem? If you're talking about the FSPort issue, it should be working with all the relevant packages installed. If it's not working even with that, then there is a bug in Knossos and we'll have to look for a fix.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: ngld on July 24, 2018, 03:29:38 pm
Version 0.12.0 has been released. macOS and Ubuntu builds will follow in a few days (both failed on the CI and I can't build them manually right now).

This release introduces a major UI change: We now have a custom title bar! If you don't like it or it doesn't work (i.e. you're seeing two title bars), you can go to the settings screen and disable it there. Huge thanks to mjn for the design and the icons!
Mod menus have a new "Open Debug Log" button which does exactly what it says on the tin.
m!m improved the "Apply To All" button in the global FSO flags section. It now does its work in the background instead of freezing Knossos (particularly noticable if you have a lot of FSO builds installed).
mjn also fixed the Save buttons, they no longer move around when a save confirmation popped up.

Oh, and you no longer have to be logged in to upload debug logs.

Finally, according to my statistics out of over a hundred users, only 2 are using a 32bit processor. Since nobody has complained since my last announcement regarding this, I'll switch to 64bit Windows builds if it becomes necessary.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: Nightmare on July 24, 2018, 03:38:31 pm
But 2 32bit users isn't "none"; you might want to keep a working 32bit version available, even if you don't continue development for that system anymore. (I have a 32bit system, but I don't use Knossos, so it's not a problem for me but for others it might be).
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: wookieejedi on July 24, 2018, 03:47:43 pm
In fairness, I think he meant that "nobody mentioned" having 32 machines only. Though having an archived, no longer supported 32 verison is probably not a bad idea if that means the rest of us 64 users can have an updated, faster version  :D
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: ngld on July 24, 2018, 03:52:25 pm
All releases since 0.5.0 are available on GitHub (https://github.com/ngld/knossos/releases) and I have no intention of taking those down. However, if I do switch to 64bit builds, I won't keep updating the 32bit builds (sorry, I simply don't have the time to maintain two versions of Knossos) and they might eventually stop working due to changes to the Nebula server.

That said, I don't have any plans to switch in the immediate future. The problem that prompted me to consider switching is that the main UI component for Knossos (QtWebEngine) only offers 64bit builds in its latest release (at least through PyQt5). I'm not sure if it's intentional and if future releases will include 32bit builds again or not. However, if PyQt5 drops support for 32bit QtWebEngine, I will eventually be forced to switch to 64bit builds if I don't want to be stuck on an old version. For now, I'm sticking to the last release with 32bit QtWebEngine.

EDIT: "nobody has complained" was in reference to my question two weeks ago. I asked if it would be a problem for anyone if I switched to 64bit builds. Nobody has responded to that.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: Nightmare on July 24, 2018, 04:03:34 pm
I had the feeling that not all people coming to HLP and playing the mods here necessary register an account (mostly when they have problems, or don't have Discord), so asking the people on the forum might not cause someone affected to complain.

It might be useful that when switch to 64bit only, you could provide a link, with something like "32bit is no longer supported/developed, but you can find a working built here:".
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: mjn.mixael on July 24, 2018, 04:17:05 pm
It honestly surprises me that even 2 people (3 with Nightmare) in 2018 still have a 32 bit computer... limited to 4gb of RAM. Yeesh.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: Nightmare on July 24, 2018, 04:21:41 pm
Well my i7 was state-of-the-art, back in 2011...
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: Spoon on July 24, 2018, 04:39:56 pm
Well my i7 was state-of-the-art, back in 2011...
If you have a i7 from 2011, then the only thing limiting it to 32bit would be if you still ran windows xp or something. I mean, my desktop is also an i7 from 2011, and it has 16gb ram and is fully 64bit and all that jazz.

IMO good call to drop support for 32bit at this point.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: mjn.mixael on July 24, 2018, 04:50:34 pm
Uh.. yeah. If you have an i7, then you have a 64-bit capable chip. You're limited by your OS (either old or you installed the wrong version).
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: chief1983 on July 24, 2018, 05:03:20 pm
Some 64-bit capable computers that came with less than 4GB of RAM from the manufacturer shipped with 32 bit OS versions.  Someone could have gone from Windows 7 32-bit to Windows 10 32-bit via the free upgrade offer and still be on fairly modern hardware and software, but still locked into 32-bit land.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: Nightmare on July 24, 2018, 05:10:23 pm
Whoops...... when I bought that thing I had a lot of 32bit games so I used that 32bit version and continued that from WinXP over Win7 and Win10 for some reason.... :warp:
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: mjn.mixael on July 24, 2018, 06:10:00 pm
I believe there's a way on Win10 to "upgrade" to the 64bit version. Would have to Google it.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: Nightmare on July 24, 2018, 07:35:40 pm
Yeah I think there is. But thanks for the reminder everybody, I totally forgot about it. :)
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: jr2 on July 26, 2018, 02:01:39 am
The "upgrade" path for x86 to x64 of any version of Windows is to do a clean install of x64 of the same revision of Windows (eg, if you had x86 Win 7 Home, do x64 Win 7 Home) and you should be able to use the same key and keep it activated.  Of course this is on the same machine, not a new one (unless you have retail, then I think as long as you aren't using the old x86 version any more, you might have to call M$ and explain, but you should still be good?)

https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/is-a-windows-7-license-key-valid-for-both-32-bit/70d546cd-b6e3-44d8-a6c8-fd7feb7d1915

https://superuser.com/questions/979528/is-a-product-key-for-32-bit-windows-compatible-for-64-bit-windows
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: OverDhill on July 30, 2018, 07:55:58 am
Is Knossos installing the upgraded movies?  I manually installed them for my wxLauncher installation and they seem to be working but the Knossos intro doesn't seem to be the updated one.

Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: ngld on July 30, 2018, 01:00:39 pm
Upgraded movies for which mod? Knossos will use whatever the mod dev told it to use. If you manually install the cutscenes, it should work (assuming you're placing them in the correct folder).
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: OverDhill on July 30, 2018, 02:36:44 pm
Sorry forgot to mention it is the ones for FS1. 

https://www.hard-light.net/forums/index.php?topic=68161.0

Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: mjn.mixael on July 30, 2018, 02:57:19 pm
I'm pretty sure FSPort has not included them in any official release or patch. You'll have to bother Goober5000 for that.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: ngld on July 30, 2018, 04:38:24 pm
The FSPort MediaVPs include the cutscenes. Make sure you're using them and have the "movies" package installed (you can check by clicking the modify button for the FSPort MediaVPs on your Explore tab).

EDIT: I haven't checked which cutscenes are included in that package. If you have it installed and the cutscenes are still not showing up, you'll have to ask Goober5000 or someone else on the FSPort team about it.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: tomimaki on August 01, 2018, 10:22:06 am
Do I need Nebula login to report problems with mods?

In this case installing Wing Commander IV Demo doesn't add Wing Commander Saga.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: Novachen on August 01, 2018, 11:51:44 am
In this case installing Wing Commander IV Demo doesn't add Wing Commander Saga.

Because Wing Commander Saga is not needed for it iirc.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: PIe on August 01, 2018, 05:49:13 pm
The WCIV demo does require WCS to be installed.
However, though you don't need to login to report a mod, the fact that you can install WCIV without first installing WCS and you can uninstall WCS without first uninstalling WCIV seems more like a problem with Knossos than those mods.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: mjn.mixael on August 01, 2018, 08:29:00 pm
Pretty sure it's a problem with the mod. For example, if you install Silent Threat: Reborn. You cannot uninstall FSPort MediaVPs because ST:R needs it. Knossos warns you and will not uninstall.

And I just checked. WCIV does not require Knossos install WCS. If WCIV requires WCS, then the dependencies are wrong in the mod.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: PIe on August 02, 2018, 05:35:09 pm
And I just checked. WCIV does not require Knossos install WCS. If WCIV requires WCS, then the dependencies are wrong in the mod.
WCIV will not run without WCS installed.  If you were just looking at the dependencies, then WCS won't be there because it's not a dependency.  It's the parent TC, just like retail FS2 is the parent game for most mods.  The relevant line is
Code: [Select]
"parent": "Wing_Commander_Saga",
Pretty sure it's a problem with the mod. For example, if you install Silent Threat: Reborn. You cannot uninstall FSPort MediaVPs because ST:R needs it. Knossos warns you and will not uninstall.
Right, that's why I said I think it's a problem with Knossos.  Because WCIV does require WCS to work, you shouldn't be able to uninstall WCS while having WCIV still there.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: mjn.mixael on August 02, 2018, 09:24:23 pm
Then why does choosing to install WCIV not force installation of WCS? As far as I can tell, Knossos doesn't really know the two are connected.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: ngld on August 03, 2018, 11:05:37 pm
I remember that I changed how TC mods worked quite a while ago. They now have to have a dependency on their TCs (if they don't, it's automatically added during upload).
This might be an old mod from before the change. The missing dependency probably caused all the mentioned problems.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: OverDhill on August 04, 2018, 05:46:35 pm
Is it possible to use the Shield Management script with Knossos and if so where do we place the files?

http://wiki.hard-light.net/index.php/Script_-_Shield_Management
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: Nightmare on August 04, 2018, 05:54:00 pm
.tbm files go into tables, .lua files into scripts. Interface is missing, and I'm not sure if the version on the wiki is broken/outdated too (last update 2011).

There was a simmilar discussion about using "extension-type"-mods on Knossos here: https://www.hard-light.net/forums/index.php?topic=47069.msg1871292#msg1871292

Edit: I think most scripting examples on the wiki are broken, if you're looking for scripts to play with grab JAD/BP/BTA or something like that...
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: OverDhill on August 04, 2018, 06:06:46 pm
The reason I was asking is there doesn't seem to be a script folder in my Knossos install.  Also the shield script works with the latest builds under wXLauncher
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: ngld on August 05, 2018, 01:22:36 pm
You can create the script folder yourself (either in FS2/data/scripts or FS2/<mod>/data/scripts). Except for a few specific cases (like TCs and dev mods), the FS2 folder in Knossos works like the FS2 installation folder with wxLauncher.
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: OverDhill on August 05, 2018, 02:03:02 pm
I already tried that and the shield balance graphics are nowhere to be seen on the screen.

I know this works under 3.8 with wxLaucher

Could you see if you can see why they are not working

[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.12.0 (combined launcher/installer)
Post by: ngld on August 05, 2018, 02:55:33 pm
The script loads fine when started through Knossos. I didn't see anything though (probably because the images were missing). However, this doesn't look like it's Knossos' fault.

If you want to find out why it breaks, I'd suggest creating a debug log and seeing if you can find a difference between the one produced by FSO run through Knossos and when it's run through wxLauncher.
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: ngld on August 08, 2018, 02:10:57 am
Knossos 0.12.1 has been released. This release fixes a bug which prevented some people from starting FRED and launching FSO from FRED.
I've increased the timeouts used for network requests which should solve a lot of the recent upload problems.
m!m contributed a patch which allows Knossos to work without the cmdline_fso.cfg. This shouldn't have any consequences for non-coders but let me know if this broke anything.
The version number is once again displayed in the title bar (it vanished after I implemented the custom title bar). Not sure if I'm going to leave that as it is. I'll probably make the version number smaller.
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: jr2 on August 10, 2018, 02:37:09 pm
Knossos 0.12.1 has been released. This release fixes a bug which prevented some people from starting FRED and launching FSO from FRED.
I've increased the timeouts used for network requests which should solve a lot of the recent upload problems.
m!m contributed a patch which allows Knossos to work without the cmdline_fso.cfg. This shouldn't have any consequences for non-coders but let me know if this broke anything.
The version number is once again displayed in the title bar (it vanished after I implemented the custom title bar). Not sure if I'm going to leave that as it is. I'll probably make the version number smaller.

Make the version number appear on titlebar mouseover.  Just because.  ;)  (Not sure if that's the brightest idea, though, as it probably makes troubleshooting easier if it's always on.)
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: OverDhill on August 10, 2018, 06:49:20 pm
Thanks for the help fixing the Shield Management. It was my error. Been so long since I added this I forgot about the interface folder. It works now. Thanks
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: Mongoose on August 11, 2018, 05:08:42 am
One tiny quibble when updating: the little pop-up that prompts for the update has the yes/no buttons as the same color as the background, so it's very difficult to tell if you're clicking on the actual button or not.
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: mr.WHO on August 12, 2018, 08:55:03 pm
Hi, after update to 0.12.1 I have "failed to save configuration" error when I try to run anything or save Knossos settings.
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: Andreas Rybak on August 12, 2018, 09:18:08 pm
Another issue - Knossos says there's an update for Revenge: Final Conflict. When I click the 'update' button, I get this error:

"A critical error occurred! Knossos might not work correctly until you restart it. This error has been reported and will hopefully be fixed soon."
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: ngld on August 13, 2018, 12:21:13 pm
@OverDhill: You're welcome!

@Mongoose: An unintended side-effect of changing the main window's colors (which was necessary for the new titlebar). I'll fix this in the next version.

@mr.WHO: Your case is an interesting one... When Knossos tries to write the fs2_open.ini, it fails because your audio device contains characters which aren't part of ISO-8859-1 (the default Windows encoding). I'll either have to replace the characters or check if FSO is fine with having the ini UTF-8 encoded.

@Andreas Rybak: As far as I can tell, something went wrong during the last installation of that mod. In any case, Knossos can't find the old version during the update. Not sure what's happening. The easiest solution for you would be to reinstall the mod. If you want to help me solve the issue, do the following first: Start the update and close Knossos after the error occurs. Send me your %APPDATA%\knossos\log.txt and the mod.json in your <data path>\FS2\revenge-1.1.0-BETA3 folder.
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: Novachen on August 13, 2018, 12:25:41 pm
Mh because i am in charge for Revenge: Final Conflict on Knossos i am actually curious about that.

Because the only change i did to the previous version was an updated VP. So i do not have a clue what went wrong there, because i do not get such error messages as the "developer".
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: mr.WHO on August 13, 2018, 02:38:18 pm
@mr.WHO: Your case is an interesting one... When Knossos tries to write the fs2_open.ini, it fails because your audio device contains characters which aren't part of ISO-8859-1 (the default Windows encoding). I'll either have to replace the characters or check if FSO is fine with having the ini UTF-8 encoded.

Strange - previous version of Knossos worked fine with my configuration.

Another issue - Knossos says there's an update for Revenge: Final Conflict. When I click the 'update' button, I get this error:

"A critical error occurred! Knossos might not work correctly until you restart it. This error has been reported and will hopefully be fixed soon."


Same here, but for Media VP.


Also when I try to run anything or FRED I also have some error message but the error window is transparetn so I don't if it's "failed to save configuration" or something else.

Is it possible to revert back to previous version od Knossos?
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: deathspeed on August 13, 2018, 04:11:16 pm
A while back there was talk of Knossos being modified to use existing installations, and/or an FAQ for existing users transitioning to Knossos.  My apologies if those are done and I just am not finding them.  I know it was lower priority to bug fixes.  I'm thinking about taking the plunge, but I would really rather not re-download the 57GB of mods I already have if possible.  Here are a few questions I have:

If I do have to re-download everything (I realize I don't have to do it all at once), should I delete the existing mod folders in my freespace2 directory? 
Delete anything else in that directory? 
If so, delete before or after using Knossos? 
Does Knossos let me choose my directory? My Windows (c:) drive is a smallish SSD, so my current installation is on another physical drive.  I CANNOT use c:\program files. 
Should I use a directory for Knossos that is different from the legacy directory I am currently using?  My current retail FreeSpace 2 installation is from ancient CDs.  I still have them, but I am always concerned that they may not load or be recognized by my PC.
Will my mod progress automatically be saved from the legacy installation?

These are the questions I can think of now, but I may have more later.  :)

Thanks, and awesome work!!
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: chief1983 on August 13, 2018, 04:16:52 pm
I have machines with both a Knossos install and a traditional install side by side.  I haven't had any issues with that yet.  If you want to test Knossos, it won't likely interfere with your existing install, aside from some possible issues people have reported with the shared config setup.  But I personally haven't had those, and it's probably isolated to certain versions.  I stick with nightlies and it's gone well for me.  You could leave your existing install alone and just install Knossos mods as you get to them.  I don't even think you'd need to do anything with your pilots/gamesaves if they are using the shared location.  But you may want to make a backup of your FS2 appdata folder just to be safe if you have a lot of pilots/saves you don't want to lose.
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: ngld on August 13, 2018, 06:07:55 pm
First of all to everyone trying to update the Media VPs (or other mods) and getting a critical error: I've found the bug and I'm working on a solution (hopefully done within a few hours).



@mr.WHO: Huh, not sure why it worked in the past. Maybe the new builds are using a newer Python version which changed that behaviour...

@deathspeed: Knossos still can't automatically import old mods. I haven't had any time to implement that (and noone else did it either). However, as chief pointed out, you can use it along with your existing launcher. If you use recent nightlies, it works fine even with older launchers.
You can choose the directory where the mods are installed. In fact, people really shouldn't use C:\Program Files for that since it complicates a few things. Please note that this directory is separate from the location where Knossos is installed. You can select both, one during installation and the other on first run. You should also use a new directory since Knossos has a different directory structure. It will copy the retail VPs from your old directory if you point Knossos towards it when it asks you to.

If you've used FSO 3.8.0 in the past, your pilots and mods will be carried over. Otherwise, you'll have to run the latest version of wxLauncher once to migrate your pilots.
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: mr.WHO on August 13, 2018, 06:16:16 pm
@ngld: Will you be able to fix my issue, if yes then what will be the eta for fix (no hurry on my side, I can wait)?
Title: Re: PUBLIC BETA: Knossos 0.12.1 (combined launcher/installer)
Post by: Andreas Rybak on August 13, 2018, 07:06:13 pm
@Andreas Rybak: As far as I can tell, something went wrong during the last installation of that mod. In any case, Knossos can't find the old version during the update. Not sure what's happening. The easiest solution for you would be to reinstall the mod. If you want to help me solve the issue, do the following first: Start the update and close Knossos after the error occurs. Send me your %APPDATA%\knossos\log.txt and the mod.json in your <data path>\FS2\revenge-1.1.0-BETA3 folder.

A bit late, admittedly - I managed to get it to successfully update. While it would not update if I clicked the button on the Home page, going to the Explore page and clicking Modify, then accepting, allowed the mod to update fine. If it's alright to throw a suggestion out, would it be possible for Knossos to remove older versions of a mod from the FS2 folder? Otherwise it just seems like they'll end up bloating the folder.

EDIT: With the update to the MediaVPs, I get the same issue. Clicking the Update button on the Home page gives me the exact same error. Closing Knossos and going to the folder in question doesn't show a log.txt file in there even after repeatedly experiencing the same error several times. As before, going to Explore, clicking on Modify, and clicking "Okay" allows it to install with no issues.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: ngld on August 13, 2018, 07:24:50 pm
Knossos 0.12.2 has been released. This should fix the bugs mentioned in the last posts. Let me know if I missed anything!

@Andreas: You installed a new version instead of updating the mods which is also the reason you still have the old versions installed (and why it worked). To uninstall the old versions go to Home > Mod > Details > select the version in the top-left corner > Options > Uninstall.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: mr.WHO on August 13, 2018, 08:44:03 pm
The update is working - thanks for quick fix.

One thing I noticed now that the Inferno mod now show me two HUDs during the game (one bigger and one smaller), but I'll ask Inferno guys about it - I checked the FS port mod for reference, but it seems to work fine.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: Andreas Rybak on August 13, 2018, 10:23:02 pm
Another issue coming up, this one with Friends and Foes: Retribution. The error in question is as follows:

"Friends and Foes: Retribution" (1.1.0-REPACK) requires "FSO" which has conflicting requirements: >=3.8.0-2 (Friends and Foes: Retribution),==3.8.0-2 (Blue Planet Complete),>=3.8.1-20180811 (MediaVPs)

Any attempt to modify it gives this error:

I'm sorry but you won't be able to install "Friends and Foes: Retribution" because "FSO" is missing!

FSO is installed, however.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: Novachen on August 13, 2018, 10:37:42 pm
There are several mods that have this problem.

They all want the 3.8.0-2 Build ONLY.

So the problem here is, FaF uses 3.8.0-2 or higher, BP only with 3.8.0-2 and nothing else and the MediaVPs are runable only with a FSO build 3.8.1-20180811 or newer.

So the Problem is Blue Planet here that does not accept any newer build.

As i said, this problem is present with some other mods aswell unfortunately. The invidiual uploaders mixed up their settings and so you have to wait that they update their meta data.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: tomimaki on August 13, 2018, 10:46:35 pm
 
Code: [Select]
           "dependencies": [
                ...
                {
                    "version": null,
                    "id": "MVPS",
                    "packages": []
                }
            ],

Probably this is the cause of a problem for Inferno. Version should be "3.7.2"
Without it Knossos chooses highest possible version of MVPS for Inferno which is 3.8.0 right now.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: Nightmare on August 13, 2018, 10:55:55 pm
I'm having the double-HUD problem on 3.8.1 Nightly from 21.7.2018 as well, so it's not Knossos-related.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: tomimaki on August 13, 2018, 11:28:56 pm
It is not.
I say deps in mod.json for Inferno should looks like this:
Code: [Select]
"dependencies": [
                ...
                {
                    "version": "3.7.2",
                    "id": "MVPS",
                    "packages": []
                }
            ],
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: hirmuolio on August 14, 2018, 06:58:21 am
I already pointed the problem of strict FSO version requirements some time ago.

"version": "3.8.0-2" will run 3.8.0-2 only and refuse to run on newer version even if you try.

"version": ">=3.8.0-2" will run just fine on newer version if you set them to.

I don't think the first one is good. You can't know if a mod will be incompatible with a future release beforehand.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: deathspeed on August 14, 2018, 05:15:52 pm
Thanks for the responses! 

It's not so much that I am interested in testing Knossos, but some of the newer things out there have not been made available for Goober's installer and I don't care for manual installs.  I know Knossos is the future, and I truly think it is awesome, but I was preferring to wait until a non-beta release to start using it. 

That being said, I may go ahead and start using it in parallel with my existing install base and wxLauncher.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: ngld on August 14, 2018, 08:01:44 pm
@Andreas Rybak: As others pointed out, that's a problem with the dependencies set by the involved mods. I'll write up some guidelines for mod devs to prevent these issues in the future. However, the rule of thumb is: Allow newer versions only for FSO and not for other dependencies and always select an exect version for those.

@deathspeed: At this point, there are only a few bugs and one missing feature left until I'd call Knossos "stable". It'll probably take a while for that to get implemented but Knossos should be stable enough for daily use at this point. It's just not complete.

In case anyone's wondering about the critical error which still affects some people: I haven't been able to reproduce the issue myself and I can't find it among the other automated error reports. If anyone is able to reproduce it, please press Win+R and enter %appdata%\knossos\log.txt and upload it here or on Discord. Knossos clears that log on every start so make sure that you don't restart Knossos between seeing the error and uploading the log. You can open the file by other means as well but I guess this is the fastest (and easiest) way.
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: hirmuolio on August 14, 2018, 08:34:57 pm
Here is the log from critical error.
This was when trying to update MediaVP.

Code: [Select]
INFO:MainThread:launcher.main: Running Knossos 0.12.2 on PyQt5 and Python 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)].
INFO:MainThread:launcher.main: OpenSSL version: OpenSSL 1.0.2o  27 Mar 2018
INFO:MainThread:integration.init: Activating Windows integration...
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180725 (FSO)> is empty, ignoring it!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\windows.py", line 794, in install
  File "C:\knossos\knossos\tasks.py", line 927, in __init__
AttributeError: 'Mod' object has no attribute 'dev_mode'
Title: Re: PUBLIC BETA: Knossos 0.12.2 (combined launcher/installer)
Post by: mjn.mixael on August 14, 2018, 08:40:44 pm
Similar Error

Code: [Select]
INFO:MainThread:launcher.main: Running Knossos 0.12.2 on PyQt5 and Python 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)].
INFO:MainThread:launcher.main: OpenSSL version: OpenSSL 1.0.2o  27 Mar 2018
INFO:MainThread:integration.init: Activating Windows integration...
WARNING:Thread-6:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180725 (FSO)> is empty, ignoring it!
WARNING:Thread-14:repo.query: Repo.query(): Expected Spec but got Version instead! (Version('3.8.0-3', partial=True))
INFO:Thread-10:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/72/a5/316d08a743a35dc144284b9fb9a466ee259e0b22756cd2a032986951527e.png"...
INFO:Thread-10:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/a7/ef/48f47a06031b010b7acf9ca2d5dececb7af9177ee72f7ba5a7a0288f205a.png"...
INFO:Thread-1:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/24/5d/8ffd571bd7453769cc55482fb3eb72602086c2da3668aa3b5579440b5ad5"...
INFO:Thread-4:util.download: Downloading "https://cf.fsnebula.org/storage/28/ac/236ff8d2ed0ecb86ff1879e4cc76de469326464973f915d5c4b2942b74ea"...
INFO:Thread-10:util.download: Downloading "https://cf.fsnebula.org/storage/45/41/8e0cf2c98ab621bd931ead1755da73ed545574bd6dff6cf3f79a9538906c"...
INFO:Thread-9:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/75/04/92c49e1e228c093f2ac4aa6cea6f0caf010a83f548415f33dc3e5a687802"...
INFO:Thread-2:util.download: Downloading "https://fsnebula.org/storage/32/7a/23e37b8e4614c9d96d12b1cd47608a5f8c94f0cf768851e9d0966b7bbfb8"...
INFO:Thread-5:util.download: Downloading "https://fsnebula.org/storage/7e/5a/345b8145e6598d2e53a9e838706db0dc645d4d0ecf1312a73d142cf6d8d0"...
INFO:Thread-7:util.download: Downloading "https://fsnebula.org/storage/47/35/00db5982a595315870d97251b815fc3b3ed200a346d16a77880ed2c5bf02"...
INFO:Thread-8:util.download: Downloading "https://cf.fsnebula.org/storage/3a/49/693b3bb8f9c4337871f217de44ce2c8582f8b4a7f371c787af63ee60a820"...
INFO:Thread-6:util.download: Downloading "https://cf.fsnebula.org/storage/2b/9a/7617fd8dd91d4d8ca859586faab8c594bcab0136458e4d5136b3590cc52b"...
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\windows.py", line 794, in install
  File "C:\knossos\knossos\tasks.py", line 927, in __init__
AttributeError: 'Mod' object has no attribute 'dev_mode'
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 15, 2018, 08:59:50 am
Thanks, that helped a lot!

Knossos 0.12.3 has been released. It should finally fix the update error as well as a problem with mod installations on case-sensitive filesystems.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Andreas Rybak on August 16, 2018, 01:14:15 am
Some issues with Neo-Terra Victorious. I get a ridiculous amount of errors when starting the campaign - 987. On startup, before the opening cutscene even shows, I also get multiple errors relating to parselo.cpp for it, Shadow Genesis, Titan Rebellion, and several other campaigns too.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: mjn.mixael on August 16, 2018, 01:32:59 am
Some issues with Neo-Terra Victorious. I get a ridiculous amount of errors when starting the campaign - 987. On startup, before the opening cutscene even shows, I also get multiple errors relating to parselo.cpp for it, Shadow Genesis, Titan Rebellion, and several other campaigns too.

These are going to be errors with the campaigns and not really Knossos. These need to get to the mod author.

@ngld; perhaps we should think more seriously about a "report mod issue" button that sends an email or something to the mod author.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Iain Baker on August 16, 2018, 09:57:55 pm

 
View Profile NOMAD's Reviews Email Personal Message (Online)
Missing mods? on: August 16, 2018, 09:28:49 pm
QuoteModifyRemove
Hi there, me again!

During my Knossos binge I noticed that several mods no longer appear in the 'explore' window. These were English and German language upgrades to FSPort/FS1, Silent Threat Reborn and I think one other. Any idea what happened to them? Was there a problem with them?

Cheers :-)
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 16, 2018, 10:09:47 pm
The mods were removed by the same person who uploaded them. I think most (if not all) of the mods you mentioned were uploaded by Novachen. You'll have to ask her why she removed them.

Regarding the other thread you posted: The error message is a bit misleading. The problem there is that Knossos detected a dependency conflict which it couldn't resolve and thus can't proceed with the installation. In that case it was probably caused by the new MediaVPs release. Usually the situation looks like this: A mod requires both Blue Planet: Complete and the MediaVPs. Blue Planet: Complete wants FSO 3.8.0-2 and the latest version of the MediaVPs wants a recent nightly. Knossos can't find a version of FSO which matches these conditions (since it's impossible) and thus reports that FSO is missing.

I've already thought about implementing a better dependency resolver. If Knossos could determine that an older version of the MediaVPs (3.7.2 instead of 3.8.1) would resolve the conflict, it could use that instead. However, once you start implementing this as an algorithm you'll quickly notice that it becomes VERY complicated since it's a recursive problem (each mod version can have different dependencies thus the version you select for one dependency can affect other dependencies).
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Iain Baker on August 16, 2018, 10:13:36 pm
FYI Captains has been fixed :-)

Thanks for reporting this.  The Battle Captains should be fixed now but I don't have control over Vengeance of the Cosmos so I can't do anything about that.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: SamVision on August 18, 2018, 01:01:06 am
Running mediavps makes cutscenes not play, help.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: deathspeed on August 18, 2018, 10:00:35 pm


You can choose the directory where the mods are installed. In fact, people really shouldn't use C:\Program Files for that since it complicates a few things. Please note that this directory is separate from the location where Knossos is installed. You can select both, one during installation and the other on first run. You should also use a new directory since Knossos has a different directory structure. It will copy the retail VPs from your old directory if you point Knossos towards it when it asks you to.



Regarding the bold text above, you mean the Knossos "data path" under Settings should be separate from my existing installation, right? 
So I have the the Knossos folder (E:\Program Files (x86)\Knossos), my existing folder (E:\games\FreeSpace2), and I will create a new folder for Knossos downloads?
Thanks!
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: niffiwan on August 19, 2018, 12:08:46 am


You can choose the directory where the mods are installed. In fact, people really shouldn't use C:\Program Files for that since it complicates a few things. Please note that this directory is separate from the location where Knossos is installed. You can select both, one during installation and the other on first run. You should also use a new directory since Knossos has a different directory structure. It will copy the retail VPs from your old directory if you point Knossos towards it when it asks you to.



Regarding the bold text above, you mean the Knossos "data path" under Settings should be separate from my existing installation, right? 
So I have the the Knossos folder (E:\Program Files (x86)\Knossos), my existing folder (E:\games\FreeSpace2), and I will create a new folder for Knossos downloads?
Thanks!

Correct - the knossos downloads dir could be something like E:\games\FS2Knossos
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 19, 2018, 01:07:09 am
@SamVision: Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

@deathspeed: Exactly. :)
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: SamVision on August 19, 2018, 03:58:04 am
https://fsnebula.org/log/5b78e393cb0d333d72f292f1 (https://fsnebula.org/log/5b78e393cb0d333d72f292f1)

Here is my debug log, I think.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: PIe on August 19, 2018, 04:59:25 am
That's a known issue with the latest FSO nightlies and is not a Knossos bug.  See https://github.com/scp-fs2open/fs2open.github.com/issues/1828.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: niffiwan on August 19, 2018, 05:23:58 am
In the meantime if you just want to play you can move the .MVE cutscenes to a different location - FSO won't crash but obviously you don't get any cutscenes either. You could also download and install the ogg cutscenes as well, but the only link I found is on the now-dead fsmods website. 

I recall someone saying there was a mirror/dump of fsmods somewhere - can anyone provide a link to it?
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Novachen on August 19, 2018, 06:46:58 am
There are on FreeSpace Files (http://sectorgame.com/fsfiles/download/dXBsb2Fkcy9NdWx0aW1lZGlhL1ZpZGVvcy9GcmVlc3BhY2UlMjAyJTIwQ3V0c2NlbmVzJTIwLSUyME9HRy56aXA=/h/6f93b75b9c42e01f7290bd862de8b778) too.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: SamVision on August 19, 2018, 06:47:17 am
I got the .OGG cutscenes, works fine now thank you.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: karajorma on August 20, 2018, 06:47:59 am
I just installed Knossos on my second PC to do some stuff for TBP and I'm not sure I like the wording of the install FS2 screen for Knossos. For those who only want to play a total conversion like TBP or Diaspora, it does very much look like FS2 is necessary. Those people might never have even heard of FS2, they'll have been promised a free game based on a TV show or film they really like and then the first thing they see when they install Knossos is a request to install / buy something called FS2. It looks a little like we lied to them and are maybe even making money off of selling FS2. For both Beyond the Red Line and later with Diaspora we found that the biggest obstacle to getting players were people who thought you needed FS2 to play the game. We'd often see our games getting mentioned on a website and the first comment being "This looks great, but I don't have a copy of Freespace 2 so I'm going to pass". Yeah, they'd be someone further down who would correct them but it's hard to not believe that it lost us a few users. It only takes one person angrily saying that they uninstalled it because we're trying to scam them into paying for FS2 to lose a lot of people.

We're also going to get people who want to play Fate of the Galaxy, download Knossos and then realise they don't have FS2 installed, can't find the CDs, etc, and then decide not to continue even though they didn't need it. There are a lot of people out there who loved FS2 and haven't played it in years. TCs can get them interested in the game again but we shouldn't make them feel like they have to dig out their copy of FS2 if they came for TBP or Diaspora.


Instead, before the screen talking about FS2 we could have one with two options. The first one is just screenshots/logos from Fate of the Galaxy, Diaspora, TBP etc and says "I'm just here for the Free stuff" and the other one has a picture of those games and a big one of FS2 and says "I have Freespace 2 / want to buy it. Give me everything!" We can have a more detailed explanation below the pictures of course but the idea is to make it easy for people to pick the correct option. If someone selects the first one, it just skips the FS2 install bit. Knossos still makes it possible to install FS2 if you buy it later so that isn't too much of a problem if someone later decides to buy it.

I really love Knossos and kudos to all of those who have put lots of work into it. I think it works great for the community, but it isn't as simple as it could be for outsiders, especially the audience we're hoping to reach when big TCs like Diaspora or Fate of the Galaxy have a release.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: mjn.mixael on August 20, 2018, 07:06:32 am
Hmm, i thought that's kinda what we did already... apparently not. I haven't seen the install screens since we originally built them.

Anyway.. I was annoyed that you felt you needed two long paragraphs to convince us. :p  No argument here, we just didn't think to do it that way.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: wesp5 on August 20, 2018, 07:37:42 am
Instead, before the screen talking about FS2 we could have one with two options. The first one is just screenshots/logos from Fate of the Galaxy, Diaspora, TBP etc and says "I'm just here for the Free stuff" and the other one has a picture of those games and a big one of FS2 and says "I have Freespace 2 / want to buy it. Give me everything!

I completely agree with this! Also I already know a bit about FSO from working on TBP, but the first time Knossos launches I get these dozends of mods and must actually search for the one I am looking for. There should be a big seperation of the standalone FSO games and the mods! Furthermore TBP only appeared after refreshing the mod list, why is that? And I recommend to list the mods according to their full names and not leaving "the" out when sorting!

Also I think there should be a more obvious link here in the forum to find and install Knossos. Like in the Getting Started thread or similar...
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 20, 2018, 08:12:25 am
@karajorma: I agree completely with what mjn said. We made it possible to skip the FS2 installation since we wanted to avoid those issues. I guess the wording wasn't the best.
@mjn: I think the screenshots in the second post here are still mostly accurate. Since this would be a purely cosmetic change (we already have the skip button) changing the template alone should be enough.

@wesp5: That's planned. I want to implement a filtering system which allows you to hide certain stuff like engines (FSO), FS2 mods, etc. If retail isn't installed, all FS2 mods will be hidden by default but can be made visible by enabling them in the filter menu.
Unfortunately, that's going to take a while since I have to solve a few other issues first. Just know that it's on my TODO list.

There's already a link to Knossos in the navbar at the top of the page. More links never hurt, I guess.  :lol:

EDIT:
Furthermore TBP only appeared after refreshing the mod list, why is that?
That might be due to the fact that TBP is still private. That won't happen once it's released.

And I recommend to list the mods according to their full names and not leaving "the" out when sorting!
Argh, really? We already had that discussion. Ignoring articles like the for sorting is common practice (take a look at Steam if you want a related example) and the whole thing was even requested by others a while back.
I'm not going to make this a setting that people can turn on and off. We have a search goddamnit! I somehow get the feeling that noone's using that.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: karajorma on August 20, 2018, 09:26:04 am
Hmm, i thought that's kinda what we did already... apparently not. I haven't seen the install screens since we originally built them.

Anyway.. I was annoyed that you felt you needed two long paragraphs to convince us. :p  No argument here, we just didn't think to do it that way.

I was more about convincing of the importance of doing this sooner rather than later. I knew it was always something that you guys knew we needed. I was just worried it had gotten forgotten about (It's pretty easy to forget since you never see it again after Knossos gets installed).
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: niffiwan on August 20, 2018, 10:00:14 am
We have a search goddamnit! I somehow get the feeling that noone's using that.

:lol:  I am!!!

Although... for some feedback...  :nervous:

It's a bit slow, especially when you've cleared the search bar and are waiting for everything to appear again (aside - are you hiding entries, or removing them from a list? I should look at the code to find out... ;7)
It's also a bit slow when typing, perhaps delay activating the search until 1 sec has passed without keypresses, or at least 3 chars have been typed (I have NO idea how hard that might be :) And having said that the Steam search bar doesn't do either & it remains snappy. Of course, it's not filtering images either, just a text list...)
A "delete" button might be useful to clear all search results, I've seen that in similar applications, e.g. in Steam you have a (x) appear at the right hand side once you've populated the search bar
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: mr.WHO on August 22, 2018, 03:17:18 pm
I'm not sure if this is the right place, but could someone from FSO team contat Avast anti-virus team - it keeps blocking my FSO.exe for about 1-2 hours saying that the file is rare and potentialy dangerous, so they need to check it for possible virues. After 2 hours the file is whitelisted, but every time FSO is updated in Knossos I have to go through the same waiting for Avast.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: OverDhill on August 22, 2018, 03:46:34 pm
I made an exception for my Freespace 2 folder for Knossos (K:\Games\Freespace2\*) so it stops that. I use Avast myself.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 22, 2018, 03:54:38 pm
@niffiwan: Weird. For me the search is pretty much instant. If you want to take a look at the code, it starts in search_text in html/templates/kn-page.vue (https://github.com/ngld/knossos/blob/develop/html/templates/kn-page.vue#L66), goes through knossos/web.py (as every JS->PY interaction) and finally reaches perform_search in knossos/windows.py (https://github.com/ngld/knossos/blob/develop/knossos/windows.py#L476). The actual filtering is implemented in search_mods in knossos/windows.py (https://github.com/ngld/knossos/blob/develop/knossos/windows.py#L365) like every other mod list filter. It updates the mod list and calls updateModlist in html/js/main.js (https://github.com/ngld/knossos/blob/develop/html/js/main.js#L128) to display the new list. That function also calls updateModlist in html/templates/kn-page.vue (https://github.com/ngld/knossos/blob/develop/html/templates/kn-page.vue#L103) which only updates the mod list in that template and nothing else in this case (it also handles tab switching and showing the welcome page during the first run). The rendering (removing and adding DOM nodes) is handled by Vue.js.
Yes, this whole chain has to run on every keypress and is overly complicated. I want to move search_mods from Python into JavaScript code which should simplify this whole thing but requires a few changes in related code (like transferring the complete mod list from Python to JS at least once). The reason things are this way is that this whole thing changed a lot. The search_mods function existed at first (back when Python was also responsible for rendering the UI) and everything kind of grew around it.
The delete button sounds like a good idea and should be fairly easy to implement since it will only require changes to html/templates/kn-page.vue.

@mr.WHO: They can try but I wouldn't expect that to help much since there's no reason for Avast to trust random people on the internet. Besides, you can do it, too: https://www.avast.com/false-positive-file-form.php
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Bryan See on August 22, 2018, 07:17:43 pm
What about other third-party AV/Internet Security software?
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Nightmare on August 22, 2018, 07:20:57 pm
They'll complain if they're having issues.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: -Norbert- on August 22, 2018, 08:04:11 pm
So I downloaded Knossos just now and I have some questions:

Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 22, 2018, 08:30:42 pm
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: -Norbert- on August 23, 2018, 03:55:50 pm
Thanks.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Bryan See on August 23, 2018, 05:23:15 pm
If I suggest, if the access to Program Files is restricted to admin only, how does Knossos launcher work in that mode? Let's say a FS2 installation resides in that folder, assuming that Steam is used.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 23, 2018, 05:33:07 pm
You shouldn't use an existing FS2 installation as your data folder (as has been pointed out several times already).
Copying the retail files from an existing FS2 installation works even if it's in Program Files since then Knossos only needs to read from there and not write.
As you can see, there is no problem even if the user installed FS2 through Steam.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Nightmare on August 23, 2018, 07:17:38 pm
But I haven't seen that info in the OP yet. Given that you come across "you need a clean install" like every 2 or 3 threads it should be added IMO in a way that you can't click the DL links without seeing it, unless you're blind.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 23, 2018, 10:17:53 pm
If you select an FS2 directory, Knossos itself tells you "Please don't use an existing FS2 directory. It won't work!". So it should be pretty self-explaining...
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Nightmare on August 23, 2018, 10:35:58 pm
Theoraticly I agree 100%. But judging from the amount of these posts (as you noted yourself), it aparently isn't for some reason. Also, it's one of the things that people might should know before switching from regular (or no install for new users) to Knossos, as it seems to be the point where most people struggle.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 23, 2018, 11:15:46 pm
I've reorganized the OP a bit. Let me know what you think. I tried to emphasize that Knossos is different from any other launcher and not make it too boring. I might've overdone it a little.  :nervous:
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Nightmare on August 23, 2018, 11:36:07 pm
Seems OK to me. On the other hand, Knossos telling you "Please don't use an existing FS2 directory. It won't work!", is quite clear too...

One detail (maybe I overlooked it)- does Knossos also install FS itself for you once you select the GOG-installer? That being said, I think the obvious "You need to buy FS2" is missing.

Maybe some Knossos-FAQ might be helpful at some point; I think most of the other "I have problems with Knossos" posts were also rather similar.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 23, 2018, 11:46:54 pm
The "you need to buy FS2" is intentionally missing since Knossos works fine with TCs (and those don't require retail). However, it will refuse to install FS2 mods until you provide the retail files.

Knossos detects an existing FS2 installation if the user used the GOG installer, Galaxy or Steam to install it and will ask the user if it's fine to use that installation. If the user declines or nothing was detected it allows the user to select an existing FS2 installation directory or the GOG installer. The last two options work on all supported OS.

I've thought about writing an FAQ before but couldn't come up with anything that wasn't explained within Knossos or the release post. (Even the stuff about folder structures and mod.json is explained in various help texts on the dev tab.)

I guess by now we have enough questions to actually consider them frequent. I'll try and collect a few then add them to the OP.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: -Norbert- on August 24, 2018, 03:13:44 pm
I stubled into two somethings:

I created a more or less dummy mod in which I tried if Sol A History worked with the latest FSPort MVPs, but since it warned me about errors on start-up, I figured it didn't and wanted to delete this test mod.

When I tried to delete it on Knossos itself I got an error saying "you might have problems connecting to fsnebula.org", but I never uploaded the mod in the first place, it's only local.
I was able to delete it by ending Knossos and deleting the folder in the FSO directory.

Not sure if that's intended or an oversight, but just in case it's the latter, I thought I'd report it.


And an issue with the sound:
The old Launcher detected automatically whether I had my soundcard set to headphones or speakers. With Knossos I can only set it to either speakers or headphones and I have to change it manually in the settings if I switch to the other, instead of just re-starting the game.
Is there a chance you could add the option for the current system default setting?
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: manwiththemachinegun on August 24, 2018, 06:58:16 pm
Is there a way to select different lighting pre-sets through this launcher? I took a look around and couldn't find old standbys like Spidey's etc.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: -Norbert- on August 24, 2018, 07:16:50 pm
If it's not there, you can get the values from the wiki (http://wiki.hard-light.net/index.php/Sample_Lighting_Settings) and copy/paste them in the custom flag field.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 24, 2018, 08:41:18 pm
@-Norbert-: That is indeed an oversight. That button is kind of overloaded, I should probably split it into "Delete from Nebula" and "Delete locally". Currently, it tries to delete the mod from Nebula and then asks if it should delete the local files as well. In this case the first step fails which is the reason it aborts. I'll have to investigate that error message since you're supposed to get a more appropriate error message.

I think I can add the system default to the sound devices pretty easily but I'll have to check the FSO code to be sure.

@manwiththemachinegun: The lighting presets were never added to Knossos because I didn't consider them an important feature to add. Additionally, none of the old lighting presets work that well with the new PBR renderer. We'd need to compile presets. IIRC there was a thread for exactly this purpose a while back and the only one who posted a preset was FrikgFeek.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Iain Baker on August 24, 2018, 10:51:58 pm

I was kindly sent this a while back when I enquired about lighting presets for Knossos. :-)

29
 
FreeSpace Campaign Restoration
View Profile Personal Message (Offline)
Re: Knossos Blue Planet lighting pre-sets Reply #3 on: July 06, 2018, 12:11:30 am
Quote
-ambient_factor (0-128) This controls ambient lighting which is applied to all parts of the ship from "all" directions. The way this works is a bit weird. (ambient factor * 2) - 255 is "added" to mission ambient, but since this will almost always be a negative value it's actually removed from mission ambient.
Because of how light values are clamped it cannot go below 5.1, ambient_factor 70 will result in -115 to mission ambient which is 120 by default.

70 is essentially the lowest ambient for missions with default ambient settings which are all retail missions and the vast majority of mod missions. Some BP missions have increased ambient so values below 70 actually do something.

So 70 is basically no ambient, 80 is a bit of ambient, and 90 is quite a bit of ambient(ships will look bright from all sides). Anything above that will make ships look incredibly "flat".


Spec_tube and Spec_point are multipliers applied to beam and laser lighting respectively. If you want beams or lasers to light up more set these to around 2. If you want less lighting set them to around 0.5.

Spec_static is a multiplier applied to direct specular lighting from suns. For non-PBR models it will make their sun-lit side very shiny and reflective, for PBR models it will make the sun-lit side a lot brighter. There's no flag to control diffuse static lighting so non-PBR models will always have the same amount of light come from suns.



So for a more dynamic "dark" look you should go with ambient_factor 65, spec_static 2.5, spec_tube 2 and spec_point 1.5. Also disable emissive lighting in the launcher settings because it makes the ships look pretty flat.

This will make lighting "dark" by default but ships will be pretty bright when facing the sun or when firing beams and lasers, resulting in a rather pretty contrasting look.

If you want a flatter, grayer look where lighting is more even use ambient_factor 85, spec_static 0.8, spec_tube 1.5 and spec_point 0.5. Beams should still be pretty bright honestly. Also disable emissive lighting in the launcher.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Iain Baker on August 24, 2018, 10:58:15 pm
Based on the information I received I'm using these:

Custom Flags: -ambient_factor 65 -spec_exp 11 -spec_point 1.5 -spec_static 2.5 -spec_tube 2. -ogl_spec 80

Full Commandline: -ambient_factor 65 -spec_exp 11 -spec_point 1.5 -spec_static 2.5 -spec_tube 2. -ogl_spec 80

It makes for a dark and moody atmosphere similar to Spidey's and Castor's Settings.

NB - make sure you turn of 'emissive light from ships'

Enjoy :-)
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: manwiththemachinegun on August 24, 2018, 11:05:37 pm
Thanks guys, I thought something seemed off even with the new models.
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: Hellzed on August 25, 2018, 04:07:30 pm
I'm encountering issues installing MediaVPs 3.8.1 (both the completely fresh Knossos + FS2 + MediaVPs install, and the upgrade from MediaVPS 3.7.2, fail in the same way):
https://gist.github.com/Hellzed/954fc709b7bd28342eb81c8fdc84550c

Installing MediaVPS 3.7.2 works just fine. I'm running Knossos master branch, no code changes. Same when I use Knossos from the Ubuntu PPA. Any idea?
Title: Re: PUBLIC BETA: Knossos 0.12.3 (combined launcher/installer)
Post by: ngld on August 25, 2018, 04:12:57 pm
I forgot an ipath call in the InstallTask code. I'll add it tonight (has been on my TODO list for a while). Sorry, didn't have much time to work on Knossos this past week.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: ngld on August 31, 2018, 06:12:13 pm
The next release is finally out! This update fixes the aforementioned problem on case-sensitive filesystems (mostly Linux systems).
I've also fixed a few annoying bugs and improved error messages. The full list is on GitHub (https://github.com/ngld/knossos/releases/tag/v0.12.4).
Also, the mod list might load faster now upon startup... not sure. Let me know if you notice a difference.

As always, Knossos should auto-update on all supported OS.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: DeadNova on September 01, 2018, 11:35:31 am
Not sure if anyone had similar problems, but any time I click on any kind of dropdown list, Knossos crashes.

Any advice? :)
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: ngld on September 02, 2018, 02:07:05 am
Which Windows version are you on?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: DeadNova on September 02, 2018, 05:26:43 am
Which Windows version are you on?

Win 8.1, using Knossos 0.12.4
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: wesp5 on September 03, 2018, 03:00:14 am
I don't have the time to read all of the posts here, but Knossos want's to update itself from 0.12.3 to 0.12.4 but always fails because it can't override some files, like 7z.exe!
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: jr2 on September 03, 2018, 07:20:02 am
Could this be an antivirus being overprotective?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: wesp5 on September 03, 2018, 08:29:54 am
Could this be an antivirus being overprotective?

I doubt it. I only use Microsoft Essentials and the rest of the update works fine. Or should Knossos be run as an administrator for this?

P.S.: It seems setting Knossos to run as Administrator did the trick! Maybe this should be mentioned somewhere, if it isn't already :)...
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: -Norbert- on September 03, 2018, 10:41:03 am
My Win7 didn't need the admin mode to make the update. It asked for admin permissions via a "OK|Cancel" pop-up like pretty much any other installation.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Jake2447 on September 04, 2018, 12:22:05 am
Thanks everyone who has worked on this or uploaded their mods.  I've been away from HLP for years and recently wanted to play again the last couple of days, and this project has made everything so much easier.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: wesp5 on September 04, 2018, 08:22:46 am
My Win7 didn't need the admin mode to make the update. It asked for admin permissions via a "OK|Cancel" pop-up like pretty much any other installation.

Yeah, it must be something different. It wouldn't update itself on another PC even as admin and with the same antivirus tool. But that one was 64bit?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: ngld on September 04, 2018, 09:11:58 am
@wesp5: Make sure that 7z.exe isn't still running. It'd be helpful if you could check if it shows up in Task Manager and if it does which commandline it's being run with (you might have to enable that column to see it).
@Jake2447: Thanks!
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: wesp5 on September 04, 2018, 12:32:57 pm
@wesp5: Make sure that 7z.exe isn't still running.

Too late, I already installed 0.12.4 from the seperate installer. And I'm pretty sure 7z.exe was not running unless Knossos starts it and doesn't stop it while it is updating itself! I'm using WinRAR all the time...
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: DeadNova on September 09, 2018, 07:19:53 am
Which Windows version are you on?

Win 8.1, using Knossos 0.12.4

Got fed up with it always crashing, even after multiple re-installs, registry cleans, etc, and upgraded to win 10 home edition... Problem solved.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Crane on September 09, 2018, 10:53:48 am
How do I get rid of all trace of Knossos?

I installed it, found it bloated and confusing and couldn't work out how to make it load multiple mods simultaneously, then uninstalled it, and now I can't manage to make FS2 load any mods at all because it wants to reference the new AppData folder but YAL doesn't write to there and even copying the command line .cfg over into appdata doesn't make it read.
I've tried completely uninstalling FS2 and reinstalling everything and I absolutely can't manage to make the game even accept things like the ****ing 3D radar flag.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: m!m on September 09, 2018, 10:55:04 am
Use a nightly build. That issue is fixed there.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: ngld on September 09, 2018, 11:11:13 am
@DeadNova: Interesting... I have no idea why Knossos would crash on 8.1 but not on 10. I'll try to investigate when I have more time. Though it probably was something specific to your computer (since this is the first time I've heard of this kind of problem). Oh, and Knossos doesn't even use the registry so I have no idea how "cleaning" it would help...

@Crane: If you'd actually read the very first post in this thread, you'd know the answer. (I've even written "VERY IMPORTANT" in front of that part...)
Also, I'm wondering; Why do you think Knossos is bloated and confusing? Is there anything we could do to make the UI clearer?
You can't load more than one mod at a time since that's the way FSO is designed. Basically, each mod is a mission/campaign pack and you choose which one you want to play.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Crane on September 09, 2018, 11:18:40 am
Oh, nightly build of FSO. I thought that meant a nightly build of Knossos. Thanks, that does fix it.

I found the UI unpleasant because there was no way I could see to view a page that was just "installed mods I could activate" instead of "all the mods ever".
I couldn't work out how to make it activate any mods that I created, because they didn't show in whatever database you were pulling from.
I also didn't want to have to work out how your .json files differed from the old style .ini files.

In general, I found the whole thing took up more visual space than it needed. I didn't even get as far as trying to find whatever screen would have let me toggle things like 3D warp effects and missile lighting.

Oh, also:
"You can't load more than one mod at a time since that's the way FSO is designed. Basically, each mod is a mission/campaign pack and you choose which one you want to play."

That's just not true. You can append as many mods as you like to the command line with the -mod parameter, and not every mod is a campaign pack. The MediaVPs for one!
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: DeadNova on September 09, 2018, 12:27:06 pm
and now something new  :blah:, getting a little frustrated with Knossos..

See attachment.

[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: niffiwan on September 09, 2018, 12:53:26 pm
and now something new  :blah:, getting a little frustrated with Knossos..

That error is from FSO - which mod are you trying to run?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: DeadNova on September 09, 2018, 01:16:07 pm
Retail FS2 and tried running MVP 3.7.2, 3.8.0 and 3.8.1. Same error.

But also found the solution. I have to install Freespace 2 using Knossos. If this is something known..I'm just bad at following instructions :)
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: jr2 on September 09, 2018, 01:34:23 pm
Oh, nightly build of FSO. I thought that meant a nightly build of Knossos. Thanks, that does fix it.

I found the UI unpleasant because there was no way I could see to view a page that was just "installed mods I could activate" instead of "all the mods ever".
I couldn't work out how to make it activate any mods that I created, because they didn't show in whatever database you were pulling from.
I also didn't want to have to work out how your .json files differed from the old style .ini files.

In general, I found the whole thing took up more visual space than it needed. I didn't even get as far as trying to find whatever screen would have let me toggle things like 3D warp effects and missile lighting.

Oh, also:
"You can't load more than one mod at a time since that's the way FSO is designed. Basically, each mod is a mission/campaign pack and you choose which one you want to play."

That's just not true. You can append as many mods as you like to the command line with the -mod parameter, and not every mod is a campaign pack. The MediaVPs for one!

You are talking about dependency tress (mods of mods).  Knossos handles those appropriately (if you load a mod that requires MediaVPs, that will be enabled, and if you try to install a mod that requires, say, FSPort, it will download FSPort for you, and enable it when you play that mod).

As far as the 3D warp options, etc, I'm not sure, but I think those are configured on a per-mod basis, but they're working on global overrides?  I could be wrong though.  Check through the settings.

I'm assuming uninstalling Knossos will remove most of it, and there's a settings somewhere in the users's AppData (Local and Roaming, I believe).
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Mongoose on September 09, 2018, 01:36:43 pm
I found the UI unpleasant because there was no way I could see to view a page that was just "installed mods I could activate" instead of "all the mods ever".

That would be the Home tab.  Once you install a mod listed on the Explore tab, it will be visible under Home.

Quote
I couldn't work out how to make it activate any mods that I created, because they didn't show in whatever database you were pulling from.
I also didn't want to have to work out how your .json files differed from the old style .ini files.

The Dev tab enables you to create your own mods and define their dependencies. You can also optionally upload them to Nebula so that other users can download them. You shouldn't need to muck about with creating .json files at all; Knossos handles that automatically when you feed it the correct dependencies for your mod. I mean you could make one manually if you really wanted to, but it's not necessary.

Quote
In general, I found the whole thing took up more visual space than it needed. I didn't even get as far as trying to find whatever screen would have let me toggle things like 3D warp effects and missile lighting.

The gear icon in the upper-right opens the settings menu, where you can set global flags that apply to all mods. Each mod can ship with its own recommended flags, which you can view/edit from its icon's drop-down menu.

Quote
Oh, also:
"You can't load more than one mod at a time since that's the way FSO is designed. Basically, each mod is a mission/campaign pack and you choose which one you want to play."

That's just not true. You can append as many mods as you like to the command line with the -mod parameter, and not every mod is a campaign pack. The MediaVPs for one!

This is true, though in those cases the secondary mods are really serving as extensions of the primary mod's data set. This is another place where Knossos shines: if you try to download a certain mod that relies on dependencies you don't have yet, Knossos will automatically download those too.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Konatsat on September 09, 2018, 02:53:00 pm
Keep getting a 0xc000007b error whenever I try to launch anything or even run a debug.  Is there something I'm missing?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: ngld on September 09, 2018, 06:26:46 pm
Can you go to your Home tab, click the details button for FSO and tell me which version you have installed? Should be in the top left corner. Also, please click on Options > Verify file integrity and tell me what the result was. Did you modify (or delete) any of FSO's DLLs?

EDIT: @Crane: Yes, you can tell FSO to load multiple mods but you're only supposed to list the main mod you want to play and its dependencies. If you try to enable (for example) both BP and JAD, you'll get a bunch of errors since they're not supposed to be loaded at once.
The MediaVPs also contain fixes for retail missions IIRC so technically they're also a mission pack. If that's not the case, then they're the only exception (aside from stuff like the Cockpit stuff though I don't see that as a traditional mod, rather an addon).
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on September 09, 2018, 07:08:33 pm
Hello guys,
I want to report 2 big issues (tried to solve it by my own but as i've been unsuccessful till now, so i seek your lights).


I was on version 0.8.3 and everything was working fine. But each time i try to launch a higher version of Knossos like 0.9.1; 0.10.1 or 0.12.3 i got this error message (attached files).

What is odd, is that there are no error message about my drivers or about opengl with KnossosLauncher 0.8.3, but have the same error message with Knossos higher versions (0.9.1; 0.10.1) and 0.12.3

Trying to solve the issue, i did that:
Checked my drivers but all were already updated.
Checked my opengl version on my system and it is compatible till opengl 4.3 (i ran a test from OpenGl viewer)
Read the topic and followed (or tried to follow) the advices given by jr2 and ngld (about DLLs that must be installed with fs2_open_..... .exe and about Reshade shaders)

As the error message said " [...] or, if this is not possible, make sure the ANGLE Open GL ES 2.0 emulation libraries (libEG.dll, libGLESv2.dll and d3dcompiler_*.dll) are available in the application executable's directory or in a location listed in PATH"
I've installed "Mali_OpenGL_ES_Emulator-v3.0.2.g694a9-Windows-64bit.exe" on my computer and copied libEG.dll, libGLESv2.dll from installed folder into my FSO folders located in FreeSpaceOpen\bin\FSO-3.8.0-3\x64_avx and FreeSpaceOpen\bin\FSO-3.8.1-20180908\windows\x64 
I've also copied D3DCompiler_47.dll into my FSO folders located in FreeSpaceOpen\bin\FSO-3.8.0-3\x64_avx and FreeSpaceOpen\bin\FSO-3.8.1-20180908\windows\x64
I've run ReShade_Setup_3.4.1.exe with each of my FSO built (FSO 3.8.0.3 and FSO-3.8.1-20180908 for having the new opengl32.dll)
And it's still not working.

So i went back to Knossos 0.8.3


From Knossos 0.8.3, i've recently updated my MediaVPS to 3.8.1. I can launch all mods that i want but i'm unable to see anything like ships, vessels, basestations.... I went to the Tech room and i cant see anything, it's black with only lights (i took a screenshot of a GTC Fenris in Tech room to give you an example).

It's very odd because when i play with mods using MediaVPS 3.7.2 or lower, i can see everything (no problem at all) but when i choose mods using MediaVPS to 3.8.1, i can't see a dam thing.
Therefore, i don't think it's a graphcard issue or opengl issue so what can i do?

Thanks in advance for your advices guys.

[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: ngld on September 09, 2018, 07:33:18 pm
First of all, remove the files you added to the FSO folders. The error message is coming from Qt (a library Knossos uses), not from FSO. Thus you're supposed to copy them into Knossos' folder, not FSO's. I think those files were bundled with past Knossos versions. Not sure why they aren't anymore, I think something changed with regards to Qt or PyQt5. Let me know if moving the DLLs into Knossos' folder fixes the problem for you.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on September 10, 2018, 09:55:03 am
"Thus you're supposed to copy them into Knossos' folder, not FSO's."
Yes, i though of that too and did it before posting on the forum but still didn't work.

First of all, remove the files you added to the FSO folders. The error message is coming from Qt (a library Knossos uses), not from FSO. Thus you're supposed to copy them into Knossos' folder, not FSO's. I think those files were bundled with past Knossos versions. Not sure why they aren't anymore, I think something changed with regards to Qt or PyQt5. Let me know if moving the DLLs into Knossos' folder fixes the problem for you.

Ok so after reading your answer, i did that:
Deleted both FSO-3.8.0-3 and FSO-3.8.1-20180908 folders
Opened Knossos 0.8.3 and download a new FSO-3.8.0-3 and FSO-3.8.1-20180908 version
Applied ReShade_Setup_3.4.1 to both FSO-3.8.0-3 (fs2_open_3_8_0_x64_AVX.exe) and FSO-3.8.1-20180908 (fs2_open_3_8_1_20180908_bc03442_x64_SSE2.exe) folders

Uninstalled Knossos 0.8.3
Installed Knossos 0.12.3 (didn't launch it yet after installation, the error message would appeared)
Copied D3DCompiler_47.dll, libEGL.dll and libGLESv2.dll from Mali OpenGL ES Emulator 3.0.2.g694a9 folder to Knossos folder
Launched Knossos 0.12.3 and i still have the same error message.

Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: m!m on September 10, 2018, 09:57:08 am
Since FSO is also having trouble with displaying ship models it is possible that your OpenGL drivers are somehow not working correctly. What GPU are you using?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on September 10, 2018, 10:18:47 am
Since FSO is also having trouble with displaying ship models it is possible that your OpenGL drivers are somehow not working correctly. What GPU are you using?

In fact i don't think so because like i said before why everything is working fine (no openGl error message and i can see ships) when i use MediaVPS 3.7.2 and lower while each time i try to use the new MediaVPS 3.8.1 i can't see anything.
I don't see any logics when in one case it works and on the case it doesn't.

My GPU:
AMD Radeon HD 7400M Series
Intel(R) HD Graphics 3000
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: m!m on September 10, 2018, 10:22:03 am
The 3.7.2 MediaVPs may be using less graphics features than the 3.8 MediaVPs so that might explain the difference. With your GPU you should be able to run FSO without problems so that is not the cause of your problems. Have you tried completely removing and reinstalling your graphics drivers? Maybe something went wrong when they got updated the last time.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on September 10, 2018, 10:38:08 am
I'm sure it's a dll problem.

I used to have a similar issue (can't see ships in Tech room) when one day (that was years ago) i tried a mod with a lower version of mediavps. I was able to solve this problem in adding a missing dll to one of my folder. But it was long time ago and a kernel issue at that time, so nothing to do with this current issue.

I don't know if it can help you guys but this is my actual Knossos 0.12.3 folder. I though maybe there is something missing or something that should not be here.

[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on September 10, 2018, 10:39:52 am
I also add you what my FSO folder look like (maybe there is something missing or something that should not be here). I noticed (but maybe it's normal) that there were common dll files beteween Knossos folder and FSO folder.

(And sorry for the lot of attachments, it's to make things cleared, and share common view)

Thanks  :)

[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: ngld on September 10, 2018, 03:54:25 pm
Looks fine to me at a glance... Can you please generate a debug log (https://www.hard-light.net/forums/index.php?topic=56279.msg1180359#msg1180359) and test what happens if you rename the opengl32.dll in FSO's directory (just choose a different name like disabled_opengl32.dll)? I know that it's part of ReShade but I want to see if it's part of the problem.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: DeadNova on September 10, 2018, 04:25:19 pm
@Bobun: Check if shadows are enabled or not.  For me that was the problem. 3.8.1 automatically enabled shadows while 3.7.2 didn't.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on September 11, 2018, 06:37:58 pm
I'm trying to be methodical to understand the origin of the problem. So here what i did, following your instructions:

Deleted both FSO-3.8.0-3 and FSO-3.8.1-20180908 folders
Uninstalled Knossos 0.12.3 (remember I can’t open it, so to be able to do the debug log I must use the only version that works for me which is Knossos 0.8.3)
Installed Knossos 0.8.3
Downloaded and installed a new FSO-3.8.0-3 and FSO-3.8.1-20180911

Note: as I don’t have any opengl error message when I use Knossos 0.8.3, I did not copy D3DCompiler_47.dll, libEGL.dll and libGLESv2.dll from Mali OpenGL ES Emulator 3.0.2.g694a9 folder to Knossos folder. This opengl error message is specific to Knossos 0.12.3

NOR did I apply ReShade_Setup_3.4.1 to FSO build at the start of my tests (check bellow). But applied ReShade at the end (check log3_fs2_open.log). Like that you have elements to compare.

Tests:
•   Essay 1-Knossos 0.8.3: Tried to use FSO builds without applying Reshade:
   Knossos Settings\Prefered Engine: Nightlies

FSO build: FSO 3.8.1 -20180911 with MediaVPS 3.8.1
Flags: -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash –enable_shadows
Result: negative (can’t see ships/vessels in techroom)
I generated the fs2_open.log (Check Log1_fs2_open.log)

@ DeadNova: I checked the FSO Settings in MediaVPS 3.8.1 Options button and yes “Enable Shadows” was “On”, so I deselected it.
Result: negative (can’t see ships/vessels in techroom)

I though that maybe it was something I selected in the list type (FSO settings) that be the problem, so I selected only these flags to check potential incidences: –dualscanlines –targetinfo –rearm_timer -3dwarp –warp_flash –ship_choice_3d –weapon_choice_3d -3dshockwave –orbradar
Result: negative

In addition, I wanted to check if “Enable shadows” had really an incidence on my issue. Here results:
FSO build: FSO 3.8.1 -20180911 with MediaVPS 3.8.1
Flags: -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash
Result: negative

FSO build: FSO 3.8.1 -20180911 with MediaVPS 3.8.1
Flags: -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash –enable_shadows
Result: negative
 
FSO build: FSO 3.8.1 -20180911 with MediaVPS 3.7.2
Flags: -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash -enable_shadows
Result: negative

FSO build: FSO 3.8.1 -20180911 with MediaVPS 3.7.2
Flags: -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash
Result: negative

   Knossos Settings\Prefered Engine: Stable
FSO build: FSO 3.8.0-3 with MediaVPS 3.8.1
Flags: -missile_lighting -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash
Result: Error message (seems a “normal” error message as MediaVPs 3.8.1 works only with nightlies)

FSO build: FSO 3.8.0-3 with MediaVPS 3.7.2
Flags: -missile_lighting -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash
Result: Positive (can see ships and vessels in Tech room)

FSO build: FSO 3.8.0-3 with MediaVPS 3.7.2
Flags: -missile_lighting -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash –enable_shadows
Result: Positive

Conclusion: @ DeadNova and everyone, “Enable shadows” seems to have nothing to do with the issue for me.


•   Essay 2-Knossos 0.8.3: Tried to use FSO-3.8.1-20180911 (with Reshade) with MediaVPS 3.8.1

Applied ReShade_Setup_3.4.1 to FSO-3.8.1-20180911 (fs2_open_3_8_1_20180911_138a1d0_x64_SSE2.exe) folder
Did not rename opengl32.dll

   Knossos Settings\Prefered Engine: Nightlies
FSO build: FSO 3.8.1 -20180911 with MediaVPS 3.8.1
Flags: -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash
Result: Negative
I generated the fs2_open.log (Check Log 2_fs2_open.log)

Renamed the opengl32.dll from FSO-3.8.1-20180911 to “disabled_opengl32.dll”
FSO build: FSO 3.8.1 -20180911 with MediaVPS 3.8.1
Flags: -3dshockwave –dualscanlines –targetinfo –orbradar –ship_choice_3d –weapon_choice3d -3dwarp –warp_flash
Result: Negative
I generated the fs2_open.log (Check Log 3_fs2_open.log)

Cheers


[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Konatsat on September 11, 2018, 06:58:13 pm
Can you go to your Home tab, click the details button for FSO and tell me which version you have installed? Should be in the top left corner. Also, please click on Options > Verify file integrity and tell me what the result was. Did you modify (or delete) any of FSO's DLLs?

The version is 3.8.1-20180911 and the popup message state that no problems were detected when verifying file integrity.  I haven't modified or deleted any of the DLLs.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: ngld on September 11, 2018, 08:41:22 pm
@Bobun: Thanks for detailed information! I think we can safely assume at this point that ReShade isn't causing any of the current issues. The log confirms that your driver is working and that it supports OpenGL 4.5. I've compared the two Knossos releases and the only significant difference that could cause the problem is a packaging issue in 0.8.3 which caused Qt to be unable to use Windows' "Vista style". It's weird. I really doubt that this causing your problem. Hm... I'll see if I can come up with any potential solutions.

@Konatsat: As an explanation: That error message is coming from windows and means that a 32bit exe file is trying to load a 64bit DLL (or the other way around). The annoying part is that Windows doesn't tell you which DLL is causing the problem so you have to guess. Does the error occur with older nightlies (try one from last year for example) or on 3.8.0?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Vidmaster on September 12, 2018, 02:07:38 pm
I have tried out Knossos for the first time today and came away impressed. I could see myself switching over to a pure Knossos-setup in the future, if there is a ZIP or EXE-only distribution.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: mjn.mixael on September 12, 2018, 05:16:29 pm
I know there's an issue on github to make portable Knossos an option. I don't think ngld has had time to prioritize that yet.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: TrashMan on September 29, 2018, 02:12:35 pm
So, someone tell me about creating mods funcion?
It has a section for mod.ini files, but throws a fit when I point to it.
Does this create a mod folder, can I copy old mod folder? How's this work?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: niffiwan on September 29, 2018, 06:32:39 pm
Try this guide, if that doesn't answer your questions we'll work out how to improve the guide:
https://docs.google.com/document/d/1oHq1YRc1eXbCgW-NqqKo1-6N_myfZzoBdwZuP16XImA/edit?usp=sharing

(or just ask either here or in Discord #knossos)
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on October 01, 2018, 11:09:25 am
Quote
@Bobun: Thanks for detailed information! I think we can safely assume at this point that ReShade isn't causing any of the current issues. The log confirms that your driver is working and that it supports OpenGL 4.5. I've compared the two Knossos releases and the only significant difference that could cause the problem is a packaging issue in 0.8.3 which caused Qt to be unable to use Windows' "Vista style". It's weird. I really doubt that this causing your problem. Hm... I'll see if I can come up with any potential solutions.

Hi guys and NGLD, i was waiting for your return and potential solution for the 2 problems i posted in my posts before, but as i didn't have any answer yet, i did other tests this weekend and finally solved one of my issue. I want to share with you guys what i did as a "return of experience" so that you will be able to enhance Knossos. I've noticed bugs with fs2_open_3_8_0_x64_AVX, fs2_open_3_8_0_x64_SSE2 and with Knossos.

It was so frustrated to not be able to play with the new Mediavps that i decided to check why it didn't work. So i I did a complete uninstallation (without forgetting files like "knossos" in  Appdata\local and roaming plus "fsoinstaller.properties" in User\Name) of everything (mods, FSO, knossos, game,...) in order to eliminate side causes and to focus only on root causes.

Then i installed everything back (game+FSO+Mediavps 3.8.0 & 3.8.1) from Knossos 0.8.3
I launched the game from Mediavps 3.8.1 using FSO 3.8.0-3 (which was fs2_open_3_8_0_x64_AVX). I tried also the last nightlies Results: both the same i cannot see any ships in the techroom.

After this, i thought that "okay, accept that you will probably never play with the new Mediavps, so let's play a mod that don't need those!"

So i installed the last version of Blue Planet mod.
I launched the game using FSO 3.8.0-3 (which was fs2_open_3_8_0_x64_AVX).
Results: intro video play as normal but 1st ingame video play very slow like 1 image per second and same during mission. :eek2:
It was very odd since i haven't had this problem before. I was always be able to play this mod in the past without any problems at all.

 :mad: From here i was very angry not understanding where the problem could be from (and don't tell me it's my computer, cause it's not! been checked in posts before).

I tried one last thing: installing the new MediaVP from the old way with openinstaller.jar
So i did a clean uninstallation of everything, then i installed the game and used last version of openinstaller.jar. Installed wxlancher, FSO and only MediaVPS 3.8.1.
Opened wxLauncher, chose Fs2 open 3.8.0 SSe2 64bit
Played the game and got an error message (check image) "the application failed to start correctly (0xc000007b)"
Ok so it seems that there is something fishy with fs2_open_3_8_0_x64_SSE2 as both old platform and Knossos encounters problem.

Then i opened wxLauncher, chose fs2_open_3_8_0_SSE2
Played the game and IT WORKED !  :D At last i was able to see the new ships in techroom and to play without having slow image per second.
However, it showed me an error messages (different from the one about opengl from my previous posts). Check the image.
Unlike Knossos you have a debug button on the old platform...so after having clicked 5 times on "debug", the game launched and i was finally able to see the new MediaVPs from the techroom.

Therefore... i can safely say that there is something buggy with either FSO 64AVX and Knossos.

Something you didn't answer from my previous posts is why only Knossos 0.8.3 worked while higher version have this error message about opengl.
Maybe a track: I've noticed that (check image) Knossos launcher 0.8.3 has 48 598 Ko while new version are a bit lighter. Maybe you "deleted" something that is no longer in new versions of Knossos and that generate this openGl error. I trully think that there is a bug somewhere in Knossos. And secondly why using Knossos i'm unable to play with the new MediaVPS while using the old platform i can.

From now on i will keep the old platform, not that i like it (i sincerly prefer Knossos looking) but as Knossos new versions don't work, i don't have much choice. Please find what is the root cause to enhance our use of Knossos. :yes:



[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on October 01, 2018, 11:23:33 am
here the 5 error messages i got using the debug button (maybe some tracks for you to resolve the mystery :) )
After the 5th message, the game launched.



[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: mjn.mixael on October 01, 2018, 12:04:05 pm
MediaVPs 3.8.x requires a nightly build. You can get one here. (https://www.hard-light.net/forums/index.php?board=173.0)

Knossos currently has a bug that prevents it from getting the required build for the MediaVPs. This bug will be fixed in the next Knossos update. You can fix the problem yourself by going...

Knossos > Settings > Knossos > Preferred Stability > Nightly.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on October 01, 2018, 12:25:09 pm
i did that already...it's not the issue. Check my first posts p23 to understand why i wrote that (take me lot of time to describe in english what is what and it's not easy)
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: mjn.mixael on October 01, 2018, 01:12:31 pm
You may have multiple issues going on, but I am telling you that one problem is that you cannot run the MediaVPs with FSO 3.8.0. The five errors you posted are because the FSO 3.8.0 does not understand some of the newer options in the game_settings.tbl in the MediaVPs. Use a nightly and then we can figure out the other issues.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on October 01, 2018, 02:59:16 pm
mjn.mixael i have the impression that you don't understand what im saying or my approach. I don't throw stones at you as my English writing is not perfect, therefore my message is maybe not clear enough. Trying to make it clearer  :) My approach is to give you details and context for you to improve Knossos (i really like this platform). Im not here to make you loose your time but to give feedback that will participate to the common good.

Quote
MediaVPs 3.8.x requires a nightly build. You can get one here.

Quote
You may have multiple issues going on, but I am telling you that one problem is that you cannot run the MediaVPs with FSO 3.8.0.

I know i have multiple issues, my 1st post on page 23 tried to carry your attention on 2 issues i encountered: one with Knossos and another one with MediaVPS+FSO.
I know also that MediaVPS need nightly versions, it's what is said here https://www.hard-light.net/forums/index.php?topic=94988.0, and previously since page 1 of this subject.
I did that already.
In addition to find out what could be at the root of these 2 different issues, i did tests (page 23) with different configuration of Knossos and FSO (stable, RCs or nightly). Results are detailed page 23.

Quote
The five errors you posted are because the FSO 3.8.0 does not understand some of the newer options in the game_settings.tbl in the MediaVPs. Use a nightly and then we can figure out the other issues.


The 5 error message, i posted them to illustrate the fact that
with Knossos 0.8.3+Mediavps 3.8.1+FSO nightly=can't see ships in techroom
with FreeSpaceOpenInstaller.jar+Mediavps 3.8.1+wxlauncher+FSO=CAN see the ships in techroom. This is an improvement and means that the issue i first posted on page 23 (about Mediavps 3.8.1) is "partly solved" (only in debug mode) using FreeSpaceOpenInstaller and wxlauncher.
I shared this with you to give you tracks to find out where the issue could be.

But like i said this is not the BIG issue. Like i wrote in my 1st post (page 23), big issue is with Knossos.
Knossos 0.8.3 works fine on my computer, apart from the mediavps 3.8.1 issue.
But each time i use a higher version of Knossos (the updates) from 0.9.1 to the last 0.12.4, after the update i can't open Knossos and i have the error message about opengl.
But again, there is no opengl problem on my computer, my drivers are up to date and are compatible with opengl 4.5. This has been checked with Ngld previously.
Therefore, if my opengl is fine why im having this odd error message each time i use Knossos 0.9.1 and higher? while i don't have this error message at all on knossos 0.8.3.
I don't understand this, that's why i think that maybe something (a dll or whatever) shall be present on knossos 0.8.3 and not anymore with the new versions. That was what i wrote previously today.

The other thing i don't understand is why there is "no more issue" (i can use the mediavps 3.8.1 and see the new ships in techroom) using wxlauncher and  FreeSpaceOpenInstaller.jar while using Knossos with nightly make it impossible to see any ships in techroom. That a new thing (from my test of this weekend). If we find out why is that maybe we can understand the root cause of this situation to enhance Knossos.

Is it clearer?
Sorry for the long text...i had the feeling that you were taking a wrong path in focusing your attention on "my 5 error messages" while it's not the problem.

Cheers :)

Edit: something new:
I extracted the nightly files into C\Games\FreeSpace2
I observe that some dlls installed from FreeSpaceOpenInstaller.jar have been improved with the nightly version (larger size dlls).
Use wxlaucher and nighly 2018-10-01 11f9175 sse2 64bit: same issue described before, can't see any ships in techroom.

Since the nightly gave me new larger size dll, i check how previous fs2 open 3.8.1 would react.
Use wxlaucher and FS2 open 3.8.0 SSE2 64 bit: 5 error messages (debug button) but CAN see the ships in techroom. It's a good news since previously there was this error message "the application failed to start correctly (0xc000007b)"

Use wxlaucher and FS2 open 3.8.0 SSE2: i have the error message "the application failed to start correctly (0xc000007b)"... weird since previously this version was working fine (apart the 5 error messages on debug, i was able to see ships in techroom) before extracting the nightly version.

Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: ngld on October 01, 2018, 04:31:12 pm
The 0xc000007b error is caused by mixing 64 exe and DLLs. In the case of wxLauncher you put both the 32bit and 64bit build in the same folder which can't work (and will never work). This is a known fact and nothing we can do about that. It's also unrelated to Knossos. If you get the same error with Knossos, it's a completely different problem.

The other issues sound like various OpenGL issues. My guess would be that your computer is using the Intel HD graphics card instead of the Radeon when launching FSO through Knossos since there shouldn't be any difference with the way FSO renders stuff regardless of whether wxL or Knossos are launching it.

The smaller size of the newer Knossos versions is due to the fact that they don't include ANGLE (which can rewrite the OpenGL calls into DirectX calls). As a result Knossos won't work on machines which don't support modern OpenGL versions, however on those machines FSO won't work either. This further confirms that there's something fishy going on with your graphic drivers. Probably the same issue. Can you force your computer to use the Radeon for Knossos and everything it launches?
Note, I didn't intentionally "delete" anything. The installer is built using an automated process and some part of that changed. I can look into fixing this and providing the missing DLLs but as I said before if you have working (modern) graphics drivers, Knossos should work fine.

EDIT: Reread previous posts and fixed some statements.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bobun on October 01, 2018, 05:08:50 pm
thanks for the answer mates (ngld & mjn.mixael), i really apreciated ;)

Quote
The 0xc000007b error is caused by mixing 64 exe and DLLs. In the case of wxLauncher you put both the 32bit and 64bit build in the same folder which can't work (and will never work). This is a known fact and nothing we can do about that. It's also unrelated to Knossos. If you get the same error with Knossos, it's a completely different problem.

ok i will try to reinstall things again.

Quote
The other issues sound like various OpenGL issues. My guess would be that your computer is using the Intel HD graphics card instead of the Radeon when launching FSO through Knossos since there shouldn't be any difference with the way FSO renders stuff regardless of whether wxL or Knossos are launching it.

Seems logical and i though too that something like that could be the root cause.
So before posting my first post on the forum (page 23), I configured the switchable graphic to use Radeon card with Knossos and FSO stable an nightly version. All my tests were done with that too.

Quote
The smaller size of the newer Knossos versions is due to the fact that they don't include ANGLE (which can rewrite the OpenGL calls into DirectX calls). As a result Knossos won't work on machines which don't support modern OpenGL versions, however on those machines FSO won't work either. This further confirms that there's something fishy going on with your graphic drivers. Probably the same issue. Can you force your computer to use the Radeon for Knossos and everything it launches?
Note, I didn't intentionally "delete" anything.

yes, thanks mate for the explanation :). I hope you didn't take it wrong, i though that maybe something could be missing between my knossos version and the update version...that could have explained things.

If it's my driver, i will be stuck with it, there won't be any updates with these switchable cards (they are final in my case). If i change my computer, i shall have modern drivers.

Thanks guys for your efforts, answers and explanation. Long live Knossos! :)
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Stardust on October 03, 2018, 06:24:12 pm
Very slick and handy. However not a single campaign/mod I've tried has successfully launched. I get as far as the main menu (after warnings and alerts that errors were detected) and then the whole thing comes crashing to desktop. So far, the original Inferno is the only one that's worked without a hitch through Knossos.

Now I'm not new, I've checked file integrity and uninstalled/reinstalled mods several times through the Knossos client, no effect. Does anyone have any thoughts? I'm running out of ideas. I'm running the latest version, 0.12.4...
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: PIe on October 03, 2018, 06:26:36 pm
There were some server-side problems recently that should be fixed now.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Stardust on October 03, 2018, 08:56:15 pm
Sweet.

*Tries to play Nostos and fails* Nope. Same problem.

*rechecks file integrity, finds same problems it has before with the same files and redownloads*

While that's doing it's thing, is there anything I should be looking for? I refuse to believe that Nostos, which was JUST released, is having this sort of problem already.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Asteroth on October 03, 2018, 11:44:16 pm
The first step is to be more specific, what exactly kind of errors are you getting? Are they consistent everywhere? And to confirm the problem isn't only with Nostos?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Stardust on October 04, 2018, 08:09:08 am
Nostos is the big one right now. I did notice that several models looked like they were missing textures, the Icelus destroyer in particular as well as the Phobos corvette, when looking at their techroom entries. Short version is when I try to launch a mission from the briefing room, within two seconds it crashes todesktop saying it can't render the Hermes or Charybdis POF. Uninstalling and reinstalling, verifying file integrity has no effect.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Iain Baker on October 04, 2018, 03:23:45 pm
Hi there. For what it's worth, I completed the Nostos Campaign via Knossos two days ago and had no problems. (FYI - 'twas bloody awesome!)

Knossos still has some bugs to work out I feel. I have had mods work one day then not the next. I have had mods refuse to load one day, then work fine the next. I have had weird errors pop up, but a mod seamed to work ok anyway. I have had mods (Inferno classic for example) load and work fine, but then randomly CTD (Crash-To-Desktop) mid mission.  :confused: :banghead:

When it works it is great, it just isn't 'quite there' yet. It is still in Beta, so that is to be expected I guess. I am looking forward to when it is out of Beta and is working smoothly. That is when I will go Blitzkrieg on the Social Media side of things and hopefully attract  many new pilots  ;)
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: mjn.mixael on October 04, 2018, 03:49:36 pm
Let's make sure we're separating mod bugs from knossos bugs. If a mod has CTD worthy data in it, then Knossos is not responsible. In general.. if you have gotten a mod to run (FSO launches and you see the appropriate mod data/campaign), then any issues from there are probably the fault of the creators and not Knossos.

However if you are having issues with a mod and the 'Verify File Integrity' option doesn't run successfully, then we probably have a Knossos issue.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Stardust on October 04, 2018, 05:34:01 pm
I got no idea, mjn.mixael. But it does seem VERY odd that a given mod would work one day but not another. I'm downloading a few mods right now, will see how they pan out, whether they work or not. MTF.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Cyborg17 on October 04, 2018, 06:58:26 pm
It could have to do with the FSO build.  We haven't had a stable release in a while, so hidden bugs may be piling up.  And the bugs may just be more difficult to reproduce since FSO is more mature.  Edge cases can cause weird things.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Stardust on October 04, 2018, 09:29:43 pm
Hmm. Don't know what I did or did not do, but everything works now. False alarm! Back to your regularly scheduled programming.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Iain Baker on October 05, 2018, 06:09:48 am
Hmm. Don't know what I did or did not do, but everything works now. False alarm! Back to your regularly scheduled programming.

Yep, just like I was getting. I am not sure why, but I suspect it may have had something to do with changing the build preference settings. I had many mods fail to load, and when I enquired about them a few weeks ago I was told to use a nightly build instead.

That worked.

What is weird is that those mods now run fine with a stable build as well, despite those mods not receiving an update as far as I can tell. Perhaps Knossos is 'remembering' something from the working nightly builds and carrying them over the stable ones. Clever Knossos  :lol:
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Bryan See on October 05, 2018, 03:12:16 pm
Hmm. Don't know what I did or did not do, but everything works now. False alarm! Back to your regularly scheduled programming.

Yep, just like I was getting. I am not sure why, but I suspect it may have had something to do with changing the build preference settings. I had many mods fail to load, and when I enquired about them a few weeks ago I was told to use a nightly build instead.

That worked.

What is weird is that those mods now run fine with a stable build as well, despite those mods not receiving an update as far as I can tell. Perhaps Knossos is 'remembering' something from the working nightly builds and carrying them over the stable ones. Clever Knossos  :lol:
Why don't we streamline without compromising everything that made the Knossos launcher?
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Iain Baker on October 06, 2018, 07:07:45 am

Why don't we streamline without compromising everything that made the Knossos launcher?
[/quote]

Eh? Sorry for sounding dumb but I'm not sure what you mean.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Iain Baker on October 06, 2018, 07:47:15 am
Knossos Wish-List - to make it as noob-friendly as possible:

1)   For Knossos to automatically select the best build for a given mod (I understand this is in the works already?)

2)   For update notes to appear somewhere when a mod has an update available. Either in Knossos itself, or a link to a thread or wiki entry.

3)   Tooltips or text to indicate some of the terms, such ‘Stable, RC, nightly’ etc. This would be very useful for newcomers.

4)   To clean up some of the duplicate mods, or show a ‘most advanced version’ option. For example: FSPort, if played via the FSPort icon, is a very old version. If you play the FS1 campaign by choosing the Freespace campaign from the campaign room of a newer mod, you get a far more up-to-date version. I worked this out by trial end error, but a newbie may not know how to do this.

5)   An easy way to integrate the new HD cutscenes, possibly with a checkbox or similar so players can choose between vanilla and the HD remakes.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: mjn.mixael on October 06, 2018, 08:05:31 am
4 and 5 are there fault of mod owners and I strongly feel it is outside the scope of Knossos to start policing mod content.

As for 2... The next person to suggest that Knossos is responsible for mod changelogs is getting modeled as one of the Marines in Hall Fight so get can be brutally murdered. Mods will provide changelogs if they want. It hasn't historically been a thing that most mods have done with the possible exception of FSCRP releases. Knossos already provides a description field and thread link field where modders can include anything they want. If you want mods to start writing changelogs, you need to ask the authors for them.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: Iain Baker on October 06, 2018, 09:28:28 am
4 and 5 are there fault of mod owners and I strongly feel it is outside the scope of Knossos to start policing mod content.

As for 2... The next person to suggest that Knossos is responsible for mod changelogs is getting modeled as one of the Marines in Hall Fight so get can be brutally murdered. Mods will provide changelogs if they want. It hasn't historically been a thing that most mods have done with the possible exception of FSCRP releases. Knossos already provides a description field and thread link field where modders can include anything they want. If you want mods to start writing changelogs, you need to ask the authors for them.

Hi there, thanks for the heads up. I had a feeling rectifying some of these issues would be due to the mod creators, now I know which. I'll bring it up with them.

Please understand that none of this was meant as a dig, I'm simply tying to get HLP and Freespace as accessible as possible for a new audience. I put myself in the shoes of someone who is new and think 'how would they expect things to work.' This is especially true if they are younger and are accustomed to highly visual UIs that 'just work'. The whole 'Knossos experience' is very close to being this, which is a remarkable achievement BTW, so much more intuitive than what we had before. Kudos all round.

Perhaps I should have called it a 'Knossos end-user experience wish-list' as this would have been more accurate. My bad. Most end users of a product will not care who's is responsible for the various parts of a system that makes the product work. They will only care about whether the system as a whole works as expected. For example, if a game on Steam was having issues, most people wouldn't know, or indeed care, whether the problem was with valve of the people who made the game. The end user would be this  :lol: https://youtu.be/xhy7dXWjpAA
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: mjn.mixael on October 06, 2018, 10:31:21 am
For example, if a game on Steam was having issues, most people wouldn't know, or indeed care, whether the problem was with valve of the people who made the game. The end user would be this  :lol: https://youtu.be/xhy7dXWjpAA

This has never been my experience on Steam... WTF kinda Steam boards have you been on?

Of course Steam lists the publisher and has ways to contact them. Knossos has a link to the release thread, but doesn't (yet) list the mod author anywhere.
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: ngld on October 13, 2018, 01:33:36 am
0.13.2 has finally been released. This release fixes a few bugs (most importantly the FSO settings screen doesn't screw with the selected FSO build anymore) and improves a few error messages.
The full changelog is over on GitHub (https://github.com/ngld/knossos/releases/tag/v0.13.0).

Unfortunately, no macOS builds this time since the builds keep failing. Looks like there's an issue with one of the dependencies Knossos uses. Will have to investigate that later...

If anyone still encounters issues with launching mods, please use the "Enforce build requirements for mods" link on the new troubleshooting tab. If some mods have broken images, then that tab has a solution as well.
There are a few changes to the dev tab as well. The buttons on the left are new a bit more organized and you can decide if you want to delete your mod only from your local PC or from Nebula as well.
The dependency screen has been changed to hopefully cause less dependency conflicts in the future. If anyone's wondering, ~0.3.1 means >=0.3.1 && < 0.4.0. It basically means that the first two numbers have to match. In addition to that change, I've added a new note to the OP: If you change your mod dependencies, please change either of the first two version numbers. As long as everyone follows this rule, we shouldn't have any further conflicts.

Please don't ask what happend to 0.13.0 and 0.13.1...



@Stardust: The next time you encounter a similar issue, please provide a debug log. That'll help a lot.
@Iain: The "preferred stability" isn't a global setting to specify whether to use a stable or nightly build... it's a lot more complicated than that. In any case, if you want to check which build Knossos is currently using, the fastest way would be to launch a debug build and check the debug log.

1)   For Knossos to automatically select the best build for a given mod (I understand this is in the works already?)
This was already implemented a long time ago. The problem was that opening the FSO settings screen automatically selected a different build which overrode Knossos' decision. This release fixes that by adding the "Mod default" option to the list of available builds and ensuring that it's selected unless the user actually selected another build before.

2)   For update notes to appear somewhere when a mod has an update available. Either in Knossos itself, or a link to a thread or wiki entry.
We already have a link to the release thread (see the details screen) and uploaders can put changelogs in the mod description (as some already do).

3)   Tooltips or text to indicate some of the terms, such ‘Stable, RC, nightly’ etc. This would be very useful for newcomers.
Ideally, newcomers won't have to worry about this stuff. Since the only place where you'll see this is the "preferred stability" option, I'm not sure how we'd implement a tooltip there. A help text would be much more appropriate. However, most of the other options could also use some explanation.

4)   To clean up some of the duplicate mods, or show a ‘most advanced version’ option. For example: FSPort, if played via the FSPort icon, is a very old version. If you play the FS1 campaign by choosing the Freespace campaign from the campaign room of a newer mod, you get a far more up-to-date version. I worked this out by trial end error, but a newbie may not know how to do this.
I've thought about having moderators (similar to forum mods) who could take of stuff like this but for that to happen, I need to implement some kind of UI for them to use, we'd need volunteers to do the actual work and some kind of rule book. Regarding FSPort: If you read the mod description for both FSPort and FSPort MediaVPs, it's easy to tell which of the two is the "more advanced" version.

5)   An easy way to integrate the new HD cutscenes, possibly with a checkbox or similar so players can choose between vanilla and the HD remakes.
Isn't that already the case? Which mod specifically are you talking about?

Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: Iain Baker on October 13, 2018, 05:27:18 am
Quote from: Iain Baker on 06-10-2018, 08:47:15
4)   To clean up some of the duplicate mods, or show a ‘most advanced version’ option. For example: FSPort, if played via the FSPort icon, is a very old version. If you play the FS1 campaign by choosing the Freespace campaign from the campaign room of a newer mod, you get a far more up-to-date version. I worked this out by trial end error, but a newbie may not know how to do this.
I've thought about having moderators (similar to forum mods) who could take of stuff like this but for that to happen, I need to implement some kind of UI for them to use, we'd need volunteers to do the actual work and some kind of rule book. Regarding FSPort: If you read the mod description for both FSPort and FSPort MediaVPs, it's easy to tell which of the two is the "more advanced" version.

- I realised that a day or two after posting, Doh!


Quote from: Iain Baker on 06-10-2018, 08:47:15
5)   An easy way to integrate the new HD cutscenes, possibly with a checkbox or similar so players can choose between vanilla and the HD remakes.
Isn't that already the case? Which mod specifically are you talking about?

If it does that already I was not aware of it. As an example, 'FSPort MediaVPs' uses the original 'Ash' opening cutscene, where as 'Trimurti' uses the newer HD remaster version. It would be great if there was an easy option to get other mods to use them too, since there are a number of HD remastered cut-scenes now. I'm thinking noob-friendly maximum eye-candy option :-)

Or is this something that the mod creators would need to alter at their end?

Hope I'm making sense.
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: chief1983 on October 13, 2018, 08:44:11 am
@ngld would it be infeasible to detect when a mod changed their dependencies without a corresponding minor bump, and then prevent the mod from being uploaded?
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: EternalRuin on October 13, 2018, 12:14:34 pm
I just decided to fire up FS2 after a while, and figured this would be the way to go about it. I'm getting a critical error, though, here's the log

Code: [Select]
INFO:MainThread:launcher.main: Running Knossos 0.13.2 on PyQt5 and Python 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)].
INFO:MainThread:launcher.main: OpenSSL version: OpenSSL 1.0.2o  27 Mar 2018
INFO:MainThread:integration.init: Activating Windows integration...
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180725 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180924 (FSO)> is empty, ignoring it!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
INFO:MainThread:ipc.handle_message: Received IPC message ["focus"]
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FSO" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FSO" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FSO" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FSO" wasn't found!
INFO:Thread-1:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png"...
INFO:Thread-1:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png"...
INFO:Thread-1:util.download: Downloading "https://cf.fsnebula.org/storage/b6/c7/b86704ae47d1c8706c64351aa81442a7bdb983062874c7482df2691e0635"...
INFO:Thread-9:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png"...
INFO:Thread-9:util.download: Downloading "https://fsnebula.org/storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png"...
INFO:Thread-10:util.download: Downloading "http://swc.fs2downloads.com/builds/nightly/20181013_842dbb1/nightly_20181013_842dbb1-builds-Win32.zip"...
INFO:Thread-9:util.download: Downloading "http://swc.fs2downloads.com/builds/nightly/20181013_842dbb1/nightly_20181013_842dbb1-builds-Win64.zip"...
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
WARNING:Thread-20:repo.query: Repo.query(): Expected Spec but got Version instead! (Version('3.8.1-20171118', partial=True))
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!

Maybe it's the new update? Thanks!
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: Bryan See on October 13, 2018, 12:43:04 pm
I just decided to fire up FS2 after a while, and figured this would be the way to go about it. I'm getting a critical error, though, here's the log

Code: [Select]
INFO:MainThread:launcher.main: Running Knossos 0.13.2 on PyQt5 and Python 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)].
INFO:MainThread:launcher.main: OpenSSL version: OpenSSL 1.0.2o  27 Mar 2018
INFO:MainThread:integration.init: Activating Windows integration...
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180725 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180924 (FSO)> is empty, ignoring it!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
INFO:MainThread:ipc.handle_message: Received IPC message ["focus"]
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FSO" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FSO" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FSO" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FSO" wasn't found!
INFO:Thread-1:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png"...
INFO:Thread-1:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png"...
INFO:Thread-1:util.download: Downloading "https://cf.fsnebula.org/storage/b6/c7/b86704ae47d1c8706c64351aa81442a7bdb983062874c7482df2691e0635"...
INFO:Thread-9:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png"...
INFO:Thread-9:util.download: Downloading "https://fsnebula.org/storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png"...
INFO:Thread-10:util.download: Downloading "http://swc.fs2downloads.com/builds/nightly/20181013_842dbb1/nightly_20181013_842dbb1-builds-Win32.zip"...
INFO:Thread-9:util.download: Downloading "http://swc.fs2downloads.com/builds/nightly/20181013_842dbb1/nightly_20181013_842dbb1-builds-Win64.zip"...
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
WARNING:Thread-20:repo.query: Repo.query(): Expected Spec but got Version instead! (Version('3.8.1-20171118', partial=True))
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:web._get_mod: Couldn't find mod "FS2" (None)!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 244, in _get_mod
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "C:\knossos\knossos\web.py", line 646, in copyRetailData
  File "C:\knossos\knossos\tasks.py", line 1772, in __init__
  File "C:\knossos\knossos\repo.py", line 216, in query
knossos.repo.ModNotFound: Mod "FS2" wasn't found!

Maybe it's the new update? Thanks!
What of total-conversions?
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: EternalRuin on October 13, 2018, 01:34:15 pm
Total conversions appear to work fine.
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: darkhorsedan on October 14, 2018, 06:13:50 am
Hello,

Just bought Freespace 2 to play for the first time and wanted to try out the graphical improvements. I'm trying to use this Knossos installer but at the point during the setup where it's asking where my Freespace 2 retail game is installed I'm getting the following error message when I confirm its location:
"A critical error occurred! Knossos might not work correctly until you restart it. The error has been reported and will hopefully be fixed soon."

Knossos can see where it is but it's not working. When I restart Knossos and try to install any of the mods a separate box headed "Retail data missing" appears. Again it can see the folder but it doesn't want to install it. If I try to select any of the .exe files it brings up the same error message "A critical error occurred! Knossos might not work correctly until you restart it. The error has been reported and will hopefully be fixed soon."

Any ideas? When I initially installed Knossos my Norton anti-virus got jittery about it but I instructed it to leave well alone. I'm using the Gog version of the game and I'm on Windows 10 if that helps.

Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: jr2 on October 14, 2018, 07:38:06 am
Where is your GOG FreeSpace installed to?  Wondering if it's permissions?  Eh, someone who knows more will be along shortly, don't worry.  ;)
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: niffiwan on October 14, 2018, 08:15:33 am
IIRC ngld said there's a bug in the 0.13.x versions that'll be fixed soon. In the meantime you can try installing 0.12.4, install FS2 retail, then upgrade to 0.13.x.
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: darkhorsedan on October 14, 2018, 10:50:33 am
IIRC ngld said there's a bug in the 0.13.x versions that'll be fixed soon. In the meantime you can try installing 0.12.4, install FS2 retail, then upgrade to 0.13.x.

Thanks! Using the earlier version seemed to have worked!
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: ksotar on October 15, 2018, 09:31:12 am
IIRC ngld said there's a bug in the 0.13.x versions that'll be fixed soon. In the meantime you can try installing 0.12.4, install FS2 retail, then upgrade to 0.13.x.

Where to get old one?

UPD here https://github.com/ngld/knossos/releases
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: oljo on October 15, 2018, 12:20:14 pm
Hello, i get this error on xubuntu 18.04.1 when i launch knossos "I don't know how to handle "override_dh_link" i only know fso://

What to do?
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: nevar777 on October 15, 2018, 05:27:03 pm
Tearing my thinning hair out here.

Cannot get any mods working. Please look at attached image for sequence of events.

GTX1060 6Gb + 16Gb RAM. Windows 10 Home. Intel 7700HQ

Any ideas what this is or I'm doing wrong? Please help.

[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: niffiwan on October 15, 2018, 05:27:37 pm
Hello, i get this error on xubuntu 18.04.1 when i launch knossos "I don't know how to handle "override_dh_link" i only know fso://

What to do?

You can modify /usr/bin/knossos & remove "override_dh_link" from the file and (for me at least) it'll work as expected.

Or if you don't want to modify the file, just run this from a terminal:
Code: [Select]
python3 /usr/share/knossos/knossos/__main__.py
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: niffiwan on October 15, 2018, 05:28:48 pm
Tearing my thinning hair out here.

Cannot get any mods working. Please look at attached image for sequence of events.

GTX1060 6Gb + 16Gb RAM. Windows 10 Home. Intel 7700HQ

Any ideas what this is or I'm doing wrong? Please help.

Assuming this is occurring on the latest version (0.13.2) then try this:

IIRC ngld said there's a bug in the 0.13.x versions that'll be fixed soon. In the meantime you can try installing 0.12.4, install FS2 retail, then upgrade to 0.13.x.

You could also see if Diaspora will install & run ok as it doesn't require the FS2 retail install.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 16, 2018, 10:01:48 am
Knossos 0.13.3 has been released, it fixes both the critical error message when trying to install retail data as well as the override_dh_link issue on Ubuntu (and derivates).

Sorry about the delay.
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: oljo on October 17, 2018, 02:10:51 pm
Hello, i get this error on xubuntu 18.04.1 when i launch knossos "I don't know how to handle "override_dh_link" i only know fso://

What to do?

You can modify /usr/bin/knossos & remove "override_dh_link" from the file and (for me at least) it'll work as expected.

Or if you don't want to modify the file, just run this from a terminal:
Code: [Select]
python3 /usr/share/knossos/knossos/__main__.py


Thanks! will try it
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: nevar777 on October 18, 2018, 12:59:36 pm
Firstly a big thankyou for your help, and wow the game I loved 20 years ago lives again....buuut

I changed my HUD colour and got this (attached) how do I fix this as the game now won't run (who'd have thought changing HUD colour would have triggered this).

Hitting debug would step me through the game up to the command briefing, but then it would pause at the game itself and then not run (all the while putting that error box up and stepping through each scene change).

I will say though bugs n all this is incredible work (cockpit mod would be nice but in reading I don't think there are any reliable mods for this).

[attachment stolen by Russian hackers]
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on October 18, 2018, 01:46:01 pm
Firstly a big thankyou for your help, and wow the game I loved 20 years ago lives again....buuut

I changed my HUD colour and got this (attached) how do I fix this as the game now won't run (who'd have thought changing HUD colour would have triggered this).

Hitting debug would step me through the game up to the command briefing, but then it would pause at the game itself and then not run (all the while putting that error box up and stepping through each scene change).

I will say though bugs n all this is incredible work (cockpit mod would be nice but in reading I don't think there are any reliable mods for this).

Were you using a mod or playing regular Freespace 2? Also, what FSO build are you using?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: nevar777 on October 18, 2018, 04:05:49 pm
Ok so the versions I'm running are as follows:

knossos 12.4 (because my first attempt at this was with 13.2 and it gave me the finger)
base FSO 3.8.0-3
Freespace port 1.0.0
FS Port MediaVPs 3.7.2

Also Freespace 2 (basic FSO update) crashed with the same error.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 19, 2018, 02:01:00 am
Knossos 0.13.3 fixed the bug you encountered in 0.13.2 so it's safe to update to that. It most likely won't resolve this specific issue, though.
Can you try and go to Knossos' settings, select Nightly as the preferred stability in the Knossos section, save, update FSO and launch the mod again? It will most likely crash with the same error but I'm hoping the conversion to JSON will work regardless. If it worked, you'll find a file under %AppData%\HardLightProductions\FreeSpaceOpen\data\players\<PILOTNAME>.json. Please attach that file to your post (if it exists).

If that didn't work and you still can't launch FSO, you could try cloning your pilot but aside from that IIRC the only solution is deleting your pilot.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: [email protected] on October 19, 2018, 05:42:47 pm
 :banghead:
I have problems with knossos launcher. I run it under ubuntu, and it went jus fine until just a few days. Awesome program to play freespace, I even downloaded some mods and they were just great!!

The problem is that now I cant get knossos to start, it only give me this warning: "I don't know how to handle "\override_dh_link"! I only know fso:// .", click "OK" and then nothing. This message shows from the very first day, but the program ran anyways so i didnt even bother. Now it doesn't i was left in the middle of the tango campaign!

Please help me solve this issue.
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: niffiwan on October 19, 2018, 08:45:55 pm
You can modify /usr/bin/knossos & remove "override_dh_link" from the file and (for me at least) it'll work as expected.

Or if you don't want to modify the file, just run this from a terminal:
Code: [Select]
python3 /usr/share/knossos/knossos/__main__.py
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: nevar777 on October 20, 2018, 04:53:14 pm
Knossos 13.3 works great and thanks again for your amazing support.

Question: where are the pilot profiles stored as I did a full uninstall to kill the issue BUT the pilot data remained...are they stroed in the windows user profile?

Again thanks to you all for your outstanding help.

A personal view point having played this 20 years ago when it first came out. I remember a game that was similar to wing commander but there was one huge difference that hit you immediatly: flight model.

Wing Commander dog fights were basically a ship moving diagonally across your screen from corner to corner - fast and annoying.
Freespace came and dog fights were memorable glide like an eagle affairs, like the best elements of a star wars dog fight.

Graphically at the time I was running a voodoo 1 at 640x480 and the graphics were amazing.

Move forwards 20years (yes sadly it was that long ago and I was 21) and time had not been kind to the original which now somehow looked like everything had been rendered to look like a half dissolved alchazeltser (buggered if I know how to spell it but you get the idea).

Now because of the efforts of all of you over the last 18 years my old gaming friend has come home.

I've missed this game of a simpler time.

Thankyou all.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 20, 2018, 05:36:34 pm
Knossos 13.3 works great and thanks again for your amazing support.
Great, hope you're having fun with the game!

Question: where are the pilot profiles stored as I did a full uninstall to kill the issue BUT the pilot data remained...are they stroed in the windows user profile?
%AppData%\HardLightProductions\FreeSpaceOpen\data\players

I've missed this game of a simpler time.

Thankyou all.
You're welcome.  :)
Title: Re: PUBLIC BETA: Knossos 0.13.2 (combined launcher/installer)
Post by: [email protected] on October 21, 2018, 05:17:02 am
You can modify /usr/bin/knossos & remove "override_dh_link" from the file and (for me at least) it'll work as expected.

Or if you don't want to modify the file, just run this from a terminal:
Code: [Select]
python3 /usr/share/knossos/knossos/__main__.py

You are a genius, thanks   ;) :yes:. Now knossos starts with no problem, and without the annoying  warning too!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on October 21, 2018, 08:21:20 pm
Hey... is www.knossos.com available?  It seems like it to me, but I'm not sure.  Could this be a thing, or is it too expensive?  How much would it cost to register?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 21, 2018, 08:44:48 pm
Knossos.com has been registered with GoDaddy since 2001. Apparently, they're auctioning it off with a minimum bid of over $6000... XD

I'd rather wait for the auction to finish (on 2019-01-19) and see what happens.
Anyway, we already have https://fsnebula.org/knossos so IMO we're fine.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: TrashMan on October 22, 2018, 02:56:40 am
Where does Knossos place screenshots? Can't find them anywhere.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: woutersmits on October 22, 2018, 03:37:43 am
it put on @[email protected]/rosming/herdlightproductions/screenshots
always its on my saves too
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: tomimaki on October 22, 2018, 05:22:32 am
C:\Users\your_account\AppData\Roaming\HardLightProductions\FreeSpaceOpen\screenshots
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: chief1983 on October 22, 2018, 06:31:52 am
Perhaps it would be prudent to point out that Knossos has nothing to do with screenshots, they are generated by FSO and put where it puts all of its data files which hasn't changed whether installed with Knossos or any other method.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 22, 2018, 09:53:34 am
It's also worth pointing out that you can click the small picture icon in Knossos (below the settings button) to open your screenshot folder. Much easier than manually opening the folder.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on October 22, 2018, 10:55:41 am
Knossos.com has been registered with GoDaddy since 2001. Apparently, they're auctioning it off with a minimum bid of over $6000... XD

I'd rather wait for the auction to finish (on 2019-01-19) and see what happens.
Anyway, we already have https://fsnebula.org/knossos so IMO we're fine.

I see.  Well, I put in a few shortcuts, https://is.gd/knossos and https://is.gd/Knossos   (Why?  Well, try Googling 'Knossos' to find the site if you forget it's under fsnebula like I do on a regular basis... :ick: )
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 22, 2018, 01:24:55 pm
I doubt we can get on the first page of search results for "Knossos" since there's way too much stuff with the same name. However, if you search for "Knossos FS2", most results on the first page are for Knossos.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Nightmare on October 22, 2018, 01:58:52 pm
Actually, the chance that somebody blindly enters "Knossos" on Google and hopes to find HLP instead of an antique palace without knowing what FS2 is is sadly rather small. :(
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on October 22, 2018, 10:59:56 pm
Actually, the chance that somebody blindly enters "Knossos" on Google and hopes to find HLP instead of an antique palace without knowing what FS2 is is sadly rather small. :(

Yup

I doubt we can get on the first page of search results for "Knossos" since there's way too much stuff with the same name. However, if you search for "Knossos FS2", most results on the first page are for Knossos.

This is what I end up doing after the first results list hits.  (I mean, who else would use that word?? lol... guess it means something in ancient Greek mythology or something)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: CT27 on October 23, 2018, 06:50:34 pm
I decided to try out Knossos.


I see where I can download campaigns, but how do I go about downloading builds (stable builds and nightlies)?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on October 23, 2018, 07:42:12 pm
Currently, builds are displayed along with the rest of the mods, so look for FSO.  This should change in the future with tags.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: CT27 on October 23, 2018, 08:21:06 pm
I have some more simple questions if that's okay.  For now:

I want to make sure I installed things in the correct places:
Is it okay that the "Knossos" folder got installed in the "Program Files (x86)" folder?

Also, is it okay that I put the game folder for Knossos ("FreespaceOpen") in the same folder ("Games") as my current Freespace 2 folder ("Freespace2")?  I mean, I didn't put FreespaceOpen into Freespace2, but rather those two folders (FreespaceOpen and Freespace2) are both in C:\Games
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on October 23, 2018, 08:52:30 pm
Yes and yes.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Knarfe1000 on October 24, 2018, 07:43:28 am
Hello,

I´m new to Knossos and want to know, if I can use WXLauncher and Knossos (for mods which are only available there) parallely?

Can I use any harddrive to install it or do I have to use C: ?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 24, 2018, 09:00:48 am
You can use wxLauncher and Knossos at the same time. However they use different folder structures so you'll have to use two different game folders.

You can install Knossos on any hard drive you want. However, the directory you select in the installer will only contain Knossos. The actual game files (mods, FSO, etc.) will be stored in a separate directory which you can select after starting Knossos for the first time (though you can change it afterwards in the settings). Make sure to select a directory outside of C:\Program Files for that.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Bryan See on October 24, 2018, 02:45:52 pm
You can use wxLauncher and Knossos at the same time. However they use different folder structures so you'll have to use two different game folders.

You can install Knossos on any hard drive you want. However, the directory you select in the installer will only contain Knossos. The actual game files (mods, FSO, etc.) will be stored in a separate directory which you can select after starting Knossos for the first time (though you can change it afterwards in the settings). Make sure to select a directory outside of C:\Program Files for that.
What about the mod development folders created by Knossos? Will they be transferred to another machine that contains the Knossos launcher?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 24, 2018, 04:02:54 pm
Mods in dev mode and normal mode work the same. You have to install them on the machine before you can use them. Obviously, you can only install uploaded mods.

That said, I'm not sure what that has to do with the previous question.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: X3N0-Life-Form on October 25, 2018, 12:14:59 am
Nothing, Bryan just tends to make random "what about" questions that are vaguely related to whatever topic he posts in.


Some minor comments regarding development mods :
- Packages kind of confused me the first time around, if it's not already on the TODO list may I suggest adding a small blurb in the "Add package" popup to describe what it is ? Something along the lines of "A package represents a single .vp file, and must be structured like <Knossos mod library>/<my mod>/<my package>/data/[missions|tables|models|whatever]"
- In the launch FSO tab, the buttons go :
[Play] [FRED]
[FRED Debug] [Fast Debug]
I feel it would make more sens to "align" those, like
[Play] [Fast Debug]
[FRED Debug] [FRED]
or
[Play] [FRED]
[Fast Debug] [FRED Debug]

Note to self : figure out how difficult it would be to submit a proper pull request for both these suggestions. Knossos is on github, right ?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Knarfe1000 on October 25, 2018, 12:50:45 am
You can use wxLauncher and Knossos at the same time. However they use different folder structures so you'll have to use two different game folders.

You can install Knossos on any hard drive you want. However, the directory you select in the installer will only contain Knossos. The actual game files (mods, FSO, etc.) will be stored in a separate directory which you can select after starting Knossos for the first time (though you can change it afterwards in the settings). Make sure to select a directory outside of C:\Program Files for that.

Thanks! I installed everything yesterday and it works great. Much more comfortable than WXLauncher.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 25, 2018, 01:25:11 am
- Packages kind of confused me the first time around, if it's not already on the TODO list may I suggest adding a small blurb in the "Add package" popup to describe what it is ? Something along the lines of "A package represents a single .vp file, and must be structured like <Knossos mod library>/<my mod>/<my package>/data/[missions|tables|models|whatever]"
There's already an explanation on the dev tab that's displayed until you add the first package. Adding it to the add package dialog is probably a good idea though.
The path should be something like this: <Knossos mod library>/<TC>/<my mod>/<my package>/data/... (you forgot the TC part)
If the mod is a normal FS2 mod, then the TC folder is FS2.

- In the launch FSO tab, the buttons go :
[Play] [FRED]
[FRED Debug] [Fast Debug]
I feel it would make more sens to "align" those, like
[Play] [Fast Debug]
[FRED Debug] [FRED]
or
[Play] [FRED]
[Fast Debug] [FRED Debug]
That's a bit complicated since those buttons are automatically generated based on the selected build. For example a recent nightly will additionally have the buttons "QtFRED" and "QtFRED Debug".

Note to self : figure out how difficult it would be to submit a proper pull request for both these suggestions. Knossos is on github, right ?
Yes, here's the code for adding a new package (https://github.com/ngld/knossos/blob/6321576f27bae343d4f3cee6c43ec77404b37773/html/templates/kn-page.vue#L560-L579) and here is the code to generate the launch buttons (https://github.com/ngld/knossos/blob/6321576f27bae343d4f3cee6c43ec77404b37773/html/templates/kn-devel-page.vue#L569-L577). The first button there is the play button and the second is a for loop that generates all the other buttons.

Finally, here's the package explanation (https://github.com/ngld/knossos/blob/6321576f27bae343d4f3cee6c43ec77404b37773/html/templates/kn-devel-page.vue#L643-L651) I mentioned earlier.

If you have any questions (how to set it up, where everything is, etc.), feel free to ask.



@Knarfe1000: Thanks for the feedback! :)  Let me know if you encounter problems / bugs.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Smooticus on October 30, 2018, 04:32:42 am
Loving the Knossos portal! made it super easy to get back into freespace.

Got a minor bug that I should let you all know about. (I'm on version 0.13.3)

The second time I tried to launch the new MediaVPs campaign I got an error saying something about an unrecognized joystick. I have never used a joystick since getting the launcher, and did not have one plugged into the computer. Went into settings, nothing was detected. I noticed that the "force feedback" box was checked. I unchecked it, and it started working for me.

So it seems to me that theres some code conflict where having it checked forces the client to look for a joystick.

Let me know if you have any other questions about the bug.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 31, 2018, 12:37:50 am
The force feedback actually doesn't matter in that situation. Simply saving your settings already solved the problem.

That error message shows up if a joystick is configured in your fs2_open.ini, that joystick can't be detected and you haven't saved your Knossos settings with a recent version. There's a problem with the SDL2 library that more recent FSO builds use which can result in FSO not detecting your joystick. I've added a workaround in Knossos for that but to make it work, Knossos has to save your selected joystick in its own settings. If that hasn't happened yet and FSO can't detect the currently selected joystick, Knossos doesn't know if that is the result of the SDL2 issue or simply because the joystick isn't present. Once you've saved your settings (regardless of whether you changed anything or not), Knossos remembers your selected joystick (or if you select "No joystick", that instead) and can handle the situation appropriately.

So, "working as designed", I guess.

Quote
Your fs2_open.ini contains a joystick which this FSO version can't detect and Knossos doesn't remember your joystick. Please go to Knossos' settings, select your joystick, save and try again.
That's the error Knossos displayed and pretty much says the same stuff I explained above (though it isn't as long-winded  :P).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: krevett62 on November 04, 2018, 10:19:14 am
Hi it's been a long time since I last launched fso and as I don't use knossos (yes I know what a loser I am) I got a little question: when I click I want to download individual files I know what i'm doing is the hash provided from the 7zip archive or from the vp file itself?

Edit: well nvm my question is dumb it's the 7zip obviously...it would be nice for users like me who love to manually install to have a way to know which of the files are updated to avoid downloading the whole mod again if only the core has been updated for example. Perhaps adding a date with the hash to know when the file was last updated in knossos?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Novachen on November 14, 2018, 03:42:24 pm
After some time i have used to establish several other installation methods, i thought about to reupload newer versions of some of my other mods on Knossos, so that it can be used as an alternative installation method.

But because of two issues, i was not able to do that, so far. Even the second one would be fixable with the 'To bury one's head in the sand' method. The first one is not.
Quote
"Your mod" requires "MediaVPs" which has conflicting requirements: ~3.8.2 (Your mod), ==3.6.10 (the base mod)

In my opinion only a mod developer by itself should have the responsibility that its own mod is working. I think it would be better, if the requirements of the base mod should be ignored if the mod is used as a requirement of another mod or overriden atleast if there are different versions of the same requirements.

Quote
character limit of the description
Well, because of my (this time it is only in english) detailed description together with an also detailed changelog, i once again hit the online character limit of the description of one of my mods.
Maybe you should display the available characters i have left in the editor screen, because otherwise i have to check the description lenght everytime with another program, which is not very intuitive. Also the character limit is not in effect if you use Knossos offline only. Online and Offline descriptions should show the same behavior in my opinion. So there should be a limit in the editor field at general or we are talking about the deletion of this limit once more :).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Bryan See on November 20, 2018, 06:57:40 pm
What about private mods?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on November 20, 2018, 10:41:03 pm
Sorry for the lack of replies. Didn't have much time to work on Knossos lately.

Perhaps adding a date with the hash to know when the file was last updated in knossos?
That information isn't stored right now so I'd need to add it but that shouldn't be too hard. I'll add it when I have time.

In my opinion only a mod developer by itself should have the responsibility that its own mod is working. I think it would be better, if the requirements of the base mod should be ignored if the mod is used as a requirement of another mod or overriden atleast if there are different versions of the same requirements.
This has been discussed on Discord as well with the result that I'll try and change the dependency resolver allowing mods to override the version requirements of other mods in the same dependency chain.

Maybe you should display the available characters i have left in the editor screen, because otherwise i have to check the description lenght everytime with another program, which is not very intuitive. Also the character limit is not in effect if you use Knossos offline only. Online and Offline descriptions should show the same behavior in my opinion.
Sounds like a good idea. I never thought anyone would hit the limit so I hadn't considered displaying (or checking) the limit in Knossos itself. Clearly I was wrong.

So there should be a limit in the editor field at general or we are talking about the deletion of this limit once more :).
Removing the character limit is not practical since there's also a limit imposed by the DB storing the metadata and having huge descriptions could cause problems elsewhere. For the record, the current character limit is 10240 (~ 10 KiB).

What about private mods?
What about them?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ruger392 on December 16, 2018, 09:22:26 pm
Just letting you know I've found a rather interesting bug. After some time (exact conditions uncertain, will update if I figure them out), launching mods with FS2 3.8.1 just... stops working. After Knossos starts, trying to launch a mod with 3.8.1 for the first time yields an "FSO is launching" notification for about five seconds after which the notification disappears and nothing happens. Further attempts to launch the game result in the same message for about half a second.

Deleting all data in the \appdata\Roaming\HardLightProductions folder except the "data" folder seems to fix the issue until it breaks again some time later. It's likely that there is one specific file in there that is causing the problem, but I haven't been able to experiment enough to find out what it is yet. If I do find out, I'll update this post.

FS2 3.8.0 and earlier versions work fine; the problem is only with FS2 3.8.1.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Iain Baker on December 16, 2018, 11:30:24 pm
Just letting you know I've found a rather interesting bug. After some time (exact conditions uncertain, will update if I figure them out), launching mods with FS2 3.8.1 just... stops working. After Knossos starts, trying to launch a mod with 3.8.1 for the first time yields an "FSO is launching" notification for about five seconds after which the notification disappears and nothing happens. Further attempts to launch the game result in the same message for about half a second.

Deleting all data in the \appdata\Roaming\HardLightProductions folder except the "data" folder seems to fix the issue until it breaks again some time later. It's likely that there is one specific file in there that is causing the problem, but I haven't been able to experiment enough to find out what it is yet. If I do find out, I'll update this post.

FS2 3.8.0 and earlier versions work fine; the problem is only with FS2 3.8.1.


I have noticed this as well. As a workaround, I have found changing the 'Preferred Engine Stability' setting from 'Stable' to 'RCs' or 'Nightlies' sometimes fixes this.



Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on December 17, 2018, 02:53:13 am
Hm... could it be that this bug appears after you unplug a controller and disappears once you go to the settings page and save (don't even need to change anything)?

@ruger392: Instead of deleting everything in the AppData folder, deleting (or renaming) the fs2_open.ini is probably enough. Would be interesting to see the difference between one version that causes the bug and another that works fine.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ruger392 on December 17, 2018, 06:52:45 pm
Hm... could it be that this bug appears after you unplug a controller and disappears once you go to the settings page and save (don't even need to change anything)?

@ruger392: Instead of deleting everything in the AppData folder, deleting (or renaming) the fs2_open.ini is probably enough. Would be interesting to see the difference between one version that causes the bug and another that works fine.

I've done some more in-depth testing and come up with some interesting results.

If I delete fs2_open.ini, connect a new controller and disconnect the previously selected one, then start Knossos, then run a mod, the game launches fine. If I try to start it again, I get the bug. The newly created fs2_open.ini shows
CurrentJoystickGUID=None
If I then select the new controller in settings and save, fs2_open.ini shows
CurrentJoystickGUID=4f04ffff000000000000504944564944
If I then start a mod, it launches and fs2_open.ini changes to
CurrentJoystickGUID=030000004F040000FFFF000000000000
From there, the game launches every time and has no problems.

If I disconnect the selected controller, the game still runs. If I save settings without changing anything (the joystick drop-down is blank), I get the bug and fs2_open.ini shows
CurrentJoystickGUID=4f04ffff000000000000504944564944

If instead of saving settings, I restart Knossos, I get the bug and fs2_open.ini shows
CurrentJoystickGUID=030000004F040000FFFF000000000000
Reconnecting the controller doesn't change anything. Saving settings without changing anything (the joystick drop-down shows the controller) doesn't help and fs2_open.ini shows
CurrentJoystickGUID=4f04ffff000000000000504944564944
Switching the joystick to "No joystick" and saving allows the game to launch. fs2_open.ini shows
CurrentJoystickGUID=
Re-selecting the controller and saving yields the bug and
CurrentJoystickGUID=4f04ffff000000000000504944564944
Manually setting CurrentJoystickGUID to 030000004F040000FFFF000000000000 doesn't help.

With CurrentJoystickGUID=4f04ffff000000000000504944564944 or CurrentJoystickGUID=030000004F040000FFFF000000000000, restarting Knossos from that point allows the game to launch and everything works fine.

Working and bugged fs2_open.ini files attached (in an archive because the site wouldn't let me upload .inis)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: bling on December 17, 2018, 07:14:48 pm
I really like Knossos and prefer it to installing mods the old-fashioned way.  :yes:

I've encountered an issue and am not sure whether it's related to Knossos, specific mods, or my configuration.  :confused:

Some mods run using the settings I specify for them using Details > Options > FSO Settings.

Some mods seem to ignore those settings altogether, and instead use 640x480 resolution with special effects off.

Please help me troubleshoot this issue.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on December 17, 2018, 07:33:39 pm
@ruger392: So first, a little background on the different UUIDs: Newer FSO builds use a more recent version of SDL (2.0.8) than the latest stable builds. Unfortunately, SDL changed how UUIDs for joysticks are generated which means that the same joystick has a different UUID depending on which SDL version you're using (great, isn't it? /s). Knossos thus detects which SDL version is currently in-use and writes the appropriate UUID to fs2_open.ini. This bug appeared around the time I added this feature so I'm fairly certain that the code handling this process is causing the issue. I haven't been able to reproduce the bug or figure out what is going wrong so I haven't been able to fix it.

CurrentJoystickGUID=None
This isn't ideal (the value should just be an empty string) but doesn't matter since it doesn't affect FSO.

If I then select the new controller in settings and save, fs2_open.ini shows
CurrentJoystickGUID=4f04ffff000000000000504944564944
If I then start a mod, it launches and fs2_open.ini changes to
CurrentJoystickGUID=030000004F040000FFFF000000000000
From there, the game launches every time and has no problems.
The first is the UUID from the old SDL version (which Knossos uses internally) and the latter is from SDL 2.0.8. So this is to expected.

If I disconnect the selected controller, the game still runs. If I save settings without changing anything (the joystick drop-down is blank), I get the bug and fs2_open.ini shows
CurrentJoystickGUID=4f04ffff000000000000504944564944
[...]
Manually setting CurrentJoystickGUID to 030000004F040000FFFF000000000000 doesn't help.
[...]
With CurrentJoystickGUID=4f04ffff000000000000504944564944 or CurrentJoystickGUID=030000004F040000FFFF000000000000, restarting Knossos from that point allows the game to launch and everything works fine.
This seems to suggest that some kind of internal state (which is cleared on restart) gets messed up when launching FSO if the currently saved controller isn't found. However, this is caused by the value stored in Knossos' configuration and not the one stored in fs2_open.ini (both values are checked before starting FSO). The weirdest thing is that Knossos is supposed to leave the FSO configuration alone if the joystick specified there is detected by FSO. The fact that setting the correct value manually indicates that the bug occurs before Knossos can compare the two values. It also further proves that this is a Knossos bug and FSO is behaving properly.

What happens if you trigger the bug and set CurrentJoystickGUID to an empty string (CurrentJoystickGUID=) before launching FSO again? Does that solve the problem?


@bling: I'm glad you like Knossos! Can you list one mod which is working properly and one that's not? Also, please post a debug log for a mod that's ignoring your options. You can do that by clicking on the dropdown button for the mod (or the Options button on the Details page) and selecting "Run FastDebug". Once you're in the mainhall, exit the game and click "Upload debug log" in the same menu as before. Finally, copy and paste the link here.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: bling on December 17, 2018, 07:58:55 pm
@bling: I'm glad you like Knossos! Can you list one mod which is working properly and one that's not? Also, please post a debug log for a mod that's ignoring your options. You can do that by clicking on the dropdown button for the mod (or the Options button on the Details page) and selecting "Run FastDebug". Once you're in the mainhall, exit the game and click "Upload debug log" in the same menu as before. Finally, copy and paste the link here.

Blue Planet Complete runs using the set resolution (1920x1080).
Ancient-Shivan War runs using what I suppose is the default resolution (640x480), even though I have it set the same way as for BPC.

Here's the log file (https://fsnebula.org/log/5c180596cb0d3328fefd57ef), which curiously shows 1920x1080 resolution set.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on December 17, 2018, 08:03:46 pm
Is the resolution ACTUALLY 640x480 or do you think so because you see black bars on the left and right sides?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: bling on December 17, 2018, 09:01:34 pm
It's... more of a feeling, actually.

I've attached a screenshot of each.

To me, it seems ASW is low-res. Barely anything can be seen on the screen, the ships seem huge.

Whereas BPC seems high-res.

Could it just be the UI scaling differently? Or models of different detail?

[attachment deleted by admin]
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: MitoPL on December 17, 2018, 09:31:45 pm
I'd say it's fine - both screenshots are in 1080p, but ASW is kinda old now and uses a custom HUD that was made like that. On the other hand, BPC's hud is scaled differently and much more transparent. Take into consideration that BPC uses a different font in some places, which IMO is more readable than the one used in retail, and in your second screenshot the camera is about... 1 kilometer or more behind your vessel.

Also, if you have got black bars on the sides of your screen in menus and it looks like they're displayed in 4:3, try the "Strech interface to fill screen" flag under Details -> Options -> FSO options -> Gameplay. Though I think it should be on by default.

(I might be a bit wrong here, I haven't played ASW in a long time)

Also, does ASW use a different fancy animation on its mission load screens? I recall it being a very nice touch that some mods around could use.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ruger392 on December 18, 2018, 06:41:42 pm
What happens if you trigger the bug and set CurrentJoystickGUID to an empty string (CurrentJoystickGUID=) before launching FSO again? Does that solve the problem?

It does, in both bugged states (after deleting the .ini and after restarting Knossos with a disconnected controller)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on December 27, 2018, 09:26:22 pm
When installing a mod that depends on another mod that is not installed (eg: JAD 2.22 depends JAD 2.21), the Launcher will snap to "Installed" as the status for the dependency, even though the dependency is still installing, as can be seen in the detailed installation screen.  There is no status bar at the bottom of the dependency mod as it is installed, either.

Very small nitpick for the back-burner, unless it's a two-second easy fix.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on December 27, 2018, 09:50:33 pm
Additionally (and this one is more serious as if it's a bug which I think it is, it's eating bandwidth), it appears some dependencies are re-installed when they don't need to be, however, I might be not realizing there's several different MediaVPs being referenced??  Unsure.  I noticed some MediaVPs that were already downloaded & installed  were installed again for some mods.
 I'll try to post the Knossos log in case that helps.  I have screenshots showing this happening with multiple mods, and it's only certain components, like MV_Music (which makes me think it's not just a different MVPs version required, but a bug).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on December 27, 2018, 10:59:54 pm
If you manage to click the blue "Installing..." icon on a mod before it can switch out to its completed state (mod has finished installing but user managed to click for details while  it was changing states) then Knossos displays a rather dire warning that it won't work properly until it's been restarted and the error has been reported and hopefully will be fixed.  Seems to work just fine afterwards, though (doesn't close, you can just click "ok" and go about your business as usual).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Bryan See on December 27, 2018, 11:45:14 pm
What about cross-machine mod development?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on December 27, 2018, 11:48:11 pm
What about cross-machine mod development?

symlink or synchronize mod folder with a folder in Google Drive, Dropbox, OneDrive, etc?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on December 28, 2018, 12:35:56 am
OK, I have the Knossos log file, the .json files from appdata\roaming\knossos in case they matter, and a few screenshots showing the random files being re-downloaded (MV_Music and MV_Radaricons usually).  Clicky (https://drive.google.com/drive/folders/1gPTPG0iR3YpOMVjxestw5tJ4unmH9oOa?usp=sharing) (Google Drive link)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on December 28, 2018, 05:10:44 am
@ruger392: Thanks for the help. Not quite sure, yet, what is causing the issue but at least now I know that the bug happens either when Knossos looks up the connected joysticks or queries FSO for the same list.

@jr2: Hm... we had a similar bug in the past but it's been a while that someone has reported it so I assumed it's been fixed. Meh. It's fairly low-priority IMO since it's very hard to debug (I can't reproduce it and honestly it's VERY annoying to figure out the root cause since it's quite complicated) and it doesn't break anything. There are other more pressing issues right now but if you can figure out WHY this happens, I'd be glad to fix it. Here's the relevant code (https://github.com/ngld/knossos/blob/develop/knossos/tasks.py#L401) in case anyone wants to look into it.

Not sure about the critical error. Can't find the report right now. Could you send me a log with the error inside?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on December 28, 2018, 07:45:22 pm
It's in the Google Drive link.  If that Error Log doesn't have the critical error, then Knossos lied (it was all one big session, so it has to be in that log).  I was hoping that the log could shed some light on the re-downloading issues as well, but if not *shrug*.  PS When it re-downloads a random file, I think it skips the verification where it checks that all prerequisites' files are ok.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jg18 on December 29, 2018, 06:27:28 pm
I for one think this is cool.

(https://joshuaglatt.com/images/knossos_sorting_menu.png)

Last Played also works and appears in mod details.

Technical details (https://github.com/ngld/knossos/pull/156)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: 0rph3u5 on December 30, 2018, 11:01:37 pm
Question:

Why is it showing me this and then only giving me a 3.8.0 build when I start up? ("Stable" build preference)
-changed to attachment-

I just spend over an hour wondering what I had broken now, when I started getting a lot inexplicable error messages on start-up...

[attachment deleted by admin]
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on December 30, 2018, 11:48:38 pm
I can't see your image :)

I think the answer might be; you need to set build stability to "nightlies" to get anything more recent than 3.8.0.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: 0rph3u5 on December 31, 2018, 12:13:27 am
I can't see your image :)

changed to attachment in the post above.

I think the answer might be; you need to set build stability to "nightlies" to get anything more recent than 3.8.0.

I get that (and I am now on the "nightlies" preference), but why is then telling me that I had a build that it didn't give me?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on December 31, 2018, 01:06:54 am
Sorry, which build did it not give you? I can see 3.8.0, one nightly & the nuWoD build?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: 0rph3u5 on December 31, 2018, 01:32:00 am
Selecting and "launching" with the 3.8.1-20181229 selected launches the 3.8.0 build instead.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on December 31, 2018, 03:16:31 am
huh - that's weird!  Does the knossos log confirm that it's using 3.8.0, including listing all the cmdline options?

%appdata%\knossos\log.txt
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Bryan See on December 31, 2018, 04:08:40 am
Same thing may have happened on Shattered Stars: A Deepness Within.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: 0rph3u5 on January 02, 2019, 07:44:32 pm
huh - that's weird!  Does the knossos log confirm that it's using 3.8.0, including listing all the cmdline options?

%appdata%\knossos\log.txt

Fixed. Disregard, User Error was the cause.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on January 03, 2019, 11:23:38 am
Why is it showing me this and then only giving me a 3.8.0 build when I start up? ("Stable" build preference)
Sounds like a bug. I'll look into it.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: 0rph3u5 on January 04, 2019, 03:54:01 am
Why is it showing me this and then only giving me a 3.8.0 build when I start up? ("Stable" build preference)
Sounds like a bug. I'll look into it.

It was user error, don't sweat it ... but I would suggest that you put a line on the FSO section of the Development Tab that clarifies its function and relation to the FSO Settings elsewhere. I got confused and in the days before release when you are already knee deep is FREDing busy work, one more things to be confused about is ... frustrating.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Dongmyeong on January 06, 2019, 02:29:13 pm
Just reinstalled FS2 a few days ago after several years to find out what's new and decided to give Knossos a try.
I had one issue so far:
I first installed the latest MediaVPs and then when running it I got an error about missing stuff. It was only through half an hour of googling it, that I eventually found out I need to use the latest nightly build to run it and chance to knossos settings from stable to nightly.
Why is the MediaVPs not DLing those already, like other mods DL the OpenFS2 build they run on? If that's not possible for technical reasons, then at least make a note of what you need to do to run in in the MediaVPs details, please.

Everything else seems to work find so far. Have one feature request:
Make a "create shortcut" option to run FS2open with a selected mod directly from the desktop without going through the launcher, thereby skipping the initialization and checking for updates each time.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Gu57avo on January 06, 2019, 03:55:25 pm
So, I've been trying to make this game work for the past 3 days, I would have been fine if i could play the original one.
But anyway, fs2 didn't work, and i tried fso, it didn't run because my graphics card doesn't support OpenGL 3.2, and i didn't find a way to change the video mode except in one of the launchers that didn't also give options except for yes you guessed it... OpenGL
So i decided to try knossos to see if it was any different, and it gave me the error in the picture attached (my driver is compatible with OpenGL 3.1 btw)  :banghead: :banghead: :banghead: :banghead: :banghead:
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Bryan See on January 07, 2019, 12:53:54 pm
I want to ask the creator behind the Knossos launcher a question: Is it possible to download my development mod from Knossos itself on other machine?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on January 07, 2019, 01:38:29 pm
Upload it as a private mod and then sign into Knossos on the other computer.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: MP-Ryan on January 20, 2019, 09:10:30 pm
Just dropped in to say that I've just reinstalled FSO for the first time in about 2 years, so this is the first time I've used it, and to ngld and the other contributors all I have to say is:

Good.
Godamned.
Job.

What a breath of fresh air from the days of manual installation.  This thing is phenomenal, well done.
Title: Help With KNOSSOS Pls
Post by: AcePilot on January 21, 2019, 08:08:59 am
Hi folks

Forgive me for asking what is likely a silly question.

I saw Knossos which looks fantastic, installed it and started downloading content.  In the settings I specified my target directory (Data Path) for the mods to be some arbitrary folder where they could all be neatly stored.  Something like ..\Games\FreespaceOpen.    This is NOT my retail FS2 folder.

So, content downloaded ok but . . . 

How am I then supposed to use that content?

If I run fs2_open_3_8_0_SSE2 from my retail folder, I just get the standard game with the standard campaign.
There are no options within there to point it to or add the additional campaigns I have downloaded.

There is nothing I can see in Knossos that allows me to run a campaign

I have WXLauncher installed which I thought was the old way of doing things.  If I run that then in the MODS tab I can see extra campaigns that were downloaded with the FSOInstaller (NOT the content downloaded via Knossos).  There is no option in that MODS tab to specify an alternate folder where additional campaigns are stored (i.e. those from Knossos).


Hence I am thoroughly confused.

Simple questions then.

1)  What executable am I supposed to use to run Freespace 2 (with mods)?   I assume its  fs2_open_3_8_0_SSE2

2)  How or where do I tell that programme to point to content downloaded by Knossos?

Thanks in advance





Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Mongoose on January 21, 2019, 11:53:35 am
If you've downloaded a mod in Knossos, you can run that mod through Knossos by simply selecting it on the Play tab.  To play the retail FS2 campaign, you'd probably want to use the MediaVPs mod (though you can even load the original retail data by selecting Retail FS2). You don't ever have to open the actual folder to launch FSO; everything is handled through Knossos, much as it is in a games launcher like Steam.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jg18 on January 21, 2019, 12:25:20 pm
If you've downloaded a mod in Knossos, you can run that mod through Knossos by simply selecting it on the Play tab.
The Play tab is currently called the Home tab. I’ve been meaning to suggest to ngld that it should be renamed Play (a much more intuitive and self-explanatory name IMO) with a new icon to match. “Play” would also lime up nicely with the verb theme established by Explore.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: AcePilot on January 21, 2019, 04:47:44 pm
Appreciate the replies all

However still making no sense

In my HOME tab in Knossos I see 2 entries which are FSO and FS2 Retail.    In the EXPLORE tab I have all the available mods of which 2 have been downloaded including Blue Planet.

In the HOME tab, clicking on FSO doesn't offer any PLAY options

In the HOME tab clicking on FS2 Retail DOES offer a PLAY option and if I take it FS2 runs but says I have no campaigns.   One of the options at that point is to go to the in game campaigns screen and in there, there is nothing, not even the main FS2 campaign.

That might be because I have now begun playing the original FS1 Port Mod using WXLauncher, don't know.

Regardless, how would I use KNOSSOS to play Blue Planet ?

It doesn't appear in that HOME TAB and in the EXPLORE tab is just has the basic options of Install, Details & Cancel








Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on January 21, 2019, 04:52:52 pm
Appreciate the replies all

However still making no sense

In my HOME tab in Knossos I see 2 entries which are FSO and FS2 Retail.    In the EXPLORE tab I have all the available mods of which 2 have been downloaded including Blue Planet.

In the HOME tab, clicking on FSO doesn't offer any PLAY options

In the HOME tab clicking on FS2 Retail DOES offer a PLAY option and if I take it FS2 runs but says I have no campaigns.   One of the options at that point is to go to the in game campaigns screen and in there, there is nothing, not even the main FS2 campaign.

That might be because I have now begun playing the original FS1 Port Mod using WXLauncher, don't know.

Regardless, how would I use KNOSSOS to play Blue Planet ?

It doesn't appear in that HOME TAB and in the EXPLORE tab is just has the basic options of Install, Details & Cancel

Install BP from the Explore tab, then it will show up in the home tab and you can click play!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on January 21, 2019, 10:23:04 pm
You did point Knossos to your retail FS2 folder during install so it could copy over the needed retail files, correct?  If not, any mod based on FreeSpace 2 will not run, if I understand correctly.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: AcePilot on January 22, 2019, 10:11:59 am
Hi all

Ok brief update.  What confused me with Knossos (as a 1st time user) was that I installed Blue Planet in the EXPLORE section and it hung at 86% for a long time yet at the same time said that it was complete.   As a result I thought it was installed but obviously it wasn't and thus hadn't gone across to the main HOME screen.   I have since re-installed successfully and all is well and can now play it.

Have to say Knossos is a brilliant piece of work which seamlessly installs what is needed for end users and looks extremely professional so kudos to the dev team on that one.

I agree with prev poster that the HOME page might be better called maybe LIBRARY or MyMods or LOADED MODS or something like that.


On a slight side issue, I note that I am getting some video issues with what I have.  Most particularly in the mission briefing screens where the grid lines are all constantly twitching/flashing like there's interference.  When I was running the FS Port using Wxlauncher I also had no ship targeting brackets which is an issue I see some others have had.  Not sure what the current status of that is though.  I'm running top resolution 1366 x 768 (16:9) but changing the res doesn't fix it.  This isn't the thread to report this but I mention in case its an issue so well known that someone might have an immediate answer.  Nevertheless the game is still very playable and Blue Planet looks really polished.

Cheers all



Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: GTV_Expanse on January 30, 2019, 05:28:30 pm
Just registered here so I can say thank you

Recently discovered freespace 2 mods so dug out my cd roms, installed the game

But was unable to get mods working. After hours of frustration I discovered Knossos.

Now I'm playing any mod I choose in glorious 4k on my 50" tv.

So thanks for all your hard work and to all modders who have brought  Freespace 2, a great game,

Into the modern era
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on February 01, 2019, 10:58:51 pm
Could this be an antivirus being overprotective?
By the way, what could you advise avast vs mcafee? What antivirus is most suitable for gaming laptop

Personally, I'd use Microsoft Windows Defender (built in), along with MalwareBytes' Anti-Malware.  Use uBlock Origin to block ads (many can be malicious, as well as the fake "Download" buttons that appear as "ads" when you try to get free software).

But of those two, I'd say Avast.  Perhaps the situation has changed, but from my previous dealings, Both Norton and McAfee overburden system resources, and can royally screw up a system when they're misbehaving.  Like I said, though, that may have changed.
Title: Re: PUBLIC BETA: Knossos 0.12.4 (combined launcher/installer)
Post by: wookieejedi on February 02, 2019, 11:05:15 am
Could this be an antivirus being overprotective?
By the way, what could you advise avast vs mcafee? What antivirus is most suitable for gaming laptop

I also use Window's Defender (used to use Avast), it has improved quite a bit from a few years ago and is not near as resource heavy as ones like Avast, etc.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Colt on February 07, 2019, 03:17:40 pm
So I've come to a bit of an obstacle. I tried to upload a campaign to Knossos but I get an error telling me the mod has no executable selected. I'm guessing this has to do with the FSO Build, but upon changing it from default to the version the mod uses (nightly version Jan 12th) it tells me...

"failed to save the selected FSO build.  Make sure you have at least one required package."

 I've dug around a bit but to no avail. Is the solution literally right in my face or did I make a big mistake?  :nervous:

Oh, also will I break my mod if I were to change the folder name? The ID is currently the ever-so elegent mod1, or is this unnecessary?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on February 07, 2019, 03:55:46 pm
Mod files go in packages and, as the error states, you have to create a package before you can add any dependencies, whether they be FSO or another mod.  See https://docs.google.com/document/d/1oHq1YRc1eXbCgW-NqqKo1-6N_myfZzoBdwZuP16XImA/edit?pli=1# for more details on packages.  In short, without packages, you can't actually have a mod.
The easiest way to rename your mod is in the Details tab.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on February 07, 2019, 04:10:19 pm
The link PIe posted is a general guide which explains the whole mod creation & upload process so you should read that in any case.
You can't actually change the mod ID once the mod has been created (and the folder name is generated based on that ID). You can rename your folder but that won't affect anyone else. Anyone who installs your mod later will get a folder named mod1-x.x.x and your mod's download link would be fsnebula.org/mod/mod1.
The easiest solution is to create a new mod and copy everything over. If you want to experiment, you can rename the folder and replace the mod ID in the mod.json file to match the new folder name. Since you haven't uploaded your mod yet and nothing depends on your mod, it should work.

By the way, what could you advise avast vs mcafee? What antivirus is most suitable for gaming laptop
I use NSIS to build the Knossos installer. Here's the latest release post (http://forums.winamp.com/showthread.php?t=454011). They list AVs which detect NSIS (and installers created through it) as malware even though they're perfectly fine. I'd say that's a pretty good reason to avoid them (both are on that list).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Colt on February 07, 2019, 04:43:19 pm
Mod files go in packages and, as the error states, you have to create a package before you can add any dependencies, whether they be FSO or another mod.  See https://docs.google.com/document/d/1oHq1YRc1eXbCgW-NqqKo1-6N_myfZzoBdwZuP16XImA/edit?pli=1# for more details on packages.  In short, without packages, you can't actually have a mod.
The easiest way to rename your mod is in the Details tab.
I failed to mention that I did make a package. The mod's dependency is only for MediaVP's, and I checked the pack as VP button too, though I couldn't find the file. Thank you for the guide, I'll give it a full read.
The link PIe posted is a general guide which explains the whole mod creation & upload process so you should read that in any case.
You can't actually change the mod ID once the mod has been created (and the folder name is generated based on that ID). You can rename your folder but that won't affect anyone else. Anyone who installs your mod later will get a folder named mod1-x.x.x and your mod's download link would be fsnebula.org/mod/mod1.
The easiest solution is to create a new mod and copy everything over. If you want to experiment, you can rename the folder and replace the mod ID in the mod.json file to match the new folder name. Since you haven't uploaded your mod yet and nothing depends on your mod, it should work.
Ah I see, thank you. My main concern was in case anyone wanted to open the file sometime down the line, and keeping it titled mod1 would've been ambiguous.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Colt on February 07, 2019, 07:02:39 pm
I've gone through the guide, but still getting the same problems as before. I made a copy of the mod, packaged it first and then gave it the FSO (version 3.8.1-20190112) and MediaVP's (newest) dependencies.

For the "Adding Files" part I clicked on the mod path, but there was no VP in the "package" folder or it's subset folders. I tried this both with and without ticking the "pack the contents as .VP" box.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on February 07, 2019, 08:53:48 pm
The .vp file is only generated during the upload process and as such you'll never see it on your computer (since you don't really need it yourself).

Make sure the status for your package is set to required. As the error mrssage states, you need to have at least one package in your mod which has its status set to "required". If that still doesn't help, put your mod folder (mod1-x.x.x) in an archive and PM that to me (or upload it somewhere and PM me the link).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Colt on February 07, 2019, 10:09:51 pm
Whoops. Yeah I left it on recommended instead of required.  Mod's uploaded to Knossos now. Thank you for the help guys!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Rogue Assassin04 on February 09, 2019, 08:07:31 am
Hello guys.

I used to play FreeSpace 2 on my desktop and due to the dedicated gfx card i had, there was no issues.
As i got my Laptop, I noticed that the launcher and the executable runs on the internal Intel Graphics. I wanted it to run on the Nvidia GFX which is available.

Is there any solution to where the launcher can open the FSO binary to run on the Nvidia Graphics?

Thank you.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on February 10, 2019, 07:15:31 pm
Open up nVidia Control Panel, find the performance area, add FreeSpace 2 Open, tell it to use the high performance graphics card.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on February 12, 2019, 10:25:34 am
@woutersmits: That's nothing Knossos can fix. Either use an adaptable HUD (like the one included with the latest MediaVPs) or encourage the SCP coders to fix the issue in the engine.
The targeting bug is a bug in FSO so there's nothing I can do about that. Find a coder with a 4k screen and tell him to fix that bug.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: woutersmits on February 12, 2019, 10:34:03 am
sorry wrong topic
knosses bugs somethin itsays not installed
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on February 12, 2019, 10:52:18 am
Can you give me the full error message? That would be much more helpful.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Rapsodius on February 14, 2019, 02:40:43 pm
Hey there! I'm back, got a nostalgia attack xd
I spent some time digging the wiki at first and installed FSO & mediavp the old way (tm), only to found this when I was looking for Blue Planet.

First of all: this launcher/manager is awesome!

After setting this thing up, I encountered some turbulence, so without further ado, my feedback:

Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on February 17, 2019, 01:44:20 pm
First of all: this launcher/manager is awesome!
Thanks! :)

After initial setup, my pilot files weren't copied, in case anyone has this problem, you need to copy/move them to "%appdata%\HardLightProductions\FreespaceOpen\data\players"
Yeah, wxLauncher is the only launcher that does this correctly right now. Since Knossos was designed for 3.8.0, I never took into account that someone might be coming to Knossos from an older FSO version.

Another thing I noticed is the launcher copies retail VPs to its own folder structure, after this, retail installation directory is no longer needed, maybe add a opt-in checkbox to delete the folder (better yet, use Freespace2 as the default Knossos data dir). Opt-in in case someone still wants to play retail via the original exe.
We're currently improving the first time setup. I might add a checkbox to delete the old folder and a notice that it's no longer needed. Knossos can't use the old Freespace2 folder itself since the retail files need to be in a subfolder to work and I don't want to break any existing retail installations.

About folder structure, I observed 'retail' FS2 on the launcher is just calling FSOpen executable with -mod FS2 cmdline, so the retail vps are used as a mod instead. However, other mods are subfolders of FS2, maybe you could make it in such a way that every mod has its own folder alongside FS2 folder. (probs adding ',FS2' to mod cmdline)
That might be possible... not sure. However, the main reason for the FS2 folder is Knossos' TC support. Each TC has its own folder inside the data folder containing the TC files and the mods for that TC. FS2 is treated as just another TC since that was the easiest way to implement TCs. If I moved the FS2 mods outside the FS2 folder, it wouldn't be clear whether those are TCs or mods.

Report button on mod detail screen just 'doesn't work' without a nebula account saved, opens a message box saying: "Request failed. Please contact ngld.", log says:
[...]
Probably it should state the reason it fails is this, or better yet report them without needing an account.
Yes, I'll fix that in the next release. Not sure if I'm going to drop the account requirement since I want to avoid spam (and without the account there's no way I could reply).

Which brings me to the reason of the report: MVP 3.8.2 seems like having a checksum mismatch, whenever I "Verify file integrity", packages MV_Music and MV_RadarIcons show as invalid, despite being redownloaded via Knossos.
That's a result of certain bug fixes on the server... I fixed the downloads but forgot about the checksums. Thanks for the reminder!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Rapsodius on February 27, 2019, 10:41:10 pm
We're currently improving the first time setup. I might add a checkbox to delete the old folder and a notice that it's no longer needed. Knossos can't use the old Freespace2 folder itself since the retail files need to be in a subfolder to work and I don't want to break any existing retail installations.

Yes, I'm aware of this limitation. My suggestion was more in the line of "recycle Freespace2 folder and put Knossos folder structure in it" (opt-in ofc)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: SL1 on February 28, 2019, 12:14:43 am
When trying to launch certain mods, I'm getting an error that says "I couldn't find an executable. Aborted." A lot of other mods work just fine, though, which is weird. Here are the mods that have given me this error so far:

The Deuterium Connection
Eyebleach
Operation Cloak and Dagger
Storm Front Saga
Walking on Ashes
Walls Closing

I'm not sure what might have caused this. It started after I installed Wings of Dawn 1+2, though. I didn't try to launch most of these mods before installing WoD, so I don't know if they were screwed up before, but I do know that I was able to launch Eyebleach and Operation Cloak and Dagger before.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Novachen on February 28, 2019, 03:49:30 am
Maybe you changed your Engine Stability to "Stable" instead to "Nightlies"?
 At least Deuterium and Storm Front are needing a Nightly 3.8.1 one.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: SL1 on February 28, 2019, 05:49:30 am
Just tried switching Preferred Engine Stability to "Nightlies". No effect.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: MitoPL on February 28, 2019, 06:47:47 am
You could try to update your "FSO" mod before you play these.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: SL1 on February 28, 2019, 02:14:28 pm
You could try to update your "FSO" mod before you play these.

I'm not seeing any way to do that. I tried clicking "Modify" on FSO, which brought up a menu for installing 3.8.1-20190205, but it looks like I already have that. Is that the newest version?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on March 01, 2019, 01:53:15 am
yes, that's the latest version
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on March 01, 2019, 03:41:07 am
"I couldn't find an executable. Aborted."
[...]
It started after I installed Wings of Dawn 1+2, though.
That might actually be related... WoD is the first mod to use a custom build on Knossos. If you uninstall the WoD builds (should show up as a tile on the Home tab), does that change anything? If Knossos doesn't let you uninstall them because they're necessary for WoD, you can just move the bin/fso-wod-17.x.x folder out of your Knossos data folder.

You could also verify the file integrity for FSO (both latest version as well as for 3.8.0-2 and 3.8.0-3).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: SL1 on March 01, 2019, 01:37:23 pm
I tried reinstalling the mods that were giving the error, and that seems to have fixed things. Someone with more technical knowledge might want to look into whether or not WoD's custom builds can cause issues, but whatever it was, reinstalling seems to work.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: neoterran on March 10, 2019, 05:48:10 pm
Knossos Windows installer (in fact all of FSNebula) is down atm. 504 Gateway Error. Any mirrors ?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on March 10, 2019, 06:14:07 pm
Nebula is back up. You can usually find all Knossos releases on GitHub (https://github.com/ngld/knossos/releases) as well though Knossos might fail to find mods (or install them) as long as Nebula is unavailable.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: [DW]-Hunter on March 16, 2019, 09:51:59 pm
I can't get it to work, it keeps asking for a GOG installer..... I installed it via Steam. I don't own a GOG copy. HELP
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on March 17, 2019, 10:44:37 am
That window should give you the choice to either select a GOG installer OR an existing game directory (<steam library>\steamapps\common\Freespace 2 in your case).

If FS2 is installed through Steam, Knossos should be able to autodetect it and tell you that it can use that directory. If that doesn't work, manually selecting it should work as well.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: gamerman on March 19, 2019, 10:41:04 am
Nice combined installation and launcher.   :nod:  I am one of the old gamer that has the retail game box and discs for both games.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: doabarrelroll on March 27, 2019, 09:33:00 pm
Hey everyone, I've been playing this game for years and this community has been the greatest thing to ever happen to it.

Last year I downloaded Knossos for the first time and followed instructions, I beat a few mods and was great fun-until my computer broke. Now I've been trying to return to the game a few months later on a different, slightly older Windows 7 laptop. The retail game works perfectly fine, but Knossos keeps crashing after 5-30 seconds of opening it. I've tried searching around for any clues of fixing it but to no avail (I could just be blind and confused) so I decided to reach out on here to see if any of you have ever heard of a similar problem happen before. I'm getting a new computer in a month, so I guess fixing it isn't a massive priority (unless the same happens with the new one) but now I'm just curious why Knossos is unable to stay running. I'm hoping it's a simple solution, and would appreciate any thoughts/ideas. I can't wait to play mods again!

Thanks in advance everyone :)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: chief1983 on March 27, 2019, 09:51:02 pm
I have a Windows 7 laptop that missed the free upgrade deadline, if I can find time I will try to reproduce it and see if that's the culprit.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: MitoPL on March 28, 2019, 02:45:34 am
If it's worth something, Knossos works just fine with Windows 7. Maybe the solution is super simple, the classical theme of restarting your computer, and if that doesn't work, reinstalling the program.
Also, maybe your antivirus is somehow angry at Knossos and decides it's a faulty or dangerous application?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: doabarrelroll on March 28, 2019, 09:55:40 am
Thank you for the quick replies!

Unfortunately I had wished it was going to be that simple as well, when I first installed it on the newer Windows 10 system months back Norton originally blocked it and I gave it the permissions etc and Knossos worked perfectly fine afterwards.

On here I've tried re-installing Knossos twice, resetting, and even turned my antivirus completely off just to see if that could have been the culprit but nothing's changed. That's why I'm so curious now to what's causing this, it's certainly something I can't think of.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on March 28, 2019, 11:31:52 am
Thank you for the quick replies!

Unfortunately I had wished it was going to be that simple as well, when I first installed it on the newer Windows 10 system months back Norton originally blocked it and I gave it the permissions etc and Knossos worked perfectly fine afterwards.

On here I've tried re-installing Knossos twice, resetting, and even turned my antivirus completely off just to see if that could have been the culprit but nothing's changed. That's why I'm so curious now to what's causing this, it's certainly something I can't think of.

Hmm strange. I run it on updated Windows 10 and it works. Do you have a joystick or some other controller plugged in? I side note, but I would recommend not using Norton, and simply using the Windows Defender. It's just as good, uses much less memory and isn't as picky or bloaty as Norton.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: neoterran on March 29, 2019, 12:42:27 pm
I also ran into antivirus issues. I also ran into issues that required me to use ccleaner to scrub the registry, because I had installed Freespace 2 from gog first and then tried to feed it the installer, which was a mistake and led to the save button failing to work and games appearing and disappearing. A nightmare.

It also wouldn't work on my Mac with Mojave at all, but that's not uncommon for Mac so I moved to windows 10 on bootcamp after realizing it wouldn't work in Parallels either.

So it's not super straightforward for everyone, even tho I had a clean Boot Camp Windows 10 setup for it and star citizen. Which is a shame, since it keeps people from playing.

However, I managed after a lot of effort and trial and error to get it working, so now I'm enjoying playing Inferno again. And now (in 2019) I actually have hardware that has 0 performance issues with it,

so it's really like a blast from the past. I first was playing Freespace 2 back in 2002-3 so it's nice to bring it all back. And also hear my voice acting in Shivans 13 years later. lol !

Even with the problems it has atm it is a big step forward in usability and design from the older installers so keep working on it.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: doabarrelroll on April 01, 2019, 03:15:44 am
Again thanks for the replies, it is still doing the same thing, and the answer is no to the external joystick/controllers. Like I said I've gotten it to work months ago before on another laptop, and nothing is out of the ordinary that I can see on here, I'm just at a loss right now. Everything works on my computer, just for some reason Knossos isn't happy with something I can't figure out and refuses to stay open for longer then 30 seconds. I have another Windows 7 PC I haven't touched in forever which I will try out tomorrow (although this is still puzzling me and I'd like to know) and I'll see if it's the same for there too.

Thanks again for the ideas so far everyone and more are welcome!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Yasuo on April 02, 2019, 06:26:18 pm
Hi, I've encountered several issues, perhaps this can help you to improve Knossos.

#1
Diaspora Shattered Armistice and The Aeos Affair "IMAGES" in the "DETAILS" section don't seem to load, it just displays the dots and the left/right arrow, but the images stay black.

#2
If your internet is disconnected while downloading a mod, an error message is shown but the mod will be listed as installed although it certainly was not finished. Even after restart, Knossos still displays it as if it had been downloaded successfully.

#3
Clicking Install on "Uncharted Territory" resulted in this error message: "A critical error occurred! Knossos might not work correctly until you restart it."
I immediately looked in ~/.config/knossos/log.txt with Knossos still running but there was nothing apart from the startup lines - the file had not been written since starting Knossos (do I have to close the error message so the log is being written to?). After restarting Knossos, I tried installing it again, but got the same message. I could install other mods, so there seems to be an issue with "Uncharted Territory". On the third try, I managed to get a log:

Code: [Select]
INFO:MainThread:launcher.main: Running Knossos 0.13.3 on PyQt5 and Python 3.6.7 (default, Oct 22 2018, 11:32:17)
[GCC 8.2.0].
INFO:MainThread:launcher.main: OpenSSL version: OpenSSL 1.1.1  11 Sep 2018
WARNING:MainThread:integration.init: Failed to specify Unity version. Most likely Unity is not available.
INFO:MainThread:integration.init: Activating Unity integration...
WARNING:Thread-4:repo.add_mod: Mod <Mod "Wings of Dawn Builds" 17.0.1 (fso-wod)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180302 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180419 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20171029 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180924 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180921 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180929 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190306 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190309 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190313 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190322 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190323 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190324 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190329 (FSO)> is empty, ignoring it!
WARNING:Thread-4:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190402 (FSO)> is empty, ignoring it!
WARNING:Thread-12:repo.query: Repo.query(): Expected Spec but got Version instead! (Version('3.8.0-3', partial=True))
WARNING:Thread-12:repo.query: Repo.query(): Expected Spec but got Version instead! (Version('3.7.2', partial=True))
INFO:Thread-1:tasks.work1: File "fs2_open_3_8_0_x64.AppImage" is left over.
INFO:Thread-1:tasks.work1: File "fs2_open_3_8_0_x64-FASTDBG.AppImage" is left over.
INFO:Thread-10:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/de/fb/652c67d50c5ea0a871f4ac1422d6c073813848479b08464ac38d0e7de269.png"...
INFO:Thread-10:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/10/9d/5bbbaea5f8fb6da7601e0b1622fa2eb0375357321ecd54e60496d56c7692.png"...
INFO:Thread-9:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/72/a5/316d08a743a35dc144284b9fb9a466ee259e0b22756cd2a032986951527e.png"...
INFO:Thread-9:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/a7/ef/48f47a06031b010b7acf9ca2d5dececb7af9177ee72f7ba5a7a0288f205a.png"...
INFO:Thread-3:util.download: Downloading "https://fsnebula.org/storage/2b/9a/7617fd8dd91d4d8ca859586faab8c594bcab0136458e4d5136b3590cc52b"...
INFO:Thread-9:util.download: Downloading "https://cf.fsnebula.org/storage/3a/49/693b3bb8f9c4337871f217de44ce2c8582f8b4a7f371c787af63ee60a820"...
INFO:Thread-4:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/75/04/92c49e1e228c093f2ac4aa6cea6f0caf010a83f548415f33dc3e5a687802"...
INFO:Thread-8:util.download: Downloading "https://fsnebula.org/storage/47/35/00db5982a595315870d97251b815fc3b3ed200a346d16a77880ed2c5bf02"...
INFO:Thread-6:util.download: Downloading "https://cf.fsnebula.org/storage/78/7c/cdf1e449ac4b1cfc7b9c849aa8b8938fecfd1e69beee54c61c1bef038bd8"...
INFO:Thread-10:util.download: Downloading "https://cf.fsnebula.org/storage/7e/5a/345b8145e6598d2e53a9e838706db0dc645d4d0ecf1312a73d142cf6d8d0"...
INFO:Thread-5:util.download: Downloading "https://fsnebula.org/storage/45/41/8e0cf2c98ab621bd931ead1755da73ed545574bd6dff6cf3f79a9538906c"...
INFO:Thread-2:util.download: Downloading "https://cf.fsnebula.org/storage/32/7a/23e37b8e4614c9d96d12b1cd47608a5f8c94f0cf768851e9d0966b7bbfb8"...
INFO:Thread-1:util.download: Downloading "https://cf.fsnebula.org/storage/24/5d/8ffd571bd7453769cc55482fb3eb72602086c2da3668aa3b5579440b5ad5"...
INFO:Thread-7:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/28/ac/236ff8d2ed0ecb86ff1879e4cc76de469326464973f915d5c4b2942b74ea"...
WARNING:Thread-13:repo.query: Repo.query(): Expected Spec but got Version instead! (Version('3.8.1-20171118', partial=True))
INFO:Thread-7:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/8b/13/9c77cf24c757f91aca01e19cade8ca6f64d0f2309a333650adfc2ec10308.png"...
INFO:Thread-4:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png"...
INFO:Thread-1:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/07/74/28c36f904bd981711fe99b91fa6f3a698e4785545f16a8d03a5fdadcdd8a.png"...
INFO:Thread-1:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/11/0c/5c000e879c9726baf993f530e8a03196509e9b19d3bdf53a754056c0874a.jpg"...
INFO:Thread-7:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/38/9e/389b1fbf74a148923e7cecfc444aa9212a0bc00552e96ee81744a510541e.png"...
INFO:Thread-4:util.download: Downloading "https://fsnebula.org/storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png"...
INFO:Thread-7:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/3a/3d/f022c8f53cb3a15ab8bdeb33abfff71d085b9589bf011abffc52e759592e"...
INFO:Thread-2:util.download: Downloading "https://cf.fsnebula.org/storage/d8/75/197cee70110437ee6fe6dd64677b5345344c94fd94f2dd2b42a10b15278d"...
INFO:Thread-4:util.download: Downloading "https://fsnebula.org/storage/c9/ae/be5071ec5866c660d4bb10805e10813c66dee36acd5654922e77c91c4ca1"...
INFO:Thread-10:util.download: Downloading "http://scp.indiegames.us/builds/nightly/20171118_dfdfd59/nightly_20171118_dfdfd59-builds-Linux.tar.gz"...
INFO:Thread-9:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/97/94/2d9d83fdcce58a904ab1d04196183e3ef67faf1e93d54dc4b01aa0e2ae55"...
INFO:Thread-5:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/ee/41/b4b6ee4509b451e7716b884da1a43286334dc54c628fb8a54b967317f3f4"...
INFO:Thread-6:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/5a/05/958363e6a4cc7d943c1a89170f8d00a9967d013f6c325c799ff4bd1ad788"...
INFO:Thread-1:util.download: Downloading "https://fsnebula.org/storage/13/b4/228c58bd350f3ab9c4a836fb3382d488f2b5f193d1aa6dee560f77be2783"...
INFO:Thread-3:util.download: Downloading "https://cf.fsnebula.org/storage/7b/34/e962a5dfdfafc16904f245a38f6460cb36061f544ca77ac3b138794465bb"...
INFO:Thread-8:util.download: Downloading "https://fsnebula.org/storage/c8/e1/69664cb515d4a8c02dfafde987cc931e1d55e57ff1f6022558e117323fda"...
WARNING:Thread-8:repo.add_mod: Mod <Mod "Wings of Dawn Builds" 17.0.1 (fso-wod)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180302 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180419 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20171029 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180924 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180921 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180929 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190306 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190309 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190313 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190322 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190323 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190324 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190329 (FSO)> is empty, ignoring it!
WARNING:Thread-8:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190402 (FSO)> is empty, ignoring it!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "/usr/share/knossos/knossos/web.py", line 284, in install
    windows.ModInstallWindow(mod, pkgs)
  File "/usr/share/knossos/knossos/windows.py", line 567, in __init__
    self.show_packages()
  File "/usr/share/knossos/knossos/windows.py", line 585, in show_packages
    all_pkgs = center.mods.process_pkg_selection(pkgs)
  File "/usr/share/knossos/knossos/repo.py", line 336, in process_pkg_selection
    deps = pkg.resolve_deps()
  File "/usr/share/knossos/knossos/repo.py", line 738, in resolve_deps
    version = util.Spec(version)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 449, in __init__
    subspecs = [self.parse(spec) for spec in specs_strings]
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 449, in <listcomp>
    subspecs = [self.parse(spec) for spec in specs_strings]
  File "/usr/share/knossos/knossos/util.py", line 886, in parse
    res.append(semantic_version.SpecItem(spec_text))
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 393, in __init__
    kind, spec = self.parse(requirement_string)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 408, in parse
    raise ValueError("Invalid requirement specification: %r" % requirement_string)
ValueError: Invalid requirement specification: '==~3.7.2-'
I haven't installed Wings of Dawn - is this a dependency for "Uncharted Territory" or is there another error?

Btw: I had to read till page 15 to find where Knossos has been installed to, so I propose to add a "Open Knossos log directory" button to the error dialog (like the Open Debug log functionality for the mods) to open ~/.config/knossos/ or the respective folder on win/mac.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on April 04, 2019, 05:31:12 pm
@Anyone who missed the Windows 10 free upgrade deadline:


It still works (https://www.zdnet.com/article/heres-how-you-can-still-get-a-free-windows-10-upgrade/).  Just click to download the "Create Windows 10 Installation Media" (https://www.microsoft.com/software-download/windows10) Tool on the Microsoft site, and then click "Upgrade this PC now".  That's it.  Don't forget to run O&O Shutup10 or W10Privacy (https://alternativeto.net/software/shutup10/) afterwards if you're worried about MS data collection.  As for disabling forced updates, look into editing Group Policy via the Registry (https://support.microsoft.com/en-us/help/328010/how-to-configure-automatic-updates-by-using-group-policy-or-registry-s); that should work just fine (assuming you can't get to it via the policy editor because you're on Home edition or something).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Spoon on April 05, 2019, 06:00:49 am
Not entirely sure why this is directly relevant to Knossos, but can confirm it still works.
'''Upgraded''' my laptop from 7 to 10 yesterday after reading this post without any issue.

Still happy with 7, pretty sad I'm going to be forced to switch to 10 but atleast it won't cost me any money. (But I'm still going to ride out 7 for a bit longer on my desktop)
So thanks for the heads up, jr2.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on April 05, 2019, 08:48:17 am
:yes:  Would recommend doing an upgrade then dropping back down to 7 just so the hardware is registered with a Win 10 license in case MS changes their mind.  To avoid too much hassle, you could shrink the system partition down a bit in Disk Management (run diskmgmt.msc), make a new partition, dual-boot another copy of 7, upgrade that to 10, then nuke that partition and re-extend the system partition. 

Sounds like a pain, but much easier than upgrading over your primary OS then reinstalling 7 :ick:

Then again, if MS hasn't closed the upgrade yet, they may never.  However, with Win 7 support ending, I'm thinking some bean counter will see a profit opportunity, hence my suggestion.

EDIT: Any mods, feel free to split this out if you think it's prudent.  :nervous:
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Autohummer on April 07, 2019, 02:46:15 pm
Is there any way to use both a HOTAS and foot pedals like I could with the old style setup? The current Knossos only recognises one controller. Dropping x360ce in the directory with the Knossos.exe file doesn't seem to work either. Sorry if it has been asked and answered before.

EDIT: Knossos did recognise the x360ce controller but the FS2/WoD it opens don't.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: TheBigCore on April 07, 2019, 03:20:15 pm
Are there any screenshots of the newest versions of Knossos?  The original post only has images of Knossos 0.7.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Yasuo on April 08, 2019, 03:23:42 am
Are there any screenshots of the newest versions of Knossos?  The original post only has images of Knossos 0.7.
Apart from the version number, the optional title bar and the added Troubleshooting menu point, it looks exactly alike.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Paraquat on April 12, 2019, 04:32:55 pm
Hello!
I have a problem with Knossos file association. I downloaded it, made sure ~5 times during multiple reinstalls that I check to associate FSO:// links to Knossos but still, I keep getting this error after I try to download Media_VPS through it. The program itself seems to work properly. Any help would be appreciated. Cheers, and thumbs up for all this awesome work!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: woutersmits on April 15, 2019, 03:41:28 am
how to fix this error
im useing linux mint
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on April 15, 2019, 04:17:49 am
You can edit this file: /usr/bin/knossos

To look like this:

Code: [Select]
#!/bin/bash
exec python3 /usr/share/knossos/knossos/__main__.py

You will need super-user privileges to edit the file, for instance run this command from a terminal window.

Code: [Select]
$ sudo gedit /usr/bin/knossos
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: woutersmits on April 15, 2019, 04:46:39 am
nowigetthis
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on April 16, 2019, 03:23:16 am
Sorry, I haven't seen that error before. I just copied all the retail VPs over from an installation I had ages ago, possibly off the retail CD ISOs, but I can't remember for sure as it was too long ago.

How are you trying to install retail? Do you have the GoG installer? Or something else?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: woutersmits on April 16, 2019, 04:10:39 am
i did from gog
site installer
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Lukeskywalkie on April 22, 2019, 02:18:20 am
Not sure if this is the right place, but just wanted to say thank you for this huge revision to the way FS2 SCP is released and enjoyed.  I think I understand where a lot of people's reservations are coming from - especially those of us who've grown accustomed to handling every part of the install by hand.  It feels like a loss of control - where once I knew what every file was doing in its folder, and spent hours combining my preferred mods via .ini, now it's all going to just drop into place with a click?  Yuck!

Then I tried it.  It took a moment, because I hit the warning 'don't use an existing fs2 folder!' or whatever, and tried to do a complete reinstall from disk, but your program outsmarted me and installed in my SCP folder anyway.  Once I realized how it worked - creating a new directory and 'harvesting' needed files from the old one, I got all excited to try all the new campaigns and mods people have made since my last tour of duty (mid 2017).  I'm not spending 2/3rds of my freespace time sorting or extracting or testing settings or figuring which nightly will probably work...I'm just booting up knossos and actually playing the damned game.   I didn't want to like it, but I do, and I think it's essential to the long-term health of the SCP et all that this system succeeds. 

Thank you for all your hard work, and for dragging us into a new era of FS2...again.  I can't believe how long I've been playing because of you guys and gals (and NEVER GETTING BETTER AT IT sorry ignore that I'm fine), and now I think my future kid just might get a chance to do so as well.  That's wild.

Cheers.

Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: HLD_Prophecy on April 25, 2019, 07:13:28 pm
Hi all,

I have a pre-existing mod folder with mod.ini, not a .vp! Trying to plug it right in as a Knossos mod and can't remember how to do it right. Tried creating a new mod and dropping the 'data' folder contents in: it wouldn't launch, couldn't find the executable until I manually led it to my old FS2 directory, then launched as a blank mod.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: MitoPL on April 25, 2019, 07:28:15 pm
I think you need to create a mod.json that lets Knossos know of the most important mod data, like used packages and FSO requirements.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on April 25, 2019, 08:26:14 pm
There is an import ini option, have you checked out the manual?

https://docs.google.com/document/d/1oHq1YRc1eXbCgW-NqqKo1-6N_myfZzoBdwZuP16XImA/edit?pli=1#
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Nightmare on April 25, 2019, 08:39:06 pm
Is the manual included to the Knossos download? Elseway it could be put somewhere more prominent.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on April 25, 2019, 08:55:23 pm
Hmm not sure, though I know it is pinned on the Discord channel.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Nightmare on April 25, 2019, 08:57:46 pm
It's not in the OP or the first page; don't know how many look on Discord. It's part of the (very short) wiki entry about Knossos though.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: HLD_Prophecy on April 26, 2019, 12:56:55 pm
I've tried importing the mod.ini, I get the screen 'you can't edit this mod since it doesn't have any packages yet'.

EDIT: Sorry for asking to be baby-stepped through this, I've lieterally done this exact thing before and I can't remember a thing about how it works, plus I'm doing this in short spurts between work/school and I can't think beyond the moment...  :rolleyes:
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on April 26, 2019, 04:14:14 pm
No worries! I would recommend making an entirely new mod following the instructions in the guide, that way you can see every step and what each step does. If you do get that error message again, simply just go to the Dev tab, click your mod, click modify, and then click add package. Hope that helps!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: HLD_Prophecy on April 26, 2019, 04:34:24 pm
No worries! I would recommend making an entirely new mod following the instructions in the guide, that way you can see every step and what each step does. If you do get that error message again, simply just go to the Dev tab, click your mod, click modify, and then click add package. Hope that helps!

Thanks a bunch for the support!

So: Create new mod, then when do I add my old data folder in? When I use the Add Package feature? (to make it clear, all my missions/assets were already done, 'way back when' with wxLauncher. I'm porting to Knossos for touch-up, bugfixing and release)   :)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on April 26, 2019, 04:50:04 pm
Yeah, after you create a mod add a package, then manually put your mod files in that package. For example, I make a package called main then in that folder I manually make a data folder and sub folders like tables, missions etc, and put my content in those folders. There are screenshots on the guide too  :)
https://docs.google.com/document/d/1oHq1YRc1eXbCgW-NqqKo1-6N_myfZzoBdwZuP16XImA/edit?pli=1#
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: HLD_Prophecy on April 27, 2019, 11:14:08 am
Thanks, that worked great! Seems like the guide screenshots are a bit outdated as per the most recent Knossos version, but regardless I was able to get all my old work up and running!

Now to get things spun up for release...  :)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on April 27, 2019, 12:20:23 pm
Great, glad to hear you got it all working!
Title: Re: PUBLIC BETA: Knossos 0.14.0-rc.1 (combined launcher/installer)
Post by: ngld on May 03, 2019, 05:13:17 pm
Oh, look... I'm not dead! This release was long overdue...

A bunch of PRs from jg18 (https://github.com/ngld/knossos/pulls?q=is%3Apr+author%3Ajg18) have been merged which bring us the following improvements:

... I think that's everything. Huge thanks to jg18 for his work!

Other changes in this release are:
matter how big your mod is.
  This change hopefully resolves a lot of painful upload issues.

Since there were so many changes, I'm fairly certain that I've introduced new bugs and hope to find them during the RC phase. As such, this release won't show up in Knossos' auto-update and has to be installed manually. Just download and run this updater (https://github.com/ngld/knossos/releases/download/v0.14.0-rc.1/update-0.14.0-rc.1.exe). If you're on macOS, here's the DMG (https://github.com/ngld/knossos/releases/download/v0.14.0-rc.1/Knossos-0.14.0-rc.1.dmg).

Sorry, no Linux releases this time. I don't want people to automatically update into an RC and making a new package just for RCs is a pain. Building from source shouldn't be too hard though.... :X



Let me know if you find any bugs / crashes / etc.

@woutersmits: Make sure you're using the Freespace2 installer and not the GoG Galaxy installer.
@Lukeskywalkie: Thanks for the feedback! Always appreciated.
I like fiddling a lot with stuff myself so I've tried to give as much control as possible to the user while still automating everyhting the user doesn't care about.

I've added the mod creation guide to the OP... I feel like it's getting bigger with each release.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Cyborg17 on May 04, 2019, 07:50:38 pm
The Future Freespace pilots of the world salute you!  :yes:
Title: Re: PUBLIC BETA: Knossos 0.14.0-rc.1 (combined launcher/installer)
Post by: Nightmare on May 04, 2019, 08:32:56 pm
I've added the mod creation guide to the OP... I feel like it's getting bigger with each release.

And if people would start reading it now, you might have less questions to awnser. If. :D
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on May 05, 2019, 07:33:03 am
@Cygorg17: Thanks!  :lol:

@Nightmare: I probably should make a new thread which is going to only contain release announcements and an FAQ for stuff like this. That way release posts won't be drowned out by troubleshooting and bug reports.



Someone PM'd me about the tile images (the mod images on the Home and Explore tab) and proposed a bigger size and removing the title below the image.
(https://cdn.discordapp.com/attachments/572381636310859776/572382056982773770/size.jpg)
The top image is the current size and the bottom image is the size other launchers (like Uplay or Origin) use.

I personally like the size we have right now. If we make the tiles bigger, less mods will fit on the screen (even if we remove the title bar). Another issue is that all the existing images will have to be updated for the new size (or just upscale them but that's... meh).
That person offered to take care of updating the images but I'm not sure if the people who uploaded the mods in the first place would be okay with that.
I don't feel too strongly about the whole thing so I'd like to hear more opinions on this.



Since the last Knossos release I've been tracking download speeds since I was curious how well the servers are working for everyone (slow downloads are a pet peeve of mine):
Code: [Select]
                fsnebula.org    3.265 MiB/s
             cf.fsnebula.org    9.156 MiB/s
 porphyrion.feralhosting.com   11.064 MiB/s
Which is a very interesting result since fsnebula.org and cf.fsnebula.org are actually the same server, they're just routed differently (hurray for ISPs  :rolleyes:).

This has given me the motivation to finally implement a speed test and preferred mirror setting. Once you've set that, Knossos will always try to download from that server first (instead of a random one). If the download fails, it'll still fall back to the other servers. This approach hopefully gets you faster (and consistently faster) downloads without causing any new issues.

Here's an example from one mod install:
Code: [Select]
         server          speed  download time
   fsnebula.org    0.507 MiB/s  190 s
cf.fsnebula.org   11.871 MiB/s   10 s
   fsnebula.org    0.946 MiB/s  248 s
cf.fsnebula.org    4.029 MiB/s   34 s
Each line represents a single download. If that user would have downloaded everything over cf.fsnebula.org and not only half of the files, the whole mod install would have been faster by several minutes!



Finally, I wanted to mention another issue: The first launch after installation and after each update, Knossos is running as administrator. AFAIK the only issue this has caused is that some people chose a special folder as their library path which means that they always have to run Knossos as admin or it won't work since it can't write to the library folder without admin permissions.
The cause is that once an application has admin permissions in Windows, it can't drop them. Even new processes it launches inherit the permissions. The installer (and updater) run with admin permissions to make sure they can write to C:\Program Files. When they launch Knossos, it inherits those permissions and can't drop them (= run as normal user).
To the best of my knowledge, the only way around this is to modify the installer and updater to launch two processes: The first process runs as a normal user process and launches a second process with admin permissions. The first process remains hidden while the second process acts as usual. Once the installer finishes, the second process tells the first to launch Knossos which can then run without admin permissions since the first process never had those. IMO this is way too complicated for a fairly minor issue.


So, yeah that's all for now. Feel free to discuss the above topics while I'll get back to fixing Knossos bugs.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on May 05, 2019, 11:49:53 am
I definitely would not like the mod title removed, since that would force people who want their mod's name visible to put it in the tile image somewhere.  I also see no reason to resize the images since mods will take up more visual space and the images will take longer to download (when they're not cached).  I don't know of any real benefit so it would just be unnecessary work.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: mjn.mixael on May 05, 2019, 12:37:08 pm
I'm with PIe on the mod images and titles. What UI concern is solved by increasing the size and removing the title? Seems like forcing mod authors to change their images again requires actual benefit to the change.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Yasuo on May 05, 2019, 03:28:42 pm
Sounds like a great update! Looking forward to the linux version to check if my bugs have been fixed.

Btw:
Just noticed that the Knossos version of WingCommanderSaga is version 0.9.4, last updated 2018-07-18, but the download on wcsaga.com is version 1.0.2.7795, date added: 27/03/2012.
So, is the version on Knossos outdated, or is the version number incorrect?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: TheBigCore on May 05, 2019, 03:49:43 pm
Finally, I wanted to mention another issue: The first launch after installation and after each update, Knossos is running as administrator. AFAIK the only issue this has caused is that some people chose a special folder as their library path which means that they always have to run Knossos as admin or it won't work since it can't write to the library folder without admin permissions.
The cause is that once an application has admin permissions in Windows, it can't drop them. Even new processes it launches inherit the permissions. The installer (and updater) run with admin permissions to make sure they can write to C:\Program Files. When they launch Knossos, it inherits those permissions and can't drop them (= run as normal user).
To the best of my knowledge, the only way around this is to modify the installer and updater to launch two processes: The first process runs as a normal user process and launches a second process with admin permissions. The first process remains hidden while the second process acts as usual. Once the installer finishes, the second process tells the first to launch Knossos which can then run without admin permissions since the first process never had those. IMO this is way too complicated for a fairly minor issue.


So, yeah that's all for now. Feel free to discuss the above topics while I'll get back to fixing Knossos bugs.

So if you chose to install Knossos to somewhere else, not c:\Program Files, there'd still be the same issue?  Why not have the installer not be able to select c:\Program Files as the install directory?  Wouldn't that get around the problem?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on May 05, 2019, 04:02:53 pm
@Yasuo: WC Saga on Knossos is Admiral Nelson's port (https://www.hard-light.net/forums/index.php?topic=94378.msg1862095). The WC Saga devs forked FSO and used that to develop their TC. Due to this, the original TC is incompatible with FSO. Admiral Nelson ported the TC back to FSO which is the release you currently see on Knossos. I don't know how those version numbers relate to each other or if they have any relation at all. You'd have to ask Admiral Nelson about that. Either way, 0.9.4 is the latest version and the one you'll want if you want to launch WC Saga through Knossos.

So if you chose to install Knossos to somewhere else, not c:\Program Files, there'd still be the same issue?  Why not have the installer not be able to select c:\Program Files as the install directory?  Wouldn't that get around the problem?
The problem isn't where Knossos is installed. The problem is which folder you select as your library folder (i.e. where mods are installed). Excluding C:\Program Files would only solve part of the problem since there are many more folders which only admins can write to. Plus you can move the Program Files folder elsewhere which means that a check for C:\Program Files isn't as straightforward as you might expect.
Overall, it'd be better to just check if Knossos is able to write to the folder or not since that's all that matters. Since Knossos is running as admin after installation / update but not when launched through the start menu, desktop icon, etc. that's kinda hard to do. Not running Knossos as admin at all the best (and cleanest solution) but as I pointed out more complicated than it should be...

Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Yasuo on May 06, 2019, 07:45:22 am
Either way, 0.9.4 is the latest version and the one you'll want if you want to launch WC Saga through Knossos.
I see, thanks!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on May 06, 2019, 09:57:14 am
2 things:

1) As for mod image size, you could (if you felt like it) do both by having the original size expand to the larger size on mouseover (so you point at it and it expands to the bigger size, then shrinks back down when you move the cursor away).

2) As for admin privileges, is it not possible to have Knossos launch a second, non-privileged instance of itself and exit the privileged instance after initial install finishes, then do the folder write check?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on May 06, 2019, 10:48:18 am
1) Hm... that does solve the space issue but still leaves the issue about creating new images. Noone has commented yet on the fact that someone offered to update all the current mod tiles if we decided to go with the bigger size. Guess that's not really relevant if you don't want the bigger size in the first place.
I've also thought about making this an option so users can choose their preferred view (kinda like Discord's compact vs normal message view) but that'd require that either the tile images work well with both sizes or that mod authors submit two tile images for new mods but that's not really worth the additional effort.

2)
The cause is that once an application has admin permissions in Windows, it can't drop them.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Nightmare on May 06, 2019, 10:51:27 am
You could start a poll whether there's even a demand for bigger pictures. If only 2 or 3 people would use them anyway, it certainly wouldn't be worth the addontional work.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: mjn.mixael on May 06, 2019, 11:21:55 am
But what does that slightly larger size actually solve? What's the purpose? Is it just because someone asked for a bigger icon or did they have reasons?

Additionally making it an option to add about roughly 50 px to the width of an icon is just silly overcomplication. That's not compact vs expanded. That's just smaller and slightly less small.

I want to understand why we'd go through all this work? I'm honestly looking to hear the reasons, because I can't think of any myself.

EDIT: I'd add, having designed the UI, that many of the elements are designed around this particular size. Now sure.. all of that can be changed. I can go through all that work to adjust notification banners, the overlay, and all the CSS. But again.. why. And I already have the source files for a large amount of those icons. This person offering to redo everything does not make me more inclined to just agree to what seems like an arbitrary change.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on May 06, 2019, 11:44:15 am
Is it just because someone asked for a bigger icon or did they have reasons?
To be more like Uplay or Origin, I guess... which is not a good reason.

@Nightmare: I doubt a poll is really necessary since so far I haven't read a single post supporting the change and only posts against it (with good reasons).
Plus, I'm happy with the current size (and so seems everyone else involved with Knossos development).

Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: MitoPL on May 06, 2019, 02:56:28 pm
Not to mention that these launchers with these bigger tiles are used to launch full games, not merely mods. I think the tile size in Knossos handily show the difference :P
Also, I think we should mention that increasing the size of these tiles would make scrolling through Explore tab a bit more tedious... Look at how many mods are there already, if I expand the Knossos window to full screen, there are about 3 and a half full "pages" of stuff in there (1920x1080). I think bigger tiles would just be not useful.

However, if you really want to have some alternative to the current GUI, I think I've got a couple rather simple ideas:

1. The tiles are displayed without the title underneath. When hovering the cursor over a tile, the title shows up like the rest of the interface over the tile, above Play/Details buttons.
2. Same as 1. but when hovering the cursor over a tile, the mod title "slides out" downward (or upward if you think it'll be better) from underneath the tile to be displayed.
3. Just make a selectable alternative mod list display mode in Knossos - just a simple list! For example, a single line of the list:

[Mod title] --- [Play/Update/Install] - [Details] - [V] ---------------------- [Installed!/Update avail!]

[V] being the dropdown menu currently found in the normal tile view.
Play/Update/Install, Details and the dropdown menu buttons being hidden until you hover your cursor above the entry.
I think it's possible to reuse every piece of the GUI artwork here too.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: mjn.mixael on May 06, 2019, 04:06:10 pm
A compact view that's just a list is probably the best way to go. That would be a true expanded/compact UI option. Moving mod names really doesn't gain much. It take the height of 5-6 mod names to get another row on the screen at any window size. I'm not against adjusting how that works, but there isn't much gain from it.. if any.

(I'd also mention the CSS/HTML here that runs all the mouse-over stuff, the mod updating progress bar, the dropdown, etc.. are not exactly clean or easy to adjust. It can be done.. but I think there are better uses of our time in terms of Knossos features.)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on May 06, 2019, 06:37:27 pm
Hm... a simple list view like that might actually be useful (especially for smaller screens). I'd estimate that implementing would take ~30 minutes. You need to add an option somewhere to turn it on or off. If you just add a new setting, then you can just copy/paste the code for an existing setting and replace the names. The mod tiles are split into two templates: home tab (https://github.com/ngld/knossos/blob/develop/html/templates/kn-mod-home.vue) and explore tab (https://github.com/ngld/knossos/blob/develop/html/templates/kn-mod-explore.vue). You'd need to modify those templates which should be relatively simple: Remove the image for the compact layout and maybe change the order of the elements. Finally write a bit of CSS to display the mods in a list instead of grid and whatever other styling needs to be done.

If you actually want it to look good you'll probably need to invest more time but it's probably simpler than some of the bugs I'm currently trying to fix (joystick, no UI on macOS, some other weirdness that's been rep. (What the hell is wrong with the joystick code... why does it break itself on the second FSO launch with an invalid selected joystick?!  :banghead:)

Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: CP5670 on May 06, 2019, 06:55:03 pm
Is there a way to edit the images/description/files of a campaign on there? I've got a slightly nicer one for PI and it should be using a different media VP version (2014, and 2018 probably also works).

Knossos itself looks really nice and modern, and should make it much easier for newcomers to get started without messing around with VPs and so on. I know that complicated install processes turn off a lot of people. The existing UI and image sizes look good to me, and are similar to Origin or Uplay. The one suggestion I have is that there should be a way to manually override parts of an install, especially the dependencies that used to be in mod.ini (things like the media VP version).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on May 06, 2019, 07:30:59 pm
PIe uploaded PI. He can either do the change himself or give you access to modify the description, etc. yourself.

Being able to locally modify a mod would be nice but isn't as simple as I'd like it to be. I'll eventually (whenever I get the time to do it) implement it. I'll probably have Knossos convert it into a local dev mod. I might change the mod ID in the process to make it distinct from the "official" mod but I'm not exactly sure about that. You can already create and modify mods through the dev tab so the actual functionality is already there. The problem is that dev mods currently use a different folder structure from normal mods. The main reason for that is that Knossos needs to be able to tell which files belong to which package. This makes subfolders for packages necessary. Normal mod installs don't use subfolders to be closer to the traditional folder structure. However, I think that the latter isn't as important anymore and having the same folder structure for both devs and users would resolve a few issues (and make local modifications easier since I'd just need to change a single value in a JSON file for that).
Sorry... that was probably a bit too detailed.

Anyway, the trade-off with local modifications is that you either don't receive further updates for that mod or that your local modifcations will be overwritten with the next update.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on May 06, 2019, 07:59:00 pm
If you want dev access to PI, send me your Knossos username.  Otherwise just send me whatever you want changed.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: CP5670 on May 06, 2019, 08:53:48 pm
I made an account on Nebula with the same username (CP5670).

Quote
Anyway, the trade-off with local modifications is that you either don't receive further updates for that mod or that your local modifcations will be overwritten with the next update.

Yes, I can see how this could create a few issues. Most of the campaigns are not updated often though, so it shouldn't occur too frequently. I'll try doing this through a local dev mod for now.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on May 06, 2019, 09:18:55 pm
Access given.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on May 07, 2019, 11:41:08 am
2)
The cause is that once an application has admin permissions in Windows, it can't drop them.


Can something like this (https://www.tenforums.com/general-support/26958-switch-non-elevated-program-elevated-prompt-post432442.html#post432442) be done?  Again, it would involve invoking a second instance of Knossos, so that would have to be supported (first one could always exit after launching non-elevated version?)

Quote from: lx07;432442
You can also do it the other way around and start a program as your normal user from a elevated cmd prompt using the runas command.



If you use the /savecred parameter you'll only be asked for your password once.



For example with your forum name and notepad

Code: [Select]
C:\WINDOWS\system32>runas /user:cniggeler /savecred notepad


or to open a certain file with your program (for example C:\Windows\WindowsUpdate.log)

Code: [Select]
C:\WINDOWS\system32>runas /user:cniggeler /savecred "notepad \C:\Windows\WindowsUpdate.log"


EDIT2: Got it!! (well, pretty sure anyways) right  here:

SetTokenInformation
Change Token to Medium Integrity Level

https://weblogs.asp.net/kennykerr/Windows-Vista-for-Developers-_1320_-Part-4-_1320_-User-Account-Control
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: CP5670 on May 07, 2019, 10:11:31 pm
Access given.

Thanks. I'm trying to configure it and am having a few issues. I don't see the 2014 media VPs as a dependency you can select. It only has 3.6.12 and "newest" as the available options. Also, it's supposed to use an extra VP file only when the media VPs are installed, and not otherwise. Is there a way to configure it like this? If not I'll just make it require the media VPs and use the content in that file by default.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on May 07, 2019, 10:30:17 pm
This may not be the problem but you have to have any dependencies installed.
You could try adding the MVPs as a dependency only to the recommended/optional package but I don't know if this would do what you want (ngld would know).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: CP5670 on May 08, 2019, 04:40:07 pm
Maybe I'll try update it to make it compatible with the current media VPs. It seems the only change needed is to update a few models with the media VP versions.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on May 08, 2019, 05:35:37 pm
You can make an optional (or recommended) package which depends on the MediaVPs. Knossos would then only load them if that package was enabled / installed. There's no mechanism to only use certain dependencies, if they're already installed.
In case you haven't seen it, yet, here's a guide that should explain the whole mod creation process (https://docs.google.com/document/d/1oHq1YRc1eXbCgW-NqqKo1-6N_myfZzoBdwZuP16XImA/edit?pli=1#). Not sure how much help that's going to be since you seem to have already come quite far.

@jr2: Just wanted to acknowledge that I've seen your post. I haven't had time to test it yet, though. I'm not 100% sure whether it's going to work or not.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: woutersmits on May 10, 2019, 04:10:28 am
https://cdn.discordapp.com/attachments/503648818986876928/576334983514292224/unknown.png (https://cdn.discordapp.com/attachments/503648818986876928/576334983514292224/unknown.png)
i get ths error can someone fix that
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on May 10, 2019, 10:04:53 am
That's a dependency conflict. PI wants FSO 3.8.0-3 or later but the MediaVPs version PI depends on requires exactly 3.8.0-2.

@CP5670: Which MediaVPs version did you select and were you able to launch PI through Knossos after your changes?
@woutersmits: There have been a few changes to the MediaVPs' metadata. Can you please go to the troubleshooting tab and click "discard local changes to mod metadata"? That should make sure you have the latest metadata. If launching PI still fails afterwards, we need to fix PI's dependencies.

Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on May 10, 2019, 10:11:14 am
The 3.6.12 MVPs should require >=3.8.0.2.  PI works fine for me.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: PIe on May 11, 2019, 11:52:59 am
@CP5670, PI is currently broken because all the mod files are currently directly inside the package folder but they need to be in a data folder inside the package.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: CP5670 on May 12, 2019, 09:21:11 pm
I'll fix that shortly. I'm still working on a few things with this. I was going to make the campaign itself compatible with the 3.8 media VPs, which involves adding some new models and modifying a few missions to account for them.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: CP5670 on May 12, 2019, 11:28:34 pm
I put up a new sub-version of it. There are still a few issues I wanted to test before calling it an "official" version, but it should work now with the 3.8 VPs.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Knecht Ruprecht on June 03, 2019, 05:26:47 am
Hi there!

I have a problem regarding joystick selection. I use an XBOX gamepad with mouse-and-keyboard-emulation via GlovePIE, so I obviously want "no joystick". I set exactly that a few days ago when I started using Knossos in the Knossos FSO settings and it used to work fine - until today. I have NO idea what changed, but after finishing Sol:AH (there it worked), booting up Inferno (worked there too) for a quick glimpse and then booting up Blue Planet, something seems to have gone amiss.

Knossos settings still show "no joystick", but that is not the case anymore. No matter which mod I try now, joystick is active. When I try to map buttons in the ingame settings, the joystick buttons get mapped instead of what I want to emulate via GlovePIE. Ingame, both actions (joystick button and emulated keyboard key) are executed simultaniously.

I'd really like to continue using my GlovePIE script. Is there any way to "reset" Knossos' FSO settings bar from reinstalling everything? Can I reinstall Knossos without needing to redownload all the mods?

Edit: Deleting the settings.json for Knossos reset the settings, but didn't solve my issue. I am running out of ideas of where to look for the cause of problem.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on June 03, 2019, 07:37:27 am
Yes, I have reinstalled Knossos before, and you do not need to reinstall the mods. Are you running GlovePIE before you even open Knossos? Also does everything work as expected with just using the keyboard and mouse (ie unplugging and not using the joystick or GlovePIE)? Maybe unplug the joystick, ensure the mouse and keyboard works as normal, restart your machine, plug in the joystick and start GlovePIE, start Knossos, make sure no joystick is selected, then see if that might fix it?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Knecht Ruprecht on June 03, 2019, 10:12:39 am
Tried every combination of starting Knossos, starting GlovePIE and turning on the controller. Even double-checked GlovePIE output with Notepad. Rebooted my computer several times. Reinstalled Knossos (but kept the mods). Everything is working and showing as expected, EXCEPT that Freespace is using my controller as a joystick although "no joystick" is selected.  :sigh:
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on June 03, 2019, 12:24:04 pm
Hmm that's odd. You mentioned that the joystick is emulating keys, so could you try going to a specific key binding, clearing it, then binding it using the keyboard keyboard key instead of the joystick key? So for example, if you want the joystick trigger to emulate CTRL for the 'Fire Primary' control you would go to the control menu, clear the 'Fire Primary' control, then bind that key to CTRL using the keyboard, then in a mission try using the joystick trigger (which would be emulating CTRL) and see if it works that way?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Knecht Ruprecht on June 03, 2019, 12:54:27 pm
It does, but additionally it acts like the button itself. I have the A-button (joystick "button 1" as referred to by FS) mapped to tabulator via GlovePIE, in order to use it for afterburners. When I press the button ingame, it will 1) simulate tab and fire afterburners AND 2) register as "button 1" and fire my primary weapons.

I might need to erase all joystick-related entries from the default control config and see if that works. It just bothers me that it worked flawlessly only minutes (and a game start) before it ceased to do so.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on June 03, 2019, 08:48:55 pm
Yeah that is very odd. I actually made my own controls using a custom table (configcontrols.tbl) so it would never change on me, but I would say that's too complicated of a solution, especially if one isn't used to editing table files.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Knarfe1000 on June 06, 2019, 12:53:54 pm
Hello guys,

how and where can I install other builds than 3.8.0.3?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: MitoPL on June 06, 2019, 03:11:39 pm
In the upper right corner click a gear, and then select "Knossos" and then "Preferred engine stability" and set it to "Nightlies". Save it, then get back to your home page and update FSO.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Knarfe1000 on June 07, 2019, 04:03:36 am
Thanks. But how do I install elder builds like 3.7.2 ?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: MitoPL on June 07, 2019, 09:48:27 am
Knossos doesn't support builds earlier than 3.8.0. If it's about the issue you've posted in a different topic, maybe try a recent nightly build? If there's a bug in the new ones, we should try to fix it, not force people to go back to such old ones.

But of course you can, you just need to set up a separate FSO installation but use wxLauncher instead of Knossos.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Knarfe1000 on June 08, 2019, 04:52:32 am
Thank, but where and how do I install elder builds like 3.7.4 ?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: m!m on June 09, 2019, 06:35:44 am
Builds older than 3.8 are not supported by Knossos. You need to use wxLauncher for that but that launcher does not support the mod structure Knossos uses. Why do you need 3.7.4?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Knarfe1000 on June 09, 2019, 12:05:48 pm
Okay than. I wanted to test someting with elder builds.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Nightmare on June 09, 2019, 01:00:35 pm
Couldn't you just name the old builts exactly the same like the current builts and than smuggle them in?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on June 09, 2019, 01:32:32 pm
Couldn't you just name the old builts exactly the same like the current builts and than smuggle them in?

I think there is communication between FSO and the launcher and the protocols used are different (don't quote me; feel free to correct if this is not the case).

Although I wonder how hard it would be to make older builds use Knossos protocol for mods etc that have not been / maybe will never be updated by FSCRP.  Probably too hard to bother with I imagine.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on June 09, 2019, 01:45:10 pm
Any time to try this?  Found perhaps a couple more methods around it in case it comes in handy:
https://stackoverflow.com/a/10001420

Hidden Text: Show
Warning! While this approach was probably more or less OK for the original poster, it isn't really a good idea in general. In particular, note (as per the comment thread) that artificially manipulated tokens have been reported to cause problems in more complicated applications, so if you are using them, be sure to stick to the basic Win32 API. There are of course also potential security implications.

In most scenarios similar to those of the OP, it would probably be preferable to replace the shortcut that launches the elevated application with a launcher application. The launcher can then remain running for as long as the elevated application is running, and provide a natural limited token for the elevated application to use to launch non-elevated processes.

There's code for launching a low integrity process, which is analogous to your case, in the Designing Applications to Run at a Low Integrity Level (http://msdn.microsoft.com/en-us/library/bb625960.aspx) article in MSDN.

First, you duplicate the process token, since you can't (or at least shouldn't) mess about with a token that is already being used. Then you use SetTokenInformation (http://msdn.microsoft.com/en-us/library/windows/desktop/aa379591%28v=vs.85%29.aspx) with the TokenIntegrityLevel class to set the integrity level. There appears to be a bug in the example code, since the correct SID for low integrity level is S-1-16-4096 rather than S-1-16-1024, but you'll want medium integrity level anyway, which is S-1-16-8192. These can be found here (http://support.microsoft.com/kb/243330).

Once you have this working (that is, once you are able to launch medium integrity processes from your high integrity process) you should try using CreateRestrictedToken to create the new token instead of DuplicateToken, and remove the Administrators token and all privileges (except SeChangeNotifyPrivilege). Otherwise, the new processes will have medium integrity but still have administrator privilege, which could make it easier for any malicious code that might be running in the same session to elevate its privileges.

https://stackoverflow.com/a/9914500

Hidden Text: Show
I've used the approach described here to accomplish this. The basic idea is to ask Explorer to run Process B for you. Since Explorer typically runs at medium integrity level, this gives you what you want.

http://brandonlive.com/2008/04/26/getting-the-shell-to-run-an-application-for-you-part-1-why/

http://brandonlive.com/2008/04/27/getting-the-shell-to-run-an-application-for-you-part-2-how/

The first link will at least give you a good background.

We have a legacy application (Process A) that unfortunately has to run with elevated "admin" privileges (accomplished by setting its shortcut to always run as administrator).

A cleaner way to do that is set the requestedExecutionLevel (http://msdn.microsoft.com/en-us/library/bb756929.aspx) to the manifest.


2)
The cause is that once an application has admin permissions in Windows, it can't drop them.


Can something like this (https://www.tenforums.com/general-support/26958-switch-non-elevated-program-elevated-prompt-post432442.html#post432442) be done?  Again, it would involve invoking a second instance of Knossos, so that would have to be supported (first one could always exit after launching non-elevated version?)

Quote from: lx07;432442
You can also do it the other way around and start a program as your normal user from a elevated cmd prompt using the runas command.



If you use the /savecred parameter you'll only be asked for your password once.



For example with your forum name and notepad

Code: [Select]
C:\WINDOWS\system32>runas /user:cniggeler /savecred notepad


or to open a certain file with your program (for example C:\Windows\WindowsUpdate.log)

Code: [Select]
C:\WINDOWS\system32>runas /user:cniggeler /savecred "notepad \C:\Windows\WindowsUpdate.log"


EDIT2: Got it!! (well, pretty sure anyways) right  here:

SetTokenInformation
Change Token to Medium Integrity Level

https://weblogs.asp.net/kennykerr/Windows-Vista-for-Developers-_1320_-Part-4-_1320_-User-Account-Control

Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: wookieejedi on June 09, 2019, 02:35:02 pm
Reaming builds to be exactly the same is a pain if you are trying to bug find and again doesn't work after 3.8. The easiest solution is to just setup a wxLauncher folder for testing older builds. I say this from experience trying it both ways  :)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on June 09, 2019, 02:51:00 pm
I think there is communication between FSO and the launcher and the protocols used are different (don't quote me; feel free to correct if this is not the case).
Older FSO versions used to store settings, pilot files, etc. in the game directory while 3.8.0 and later store them in AppData. You can launch older builds with Knossos but all the fs2_open.ini settings made through Knossos wouldn't work since the build will be looking in the wrong place. You can still manually edit the fs2_open.ini, of course. There's another bug affecting macOS and possibly Windows in older builds that breaks the way Knossos handles the mod folder structure. Those builds change the current working directory (or root directory) to the same directory the exe file is in. Afterwards, it obviously won't be able to find any mods.

Adapting old builds to work with Knossos isn't too hard but I'm not exactly sure why you'd want that either.

@jr2: Sorry, not yet.

I'm currently stuck on an annoying bug on macOS. Whenever I launch the packaged version of Knossos, the HTML UI fails to initialize. It's somehow related to the way I package Qt with Knossos but I have no clue what the exact cause is. If anyone wants to help out (and has a macOS installation handy), feel free to speak up and I'll explain the build process for Knossos. If I can find no other solution, I might just remove Qt from the Knossos build which would mean that every macOS user would have to install Qt before using Knossos but at least that'd work.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on June 09, 2019, 11:01:20 pm
I have MacOS Mojave installed via Clover on this machine, which should work the same as normal MacOS as far as I'm aware.  What exactly do you need me to do?
EDIT: I have to work a 12 hour shift the next two days and a 6 hour after that, so if I take a while getting back to you that's why.  Should be able to poke at it for a bit during that time though.

EDIT2: Wait.  Do you mean help like coding help or help like try different patches and things out and report back help?  I'm useless for coding unfortunately :ick:  (I mean... slightly better than a monkey with a typewriter I imagine? :lol: ).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on June 14, 2019, 04:17:37 pm
Sorry for the late reply.

@jr2: Being able to code isn't necessary but I suppose it'll be hard to find the problem without understanding the code or being familiar with Qt on macOS.
Still, you can try the last macOS build and tell me if it works or launches with just a grey window: https://github.com/ngld/knossos/releases/download/v0.14.0-rc.1/Knossos-0.14.0-rc.1.dmg
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: rhraziel on June 18, 2019, 01:40:16 pm
Should the sorting option in Knossos work? When I try to sort the list by Last released or Last updated, nothing happens.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: MitoPL on June 18, 2019, 03:05:23 pm
Knossos 0.14.0, for this version these functions work just fine (for me).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: rhraziel on June 18, 2019, 03:20:30 pm
Knossos 0.14.0, for this version these functions work just fine (for me).

Awesome, that worked. I thought 0.13.3 was the latest version. Thanks.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Nightmare on June 18, 2019, 04:12:02 pm
Thread title needs some little update then~
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on June 18, 2019, 08:15:49 pm
0.14.0-RC.1 is technically the latest version but the download links at the top and the auto update function still install 0.13.3 since RC1 still has a few bugs I have to fix. Also, the macOS build is broken and I still have no idea why... :/

So, yeah. I'll fix at least the general bugs that I know about before I make it a "proper" release. RC1 was mostly meant as a solution for a pressing issue (huge mod uploads) and to discover new bugs. I knew that it added bugs (since the 0.13.3 release was so long ago) so I didn't want to force anyone (especially new people!) through that.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on June 18, 2019, 09:56:30 pm
Sorry for the late reply.

@jr2: Being able to code isn't necessary but I suppose it'll be hard to find the problem without understanding the code or being familiar with Qt on macOS.
Still, you can try the last macOS build and tell me if it works or launches with just a grey window: https://github.com/ngld/knossos/releases/download/v0.14.0-rc.1/Knossos-0.14.0-rc.1.dmg


It launches with a gray window.  Has "Knossos 0.14.0" logo in the top-left.  That's it.  It's not frozen or anything; I can move and resize it.  But.. Umm, MacOS has your window-controls at the top-left, the red x, yellow -, and green double-arrow buttons.  For whatever reason Knossos is showing up with Windows window controls at the top-right.  All 3 controls are fully functional; however, if you get a pure Mac user that might cause some consternation.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jg18 on June 29, 2019, 12:38:29 am
...and I reappear! :D

I have a MacBook Pro that I could use to help debug the macOS-specific issue. It's running High Sierra I think, but I can update it to Mojave or whatever the latest is if needed (I don't use it that often).

Also ngld, can you e-mail me with the list of release blockers for 0.14.0 and I'll see if I can squash any of them?

Currently juggling two major RL projects on top of work and the usual, but I'll take a look when I can.

EDIT: Slight correction.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: SirCumference on July 20, 2019, 04:09:36 pm
Hi all! Just installed Knossos on Kubuntu 19.04. While attempting the install I get a dependency error saying I was missing "python3-token-bucket". This package seems to be peculiar to Knossos, and isn't available in standard repositories. I was able to track down a copy on the Knossos launchpad.net page (https://launchpad.net/~ngld/+archive/ubuntu/knossos/+packages), but it wasn't obvious from the install instructions (https://fsnebula.org/knossos/) that that's what I was supposed to do. Is this the expected procedure or is something in the install not working right? Thanks!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Rico on August 14, 2019, 09:15:03 am
Hey,

Just tried to install this for the first time on my linux gaming desktop and receive the below error:

Code: [Select]
sudo apt-get install knossos
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 knossos : Depends: python3-token-bucket but it is not installable
E: Unable to correct problems, you have held broken packages.

I am running Ubuntu 19.04 and have added the PPA from the instructions here - https://fsnebula.org/knossos/

Can someone please direct me as to where I can get the missing "python3-token-bucket" package?

EDIT: I found the .deb file in the launchpad at https://launchpad.net/~ngld/+archive/ubuntu/knossos/+packages works perfectly as per SirCumference comment above. Thanks for the heads up!  :yes:


Unfortunately after installing Knossos it now gives an error that says "I don't know how to handle "\override_dh_link"! I only know fso:// ."
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on August 15, 2019, 03:15:42 am
You can 'workaround' that by making /usr/bin/knossos look like this:
Code: [Select]
$ cat /usr/bin/knossos
#!/bin/bash
exec python3 /usr/share/knossos/knossos/__main__.py
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: RecklessPrudence on September 02, 2019, 10:15:28 am
Dunno if this is fixed in 0.14.0 RC1, but in 0.13.3 either setting a download limit or reducing the number of active downloads only appears to do anything after all the downloads that were started already finish. I'm on Australian internet, so 512kb/s is literally half of my bandwidth on a GOOD day, and when I just started Knossos downloading something on a fresh install with 3 simultaeneous unlimited downloads it immediately chewed up almost all my bandwidth. I limited it to 512, then to 128, then reduced the number of actives from 3 to 2. It still kept the three active, with one going hammer and tong at ~700kb/s, and the other two using the rest of my bandwidth for ~100 on one and ~200 on the other. Only when the first was done did it register that I wanted it to only have two actives, and when there was one of the old unlimited downloads and one new limited to 128 download, the old one was sitting at around 900kb/s. Once it finished and the only downloads active were from after I put the limits on, then it started behaving. It's just that until the last of the original three finished, I had essentially 54k dial-up speeds back for everything else I wanted to do on the internet combined! Was an unpleasant reminder. And most webpages are a LOT bigger nowadays, so loading was taking even longer than they used to!

EDIT: Hm, interesting... Last night it was treating the download limit as a per-active-download thing, even once it opened new downloads - a limit of 128kb/s was the max for each download separately, after it started respecting that limit at all. After a restart, it's now treating it as a total-bandwidth-for-Knossos thing - a limit of 512kb/s and two active downloads sees one going at around 300kb/s and the other at around 200.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Durandal7 on September 10, 2019, 07:23:27 am
I don't know if this is the correct thread or if the FSO 19.0.0-RC1 one would be more appropriate. Some time ago, since I only have an Intel integrated graphic card and shadows hit my FPS really hard, I was suggested to add the "-no_glsl" flag to FSO. It still does the job, even if now I'm getting an "Unrecognized command line parameter" error. This flag, along with the -disable_glsl_model, should be in the Troubleshooting tab (source: https://wiki.hard-light.net/index.php/Command-Line_Reference#Troubleshooting), but I don't see them in Knossos.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: tcrayford on September 10, 2019, 08:52:19 am
Hi!

I can help test and debug the packaging of knossos and QT on OSX, I think. I use a mac for all my freespace stuff. I can definitely reproduce the issue with the 14.0 RC1 download you posted (the window shows up but it's just grey).

I don't have that much experience with QT, but am a generally experienced programmer and debugger.

I don't know what usage numbers are like for macs, but personally I'd like to help fix the issue if possible. Did anything change with the packaging of Knossos between the main 0.13.3 release and this RC?

Thanks

Tom
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: chief1983 on September 10, 2019, 10:04:04 am
I am eagerly anticipating improved Mac support, keep changing MacBook at work and just don't have the time I used to to help develop it myself, but do attempt to report testing results of each new release.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: m!m on September 10, 2019, 11:06:42 am
I don't know if this is the correct thread or if the FSO 19.0.0-RC1 one would be more appropriate. Some time ago, since I only have an Intel integrated graphic card and shadows hit my FPS really hard, I was suggested to add the "-no_glsl" flag to FSO. It still does the job, even if now I'm getting an "Unrecognized command line parameter" error. This flag, along with the -disable_glsl_model, should be in the Troubleshooting tab (source: https://wiki.hard-light.net/index.php/Command-Line_Reference#Troubleshooting), but I don't see them in Knossos.
"-no_glsl" along with "-disable_glsl_model" have been removed for a while now and do not have any effect anymore. You probably had these issues back when shadows were enabled by default which is no longer the case. Now they need to be enabled explicitly.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Durandal7 on September 10, 2019, 02:19:16 pm
"-no_glsl" along with "-disable_glsl_model" have been removed for a while now and do not have any effect anymore. You probably had these issues back when shadows were enabled by default which is no longer the case. Now they need to be enabled explicitly.
Thank you for the info! :D Indeed I removed the flags and the fps are the same... Seems like this time around the issues I was having were caused by vsync (which now is solved).
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Nightmare on September 11, 2019, 01:56:18 am
I don't know if this is the correct thread or if the FSO 19.0.0-RC1 one would be more appropriate. Some time ago, since I only have an Intel integrated graphic card and shadows hit my FPS really hard, I was suggested to add the "-no_glsl" flag to FSO. It still does the job, even if now I'm getting an "Unrecognized command line parameter" error. This flag, along with the -disable_glsl_model, should be in the Troubleshooting tab (source: https://wiki.hard-light.net/index.php/Command-Line_Reference#Troubleshooting), but I don't see them in Knossos.
"-no_glsl" along with "-disable_glsl_model" have been removed for a while now and do not have any effect anymore. You probably had these issues back when shadows were enabled by default which is no longer the case. Now they need to be enabled explicitly.

Could somebody with the required knowledge update the wiki page than?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Durandal7 on September 12, 2019, 12:51:10 pm
Here is an odd question for you guys: if I'm creating around half a dozen of sub-mods for another mod, should I group them all togheter into an unique mod called something along the lines of "fan tweaks", or should I create several separate mods and "spam" Knossos with 1 or 2 KB mods?

I'd rather like to use the first option, but I'm reading the documentation (https://docs.google.com/document/d/1oHq1YRc1eXbCgW-NqqKo1-6N_myfZzoBdwZuP16XImA/edit?pli=1#) and it's written that I have to create at least 1 "required" package... so I would have to make an empty .vp file, correct? (since all the actual sub-mods packages will be "optional")

Like, that empty .vp file will be "required" and have the parent mod as requirement.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on September 19, 2019, 12:24:34 pm
I'm getting a weird error when I try to install a couple different campaigns from Knossos 0.13.3 in Linux Mint.  "A critical error has occurred! Knossos might not work correctly until you restart it.  The error has been reported and will hopefully be fixed soon."

I haven't tried every possible campaign to install yet, but I keep getting it consistently with "The Mantle" and with the recently reuploaded "Friends and Foes" campaigns.  I posted this awhile back in Bomb3rman's release thread, but he isn't sure what could be the problem.

Are these issues actually getting reported to someone somewhere?  Is there anything I can do on my end to help diagnose?  I know Linux is probably not the preferred platform for Knossos or FSO, but for the most part I've been able to get both to work!  Just a couple befuddling exceptions, which is unfortunate because I really like both of these campaigns!  (An aside shout out: if you haven't played Friends and Foes or The Mantle yet, do yourself a favor and DO SO!  Solid, quality missions with good writing and characterization!  And they are fun to play!)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Diablokin551 on September 25, 2019, 05:34:51 pm
ok, so first time installing. "just hit run". ok, done and done, run the launcher, leave path the same, run game "executable not detected". da fuq? find this forum. realized i screwed up with the file destination and need to set it to the game. ok, no prop, easy fix "don't use preexisting FS2 directory, that won't work" ........  :mad:  :banghead:
 :o ok, calmed down enough to ask... how the hell do i make this thing work?

Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Cyborg17 on September 25, 2019, 08:54:00 pm
I believe that message just means that you have to point to somewhere new for knossos to do its thing.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Robsoie on September 26, 2019, 12:32:09 pm
Hello,

I'm very new to Knossos but today i decided to finally give it a try, i downloaded the 0.14 RC1
https://github.com/ngld/knossos/releases/tag/v0.14.0-rc.1

Wasn't expecting window 10 smartscreen to prevent me to install it, so instead of ignoring smartscreen i decided to try to just use 7zip to extract the Knossos installer instead of launching said installer.

In the extracted folder i double clicked on the Knossos.exe and Knossos launched without a single problem, no smart screen , nothing.
From there i could configure it again without problem.

So maybe a distribution of a simple archive instead of only an installer for window could solve the Smart Screen problem ?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: AstralStorm on September 27, 2019, 07:36:05 pm
Hello,

I'm very new to Knossos but today i decided to finally give it a try, i downloaded the 0.14 RC1
https://github.com/ngld/knossos/releases/tag/v0.14.0-rc.1

Wasn't expecting window 10 smartscreen to prevent me to install it, so instead of ignoring smartscreen i decided to try to just use 7zip to extract the Knossos installer instead of launching said installer.

In the extracted folder i double clicked on the Knossos.exe and Knossos launched without a single problem, no smart screen , nothing.
From there i could configure it again without problem.

So maybe a distribution of a simple archive instead of only an installer for window could solve the Smart Screen problem ?

Windows SmartScreen is extremely dumb protection, it looks for signatures on an executable file only. The author of Knossos has not cryptographically signed the archive. That's it.
You can bypass SmartScreen by clicking "More Info" and "Proceed Anyway".
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Soul Reaver on September 30, 2019, 06:10:34 pm
I'm not sure if this is a Knossos problem or something else, but...

I've installed MediaVPS, FSPort and FSPort Media VPS.  Ticked all boxes for all of them.

When I try to play FSPort Media VPS, my ship's ML-16s and Disruptors look like this:
https://i.imgur.com/lNrC7pR.png

I've tried checking file intergrity, uninstalling and redownloading everything... no luck.
Oddly, if I install Silent Threat: Reborn and change the campaign to Freespace, the lasers look more normal, but I'm not sure if doing that will mess up my FSPort campaigns in some way.

Any idea what's going on here?
Is this a problem with the files Knossos is grabbing or something else?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on September 30, 2019, 10:28:16 pm
Graphics drivers up to date?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Soul Reaver on October 02, 2019, 04:31:38 am
Graphics drivers up to date?

Yes.
I actually found what was causing it: turning on the post processing (post_process) flag makes them look that way.  That goes for Silent Threat: Reborn too - I didn't realize it the first time because I hadn't set the FSO Options for Silent Threat: Reborn up the same way when I went to try it.  But once I turned on post_processing for Silent Threat: Reborn it did the same thing.

It does the same on two different machines... maybe FSPort MediaVPS just don't like the post processing option?

I don't think it's a Knossos issue now.
Maybe I can make a bug report for FSPort Mediavps.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: maquise on October 02, 2019, 11:11:41 pm
From the beginning, I will say I'm fairly new at Freespace 2 in general.

I've installed the Diaspora: Shattered Armistice mod off of Knossos, and it will not start. Every time I try to start it, I get a "Application Error - The application was unable to start correctly (0xc000007b)" pop-up. I am running Knossos 0.13.3, and Diaspora 1.1.3 (only version currently available to me). I get the same popup if I try to run any of the Debug options. Strangely enough, opening the FSO Options also produces the debug, but the FSO panel does show up.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on October 03, 2019, 04:15:17 pm
Wondering if your antvirus interfered with the installation.  Or perhaps OpenAL wasn't installed.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: maquise on October 05, 2019, 07:29:59 pm
The Babylon Project seems to run fine, that's the only other one I've currently installed.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Deneb on October 10, 2019, 08:58:56 am
Trying to get FS2 and Open installed via Knossos. I downloaded the setup exe from GOG however when I select it in Knossos to install it gives me an error saying "The installer does not contain the retail files! Please make sure you selected the correct installer!"

Not sure what I can do differently as there is only the exe file to work with.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: mjn.mixael on October 10, 2019, 09:02:35 am
Did GOG change their installer?

A more round-a-about way you can do if you'r comfortable is to install FS2 using the GOG installer (make sure not to install into Program Files or other protected OS area.

After than you can run Knossos and simply point it to where GOG installed FS2. It should be able to setup from there.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Deneb on October 10, 2019, 09:13:34 am
Did GOG change their installer?

A more round-a-about way you can do if you'r comfortable is to install FS2 using the GOG installer (make sure not to install into Program Files or other protected OS area.

After than you can run Knossos and simply point it to where GOG installed FS2. It should be able to setup from there.
That seems to have done the trick, thank you. However there isn't a play button for FSO, is this normal? Will it just run the FSO upgraded version of the game if I click play on retail in Knossos?
(https://i.imgur.com/S4Ck4zN.png)

In case it matters, the exe file I downloaded from GOG had the following name "setup_freespace_2_1.20(32720).exe"
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Mongoose on October 10, 2019, 09:15:13 am
Yes, that's normal. To play FS2 with updated effects you need to download the MediaVPs mod and run that.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: mjn.mixael on October 10, 2019, 09:17:29 am
To add info; Knossos differentiates between builds and mods/games. You don't just run an FSO build. You choose a mod/game and Knossos will launch the appropriate build for it automatically.

Go to the Explore Tab to find and download from a huge list of ready-to-play mods. As Mongoose said, if you want to play FS2 with all the bells and whistles, find the MediaVPs mod and install that. Then play it.

Or just click here.

(https://fsnebula.org/static/kn_download.png) (https://fsnebula.org/mod/MVPS)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Deneb on October 10, 2019, 10:06:26 am
Brilliant, thanks for the excellent support guys  :yes:
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: mjn.mixael on October 10, 2019, 10:09:34 am
Glad to help. It's worth noting that Knossos' Settings has a option to hide FSO builds. (At least I think that's available in Knossos 13.3.. if not, it will be eventually.)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on October 14, 2019, 12:26:53 pm
:bump:
Bump.
 
I'm getting a weird error when I try to install a couple different campaigns from Knossos 0.13.3 in Linux Mint.  "A critical error has occurred! Knossos might not work correctly until you restart it.  The error has been reported and will hopefully be fixed soon."

I haven't tried every possible campaign to install yet, but I keep getting it consistently with "The Mantle" and with the recently reuploaded "Friends and Foes" campaigns.  I posted this awhile back in Bomb3rman's release thread, but he isn't sure what could be the problem.

Are these issues actually getting reported to someone somewhere?  Is there anything I can do on my end to help diagnose?  I know Linux is probably not the preferred platform for Knossos or FSO, but for the most part I've been able to get both to work!  Just a couple befuddling exceptions, which is unfortunate because I really like both of these campaigns!  (An aside shout out: if you haven't played Friends and Foes or The Mantle yet, do yourself a favor and DO SO!  Solid, quality missions with good writing and characterization!  And they are fun to play!)
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: ngld on October 14, 2019, 09:59:35 pm
Are these issues actually getting reported to someone somewhere?
Uh, yeah... about that...
(https://d.gruenprint.de/pZXwdEjixRUmoIOuydd7lTN74d8k6Sln.png)
Just sorting through that and figuring out which of those are user mistakes and which are genuine bugs takes a lot of time. And even then it can be hard to figure the root cause out.

Is there anything I can do on my end to help diagnose?
Can you send me your ~/.config/knossos/log.txt?

I know Linux is probably not the preferred platform for Knossos or FSO, [...]
Knossos actually was developed on Linux initially, later on I switched to Windows to fix a few bugs there that I couldn't reproduce on Linux.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on October 15, 2019, 10:16:19 pm
@ngld, Sorry.  I could definitely have worded that better.  I am very grateful for any help you have time to give! 

I would love to send you my ~/.config/knossos/log.txt  Unfortunately, I have no idea where it is.  I've been using Windows my whole life, and I only switched this PC over to Linux a few months ago.  I've tried searching my local drive for "Knossos" but the only hits I'm getting that are directories are inside my ~:/usr/share/knossos/ directories.  And all of those are *.PY files (because Knossos was written in Python?), no "log.txt" to be found.  I've tried hunting around to see if I can find it on my own, but I'm just not familiar enough with how Linux does these things yet.  My intuition for nosing around in a MS OS is not helping me here.

Does Linux Mint store configuration / log files in a different place than Ubuntu, maybe?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on October 16, 2019, 06:00:05 am
The ~ is a shortcut that means your home directory. 

If you're running Mint 19, you should be able to open that file by doing the following:

Open "Text Editor"
File -> Open
Press CTRL-H to see hidden files
Open .config/knossos/log.txt

Now; not that I want to disagree with ngld, but I can't actually find that file on my Mint 19 system :) For me it's at ~/.knossos/log.txt; but everything else is the same for finding it there instead.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on October 16, 2019, 10:13:31 pm
Thanks, niffiwan!  I did not know about CTRL-H to show hidden files.  It is going to take me awhile to get used to this.

I found the Log.txt file exactly where ngld said it would be.

Code: [Select]
INFO:MainThread:launcher.main: Running Knossos 0.13.3 on PyQt5 and Python 3.6.8 (default, Oct  7 2019, 12:59:55)
[GCC 8.3.0].
INFO:MainThread:launcher.main: OpenSSL version: OpenSSL 1.1.1  11 Sep 2018
WARNING:MainThread:integration.init: Failed to specify Unity version. Most likely Unity is not available.
INFO:MainThread:integration.init: No desktop integration active.
WARNING:Thread-10:repo.add_mod: Mod <Mod "Wings of Dawn Builds" 17.0.1 (fso-wod)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180302 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180419 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20171029 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180924 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180921 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180929 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190306 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190309 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190313 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190322 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190323 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190324 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190329 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190402 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190406 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190407 (FSO)> is empty, ignoring it!
WARNING:Thread-10:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190728 (FSO)> is empty, ignoring it!
ERROR:MainThread:manager.transform: 'Spec' object has no attribute 'specs'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/raven/utils/serializer/manager.py", line 76, in transform
    return repr(value)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 486, in __repr__
    return '<Spec: %r>' % (self.specs,)
AttributeError: 'Spec' object has no attribute 'specs'
ERROR:MainThread:manager.transform: 'Spec' object has no attribute 'specs'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/raven/utils/serializer/manager.py", line 76, in transform
    return repr(value)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 486, in __repr__
    return '<Spec: %r>' % (self.specs,)
AttributeError: 'Spec' object has no attribute 'specs'
ERROR:MainThread:manager.transform: 'SpecItem' object has no attribute 'kind'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/raven/utils/serializer/manager.py", line 76, in transform
    return repr(value)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 436, in __repr__
    return '<SpecItem: %s %r>' % (self.kind, self.spec)
AttributeError: 'SpecItem' object has no attribute 'kind'
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "/usr/share/knossos/knossos/web.py", line 284, in install
    windows.ModInstallWindow(mod, pkgs)
  File "/usr/share/knossos/knossos/windows.py", line 567, in __init__
    self.show_packages()
  File "/usr/share/knossos/knossos/windows.py", line 585, in show_packages
    all_pkgs = center.mods.process_pkg_selection(pkgs)
  File "/usr/share/knossos/knossos/repo.py", line 336, in process_pkg_selection
    deps = pkg.resolve_deps()
  File "/usr/share/knossos/knossos/repo.py", line 738, in resolve_deps
    version = util.Spec(version)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 449, in __init__
    subspecs = [self.parse(spec) for spec in specs_strings]
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 449, in <listcomp>
    subspecs = [self.parse(spec) for spec in specs_strings]
  File "/usr/share/knossos/knossos/util.py", line 886, in parse
    res.append(semantic_version.SpecItem(spec_text))
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 393, in __init__
    kind, spec = self.parse(requirement_string)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 408, in parse
    raise ValueError("Invalid requirement specification: %r" % requirement_string)
ValueError: Invalid requirement specification: '==~1.0.5-'
ERROR:MainThread:manager.transform: 'Spec' object has no attribute 'specs'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/raven/utils/serializer/manager.py", line 76, in transform
    return repr(value)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 486, in __repr__
    return '<Spec: %r>' % (self.specs,)
AttributeError: 'Spec' object has no attribute 'specs'
ERROR:MainThread:manager.transform: 'Spec' object has no attribute 'specs'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/raven/utils/serializer/manager.py", line 76, in transform
    return repr(value)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 486, in __repr__
    return '<Spec: %r>' % (self.specs,)
AttributeError: 'Spec' object has no attribute 'specs'
ERROR:MainThread:manager.transform: 'SpecItem' object has no attribute 'kind'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/raven/utils/serializer/manager.py", line 76, in transform
    return repr(value)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 436, in __repr__
    return '<SpecItem: %s %r>' % (self.kind, self.spec)
AttributeError: 'SpecItem' object has no attribute 'kind'
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "/usr/share/knossos/knossos/web.py", line 284, in install
    windows.ModInstallWindow(mod, pkgs)
  File "/usr/share/knossos/knossos/windows.py", line 567, in __init__
    self.show_packages()
  File "/usr/share/knossos/knossos/windows.py", line 585, in show_packages
    all_pkgs = center.mods.process_pkg_selection(pkgs)
  File "/usr/share/knossos/knossos/repo.py", line 336, in process_pkg_selection
    deps = pkg.resolve_deps()
  File "/usr/share/knossos/knossos/repo.py", line 738, in resolve_deps
    version = util.Spec(version)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 449, in __init__
    subspecs = [self.parse(spec) for spec in specs_strings]
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 449, in <listcomp>
    subspecs = [self.parse(spec) for spec in specs_strings]
  File "/usr/share/knossos/knossos/util.py", line 886, in parse
    res.append(semantic_version.SpecItem(spec_text))
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 393, in __init__
    kind, spec = self.parse(requirement_string)
  File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 408, in parse
    raise ValueError("Invalid requirement specification: %r" % requirement_string)
ValueError: Invalid requirement specification: '==~3.7.2-'
INFO:Thread-2:util.download: Downloading "https://fsnebula.org/storage/48/56/147210a6a8269175356ebb134a98baaad6f4f59eb2c90f6b814925a655fe"...
INFO:Thread-5:util.download: Downloading "https://fsnebula.org/storage/55/c5/e2b74a12e9ec1cfc648cce4462159ef07721fd3f64ac5836b6eb171c90f1"...
INFO:Thread-4:util.download: Downloading "https://cf.fsnebula.org/storage/42/85/9696f86b55e88ac19671c1107af59996877c91f1faac8e19b55a4cc4b7ed"...
INFO:Thread-10:util.download: Downloading "https://cf.fsnebula.org/storage/ef/4a/63d84b8cb382c10a5d3bca6eb61ff6aeae75d6735ba5fa18d1dac4cd08f1"...
WARNING:Thread-4:tasks.work2: Missing file "data/music/AlbumArtSmall.jpg" from archive "BTA_Music.7z" for package "BTA_Music" (Between The Ashes)!
ERROR:Thread-4:tasks.work2: Failed to unpack archive "BTA_Music.7z" for package "BTA_Music" (Between The Ashes)!
INFO:Thread-3:util.download: Downloading "https://fsnebula.org/storage/1b/d0/146cca8c8bd5e9259136369b4f66bea731cf176d9563d841174e83f9f214"...
WARNING:Thread-10:tasks.work2: Missing file "data/voice/briefing/bta1_d1_01_br01.ogg" from archive "BTA_Voice.7z" for package "BTA_Voice" (Between The Ashes)!
ERROR:Thread-10:tasks.work2: Failed to unpack archive "BTA_Voice.7z" for package "BTA_Voice" (Between The Ashes)!
INFO:Thread-7:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/a3/28/943ab1ef2127dba33e4efff2c7337b0a0f7850110b9640a798a0763be246"...
INFO:Thread-1:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/28/a4/9953490c958416045d861d7acbc411e0be1151db830f53e238da4e25f66a"...
WARNING:Thread-7:tasks.work2: Missing file "data/config/axmessage.cfg" from archive "BTA_Core.7z" for package "BTA_Core" (Between The Ashes)!
ERROR:Thread-7:tasks.work2: Failed to unpack archive "BTA_Core.7z" for package "BTA_Core" (Between The Ashes)!
INFO:Thread-8:util.download: Downloading "https://cf.fsnebula.org/storage/b7/2d/fb024389352d54e9e53b14ae6b69f1c609f26f4c66ca4ac88f558617725f"...
WARNING:Thread-2:tasks.work2: Missing file "data/cbanims/cb_default.ani" from archive "BTA_Root.7z" for package "BTA_Root" (Between The Ashes)!
ERROR:Thread-2:tasks.work2: Failed to unpack archive "BTA_Root.7z" for package "BTA_Root" (Between The Ashes)!
WARNING:Thread-1:tasks.work2: Missing file "data/maps/AlphCent_back6.dds" from archive "BTA_Advanced.7z" for package "BTA_Advanced" (Between The Ashes)!
ERROR:Thread-1:tasks.work2: Failed to unpack archive "BTA_Advanced.7z" for package "BTA_Advanced" (Between The Ashes)!
WARNING:Thread-8:tasks.work2: Missing file "data/movies/Collapse.mp4" from archive "BTA_Movies.7z" for package "BTA_Movies" (Between The Ashes)!
ERROR:Thread-8:tasks.work2: Failed to unpack archive "BTA_Movies.7z" for package "BTA_Movies" (Between The Ashes)!
WARNING:Thread-5:tasks.work2: Missing file "data/maps/afc_dvorak.dds" from archive "BTA_Maps.7z" for package "BTA_Maps" (Between The Ashes)!
ERROR:Thread-5:tasks.work2: Failed to unpack archive "BTA_Maps.7z" for package "BTA_Maps" (Between The Ashes)!
WARNING:Thread-3:tasks.work2: Missing file "data/cbanims/2_cb_aflogo.png" from archive "BTA_Anims1.7z" for package "BTA_Anims1" (Between The Ashes)!
ERROR:Thread-3:tasks.work2: Failed to unpack archive "BTA_Anims1.7z" for package "BTA_Anims1" (Between The Ashes)!
ERROR:MainThread:launcher.my_excepthook: UNCAUGHT EXCEPTION!
Traceback (most recent call last):
  File "/usr/share/knossos/knossos/tasks.py", line 385, in finish
    'Please run a file integrity check or reinstall (uninstall + install) it.' % title
TypeError: not all arguments converted during string formatting

During this run of Knossos, I first tried to install the Friends and Foes mod.  Got the error message previously described.  Then tried Mantle.  Ditto.  Then I tried to repair the install of Between the Ashes v 1.2.2.  That may be a completely unrelated issue entirely.  Not sure.  mjn.mixael is already looking into that on the following thread, I just figured I'd go ahead and try and capture what's going on in the same log.txt in case it would be helpful.  As far as I know, these are unrelated.

https://www.hard-light.net/forums/index.php?topic=92701.msg1888382#msg1888382 (https://www.hard-light.net/forums/index.php?topic=92701.msg1888382#msg1888382)

Thanks for the help so far.  Anything else I can do to help from my end?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: cloneof on October 23, 2019, 04:44:22 pm
Has anyone had any success with Debian with Knossos?

One would intuitively think that it would have a high compatibility out of the box, but I just kept looking at those repository command. If had a bad time with adding to the repository list when it doesn't say Debian compatibility out of the box.

Any comment from an experienced user would be appreciated. Would love to install The Babylon Project again, but I just don't have enough years under my belt to start another fight with the terminal : D.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on October 31, 2019, 10:26:31 pm
Can anyone tell me the best way to do a complete clean slate reinstall of Knossos onto a Linux Mint 19.2 system?  I'm convinced something has gone wrong with this installation.  I must have done something wrong.  I'm only able to download and install roughly half of the mods on the Explore tab.  The rest give me error messages.  Even mods I was previously able to download are not allowing me to anymore.

So, short of reformatting my hard drive and REALLY going full scorched earth, what is the best way to remove Knossos any any traces of settings it might leave behind so I can truly start over from scratch?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Vida_Aceptada on November 07, 2019, 09:10:15 pm
I've been trying to install the retail using the GoG installer, but it gives me an error.

I'm using Manjaro

Edit: It seems to have worked when I installed through Lutris.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Androgeos Exeunt on November 14, 2019, 11:03:35 am
I am getting the same error as Vida on Windows. Should I log a ticket on the GitHub repository or is it already logged?

I think the recent addition of Polish into the installer broke the process.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Izana Shinatose on November 19, 2019, 04:40:21 pm
For some reason Knossos can't launch FSO-19.0.0-RC1 at all, just get a brief FSO IS LAUNCHING... and that's it.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: Colt on November 19, 2019, 07:10:00 pm
For some reason Knossos can't launch FSO-19.0.0-RC1 at all, just get a brief FSO IS LAUNCHING... and that's it.
I believe this can occur if you do not have either RC's or Nightlies selected in your "Preferred Engine Stability" in the Knossos options.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on November 28, 2019, 01:04:11 am
Can anyone tell me the best way to do a complete clean slate reinstall of Knossos onto a Linux Mint 19.2 system?  I'm convinced something has gone wrong with this installation.  I must have done something wrong.  I'm only able to download and install roughly half of the mods on the Explore tab.  The rest give me error messages.  Even mods I was previously able to download are not allowing me to anymore.

So, short of reformatting my hard drive and REALLY going full scorched earth, what is the best way to remove Knossos any any traces of settings it might leave behind so I can truly start over from scratch?
So, I've been trying to figure this out for over a month now, and I'm no closer now than when I started.  For some reason I cannot figure out, I am getting the following error message whenever I try to install certain mods, "A critical error has occurred! Knossos might not work correctly until you restart it.  The error has been reported and will hopefully be fixed soon."

This is happening for Blue Planet, Friends and Foes, Shadow Genesis, Between the Ashes, Trimurti, The Mantle, Derelict, Bolitho Command and The Last Stand, Exile, JAD 2.21 and 2.22, Uncharted Territory, among others.  Can anyone help me figure out what on earth could be going on and how to make it stop?  Here is a copy of my .config/knossos/log.txt.

Seriously at my wit's end and need help.  I've done everything I can think of short of reformating the hard drive to give Knossos a fresh install.  Sudo apt-get purge knossos, followed by sudo apt autoremove to get rid of orphaned configuration files.  Wipe out the FreespaceOpen directory... none of it works.  I have to reinstall Knossos, sure, but it is still acting like it has all of the old settings.  First time I ran Knossos after I installed Linux, it ran me through an introduction wizard.  It isn't doing that now.  What's more, it seems like every campaign I successfully download and play is not something I can get to install next go around.

Any help would be greatly appreciated!
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on November 28, 2019, 01:55:47 am
I hear you, Knossos is pretty broken on my Mint 19 install as well, IIRC I can't use the explore tab and I can't update anything on the home tab. I suspect there's a bug somewhere in the code (hopefully client side; not server side otherwise I doubt there's anything I can do) but I haven't summoned up the motivation to investigate it yet.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: chief1983 on November 28, 2019, 09:49:33 am
If you are logged in and have any private mod access I suspect it's the same issue I have, I think it affects all platforms.  I can't view the Explore tab on Windows or macOS now.  Haven't really been able to use Knossos since that started happening.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on November 28, 2019, 10:09:25 am
I don’t have a login or any developer access. Sounds like this may be more complicated than I thought!  :(
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: jr2 on November 28, 2019, 12:20:29 pm
I don’t have a login or any developer access. Sounds like this may be more complicated than I thought!  :(

If you're looking to help out, I'm sure someone can get you access.  Not sure who, but good help is always appreciated.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: mjn.mixael on November 28, 2019, 12:59:00 pm
I'm logged in with dev access to mods and I can use it just fine.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on November 28, 2019, 01:07:21 pm
I’m not sure know enough to be of much help, but I can test things out if someone can tell me how. At this point, I’m even considering a reformat and reinstall of the OS. Just, you know, I’m pretty ignorant where all things code and Linux are concerned. My real job is all based on mechanical engineering design, so I live sleep and breathe AutoCAD and Excel, but my skill set is very... “specialized” let’s say.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on November 29, 2019, 12:50:53 am
Ok.  So, I bit the bullet and reinstalled my OS.  This time, I'm trying Ubuntu 18.04, just to see if that helps anything.  Got Knossos installed per the instructions at https://fsnebula.org/knossos/.  Had to remove the "override" bit of text per page 32 of this thread.  So far nothing different.  Knossos loads up and goes through the wizard!  Definitely better.  I direct it to my original FS2 files, it says it has managed to install everything successfully, invites me to log in, I pass because I haven't bothered to set one up yet.  I go to the explore tab, and maybe half of the mods show up with posters, and the other half are blank like the images are failing to load.  Then I realize I can't scroll up or down to look at more.  I think I'm probably just being impatient, wait a minute, and then Knossos "unexpectedly aborts."
Code: [Select]
python3: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.
Aborted (core dumped)
That's a new one for me.  Here's the log file.
Code: [Select]
INFO:MainThread:launcher.main: Running Knossos 0.13.3 on PyQt5 and Python 3.6.9 (default, Nov  7 2019, 10:44:02)
[GCC 8.3.0].
INFO:MainThread:launcher.main: OpenSSL version: OpenSSL 1.1.1  11 Sep 2018
WARNING:MainThread:integration.init: Failed to specify Unity version. Most likely Unity is not available.
INFO:MainThread:integration.init: Activating Unity integration...
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-1:repo.add_mod: Mod <Mod "Wings of Dawn Builds" 17.0.1 (fso-wod)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180302 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180419 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20171029 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180924 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180921 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180929 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190306 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190309 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190313 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190322 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190323 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190324 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190329 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190402 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190406 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190407 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20191104 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20190728 (FSO)> is empty, ignoring it!
INFO:Thread-10:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png"...
INFO:Thread-10:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png"...
INFO:Thread-10:util.download: Downloading "https://fsnebula.org/storage/f9/d5/f9a3866fa5e0c5b3a4d9721b49bca35f5597de21f3c466852f74e6bd72db"...
I tried opening Knossos again, and the same thing happened minus the new install wizard.  Tried to navigate to the Explore tab, the mods show up, but I can't scroll or actually do anything, and CTD follows.

Is there anything I can try on my end that would be helpful to anyone trying to diagnose this?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: tomimaki on December 01, 2019, 05:18:46 pm
Code: [Select]
python3: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.
Aborted (core dumped)
Try to install propertiary Nvidia drivers, nouveau (open drivers for Nvidia) is a bit... faulty (in this case). :nervous:
https://itsfoss.com/install-additional-drivers-ubuntu/
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on December 01, 2019, 07:21:47 pm
Drat.  That was dumb, I can't believe I missed that.  I already dumped the Ubuntu installation and switched back to Mint.  Mint prompts me to install those Nvidia drivers straightaway.

I dumped the partition, installed Mint, installed the drivers and relevant updates, then installed Knossos.  I'm more or less back where I started now.  Some of the mods work and some won't download.  I only went as far as installing different OSs because I had some spare time with the Thanksgiving holiday weekend.  That time is up now, so I think I'm probably committed to Mint 19.2 for the foreseeable future.  If I can't get Knossos to work, I'll have to try some other ideas.  Is it possible to play mods you download from Nebula the old fashioned way through Knossos?  Is there a text file I have to edit somewhere in the modern equivalent to a mod.ini file?  Or would I be better off trying to get wxLauncher to work for that sort of thing?
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: niffiwan on December 02, 2019, 04:01:21 am
Technically you can start FSO from a plain old bash script and forget about launchers completely. e.g. add the following to a script and make it executable (for mediavps 3.8.2 (and you can have a separate script for each mod you want to run, with the relevant lighting customisations, etc)

Code: [Select]
cd YOUR_FS2_INSTALL_DIR
PATH_TO_OLD_KNOSSOS/bin/FSO-19.0.0-RC1/linux/fs2_open_19_0_0_RC1_x64.AppImage -mod MVPS-3.8.2 -nomotiondebris -missile_lighting -3dshockwave -post_process -soft_particles -fxaa -dualscanlines -targetinfo -ship_choice_3d -weapon_choice_3d -3dwarp -warp_flash -nograb -fullscreen_window -no_unfocused_pause -fxaa_preset 9 -fov 0.5 -ambient_factor 125 -no_emissive_light -spec_point 0.6 -spec_static 0.2 -spec_tube 0.4 -bloom_intensity 25

But using wxLauncher is probably simpler, assuming it still compiles & runs.
Title: Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Post by: perihelion on December 09, 2019, 08:28:01 am
Yep! WxLauncher does work on Mint. I tried and failed building it a couple times, and then finally thought to look through the Synaptic Package Manager. Sure enough, found a copy there although the version seems a little off. 0.11.0+dfsg-1?? Through a bit of mixing and matching between stuff downloaded by the FreeSpaceOpenInstaller.jar, Knossos, downloading mods directly from Nebula, and the wxLauncher I found, I’ve been able to get at least two of the campaigns I couldn’t install before to work!

That should keep me going. I do hope whatever is going on with Knossos gets figured out. It is soooo much easier. Fortunately, I‘m  stubborn.  :p

Thanks for all the help!