[X3N0-Life-Form]

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 ?

[Knarfe1000]

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.

[ngld]

- 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 and here is the code to generate the launch buttons. 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 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.

[Smooticus]

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.

[ngld]

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.

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  ).

[krevett62]

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?

[Novachen]

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.

"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.

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 .