Wow guys. Just.. wow, that looks so awesome...QFT
Wow guys. Just.. wow, that looks so awesome...QFT
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.Well, this way Diaspora can be the guinea pig ;7
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 possibleIt 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.
Can the modder overwrite version numbers?The version number is specified by the modder, if that's what you're asking.
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
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.
I don't know how to handle "-psn_0_401506"! I only know fso:// .
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!
KN_DEBUG=1 /Applications/Knossos.app/Contents/MacOS/Knossos
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.
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.
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.
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.
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)
@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?
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.)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
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.
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
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 KnossosI am very sad to hear that cause it's one of my favourite campaigns in existence along with the other classics. :(
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'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.
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
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:
(P.s. I know I've said this before, but it cannot be overstated, Knossos is really nice, neat and cool)Thanks a lot! :)
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.
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.
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.
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).
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.
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.
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.
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 UsersNot suprising given that only some people on this forum have installed Knossos and I'm not sure how many of those even use Norton.
Fewer than 5 users in the Norton Community have used this file.
NewNot 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.
This file was released 10 days ago.
HighNot exactly sure why it thinks the file is risky.
This file risk is high.
File: d:\games\knossos\ knossos.exe RemovedWell, those are all harmless text files. Those aren't threats but they were created by Knossos.
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 ActionsKnossos doesn't actually use these registry keys. However, it uses SDL2 which uses DirectInput.
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
File Thumbprint - SHA:Now, if you take that hash and go to VirusTotal, you get this page: https://www.virustotal.com/#/file/6820d53c5b2b0360fc6740576026e6c433eb1c93babf690e9492a05337f879cf/detection
6820d53c5b2b0360fc6740576026e6c433eb1c93babf690e9492a05337f879 cf
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 UsersNot suprising given that only some people on this forum have installed Knossos and I'm not sure how many of those even use Norton.
Fewer than 5 users in the Norton Community have used this file.NewNot 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.
This file was released 10 days ago.HighNot exactly sure why it thinks the file is risky.
This file risk is high.File: d:\games\knossos\ knossos.exe RemovedWell, those are all harmless text files. Those aren't threats but they were created by Knossos.
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 RemovedRegistry ActionsKnossos doesn't actually use these registry keys. However, it uses SDL2 which uses DirectInput.
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 RepairedFile Thumbprint - SHA:Now, if you take that hash and go to VirusTotal, you get this page: https://www.virustotal.com/#/file/6820d53c5b2b0360fc6740576026e6c433eb1c93babf690e9492a05337f879cf/detection
6820d53c5b2b0360fc6740576026e6c433eb1c93babf690e9492a05337f879 cf
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.
Or people should stop using bloatware anti-virus like Norton....
...
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 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.
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.
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.
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.
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)
"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.
excactly my issue well hopefully this will be fixed in the next update. :mad: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)
Sometimes I get error: The application was unable to start correctly. 0xc000007b error when trying to run any game from Knossos.I had the same message until I reinstalled (or installed) the Open AI. May be that will be your problem too.
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
Sometimes I get error: The application was unable to start correctly. 0xc000007b error when trying to run any game from Knossos.I had the same message until I reinstalled (or installed) the Open AI. May be that will be your problem too.
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
Maybe another project for Bryan See or woutersmits? :lol:
Better not. They already have so much stuff to do...
Well, i know that. But somebody have to play Freespace very much to create a very good OpenAI profile :).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.
Let's get back to the original problem...Thank you that has appeared to fix the problem. funny detail though is sometimes it worked and sometimes it didn't
@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
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.
... 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?
Which Windows version are you using?
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?
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.
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.
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...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.
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.
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
The logs aren't uploaded automatically. The user has to click on "Upload debug log" to trigger that.
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?
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
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.
Interesting. Haven't seen that problem before. Which AV do you use?
4.description.String value is too long: ['releases']
Does 100000 sound reasonable?
Why can't we have internal video hosting of our own?
~ $ 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.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...
I still moderate this? :P
Can you run a Fast Debug build and upload the debug log?
Try to run a debug build again (once) and then upload your %appdata%\knossos\log.txt.
@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: ..." ?
[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]
Hm... do you have a log in C:\Games\FreespaceOpen\FS2\data\fs2_open.log ?
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.
@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: ..." ?
[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]
@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).
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.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.
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, 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.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.
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.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.
Either way, thanks for working on it.
You've done amazing work with knossos.Thanks!
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.Gotcha, I understand your thought process.
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.
@Spoon: Sorry, I was in a bad mood yesterday and the frustration got to me.No worries, I understand it can be frustrating when you keep hearing the same issue that you can't do anything about.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.
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.
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.
"<Mod "Trimurti" 1.1.0 (shv)>" requires "FSO" which is missing!
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.
@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.
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).
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).
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: ..." ?
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.
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.
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.
In this case installing Wing Commander IV Demo doesn't add Wing Commander Saga.
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
"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.
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.
@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.
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."
@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.
"dependencies": [
...
{
"version": null,
"id": "MVPS",
"packages": []
}
],
"dependencies": [
...
{
"version": "3.7.2",
"id": "MVPS",
"packages": []
}
],
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'
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'
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.
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.
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.
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!
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!
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.
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.
We have a search goddamnit! I somehow get the feeling that noone's using that.
Which Windows version are you on?
Could this be an antivirus being overprotective?
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.
@wesp5: Make sure that 7z.exe isn't still running.
Which Windows version are you on?
Win 8.1, using Knossos 0.12.4
and now something new :blah:, getting a little frustrated with Knossos..
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!
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!
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.
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?
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?
@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.
MediaVPs 3.8.x requires a nightly build. You can get one here.
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.
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.
Hmm. Don't know what I did or did not do, but everything works now. False alarm! Back to your regularly scheduled programming.
Why don't we streamline without compromising everything that made the Knossos launcher?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:
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.
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
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?
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!
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 logWhat of total-conversions?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!
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.
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.
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?
python3 /usr/share/knossos/knossos/__main__.py
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.
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.
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
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).
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
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.You're welcome. :)
Thankyou all.
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
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.
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. :(
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.
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.What about the mod development folders created by Knossos? Will they be transferred to another machine that contains the Knossos launcher?
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.
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.
- 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.
- In the launch FSO tab, the buttons go :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".
[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 ?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.
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).
"Your mod" requires "MediaVPs" which has conflicting requirements: ~3.8.2 (Your mod), ==3.6.10 (the base mod)
character limit of the descriptionWell, 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.
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?
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.
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.
CurrentJoystickGUID=NoneThis 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 showsThe 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.
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 showsThis 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.
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.
@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.
What happens if you trigger the bug and set CurrentJoystickGUID to an empty string (CurrentJoystickGUID=) before launching FSO again? Does that solve the problem?
What about cross-machine mod development?
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.
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
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.
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.
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.
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
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
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
By the way, what could you advise avast vs mcafee? What antivirus is most suitable for gaming laptopI 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).
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.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 easiest way to rename your mod is in the Details tab.
The link PIe posted is a general guide which explains the whole mod creation & upload process so you should read that in any case.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.
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.
ERROR:MainThread:web.nebReportMod: Failed to send mod report!
Traceback (most recent call last):
File "C:\knossos\knossos\web.py", line 1288, in nebReportMod
File "C:\knossos\knossos\nebula.py", line 225, in report_release
File "C:\knossos\knossos\nebula.py", line 33, in _call
knossos.nebula.InvalidLoginException
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: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).
[...]
Probably it should state the reason it fails is this, or better yet report them without needing an account.
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!
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.
You could try to update your "FSO" mod before you play these.
"I couldn't find an executable. Aborted."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.
[...]
It started after I installed Wings of Dawn 1+2, though.
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.
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?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.
#!/bin/bash
exec python3 /usr/share/knossos/knossos/__main__.py
$ sudo gedit /usr/bin/knossos
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!
I've added the mod creation guide to the OP... I feel like it's getting bigger with each release.
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:). 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.
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.
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!
The cause is that once an application has admin permissions in Windows, it can't drop them.
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.
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.
2)The cause is that once an application has admin permissions in Windows, it can't drop them.
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 notepadCode: [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"
Access given.
Couldn't you just name the old builts exactly the same like the current builts and than smuggle them in?
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;432442You 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 notepadCode: [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
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.
Knossos 0.14.0, for this version these functions work just fine (for me).
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
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.
$ cat /usr/bin/knossos
#!/bin/bash
exec python3 /usr/share/knossos/knossos/__main__.py
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.
"-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).
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.
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 ?
Graphics drivers up to date?
Did GOG change their installer?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?
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.
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!)
Are these issues actually getting reported to someone somewhere?Uh, yeah... about that...
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.
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
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.
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, 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."
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?
I don’t have a login or any developer access. Sounds like this may be more complicated than I thought! :(
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.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.Try to install propertiary Nvidia drivers, nouveau (open drivers for Nvidia) is a bit... faulty (in this case). :nervous:Code: [Select]python3: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.
Aborted (core dumped)
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
Hello,
after quite a long break from FreeSpace I wondered about the current state and tried to update my installation (3.7 based) to the current version.
Since Knossos is now the recommended installer/launcher I thought I give it a try and stumbled into various issues...
I'm using macOS High Sierra 10.13.6 on a dated MacPro (3,1) with a Nvidia GTX 680... (therefore, I can't update the OS anymore: bad/no Nvidia support etc.)
First try:
I created a new directory for Knossos to be used for the FSO files and started it.
I tried to point the "first run" wizard to my existing FSO installation to get the "retail files". This didn't give any error, but later on I discovered that it didn't do anything to copy the required files.
I installed some mods (MediaVPs, FSPort) and tried to run it.
When launching the FSO binaries (nightly, 3.8 as well as 19.0) I got an application error, "status: -6".
I opened a shell and tried to start the binaries manually and discovered that they have a strange external dependency: They are compiled to use a freetype library at /usr/local/opt/freetype/lib/libfreetype.6.dylib
I think that is strange not only because it doesn't have this dependency bundled, but also because of that path: I'm used to either use /usr/local or /opt, not having both in the pathname...
Ok, MacPorts nowadays uses /opt/local, but that has some more logic in it...
I installed freetype via MacPorts and linked the library files to the path that these binaries expected.
When trying to launch FSO, I now got an error message about the missing retail files...
Second try:
I deleted the configuration files in ~/Library/Preferences and in ~/Library/Application Support as well as the FSO directory for Knossos and started again.
This time, I pointed the "first run" wizard to the installer from GOG. The "Install Retail" window opened and an error dialog appeared during "Extracting InnoExtract...": "Unpacking the GOG installer failed for unknown reasons! ..."
Closing the dialog and the "Install Retail" got me back to the wizard page and I tried to point the wizard to a Freespace 2 installation in a Parallels VM. That didn't seem to work, so I started all over again.
Third try:
I deleted the configuration files and data files again and started Knossos again.
This time, I pointed the "first run" wizard to the installation directory of Freespace 2 in my Parallels VM. Again, just like with the "first try" it happily claimed to be busy doing it's stuff, but after that, the retail files still can't be found in the FSO directory...
So...
...can I do something, to debug that further? Does it write a log file somewhere? I couldn't find one, but I didn't dive into the system area tp look out for it, either...
Where should the retail files go? The movie files seem quite obvious ("./FS2/data/movies") -- but what about the VPs?
Btw: I also tried 0.14, but that just shows a black content area of the window after initialization, so even less usable for me right now.
Kind regards,
webbasan
@jr2: somewhat off topic, but nevertheless: Yes, there are currently still possibilities, but Apple isn't sailing in a direction where I currently want to go. With Mojave (10.14), Apple already dropped Nvidia support somehow (the internal drivers give poor performance and Apple doesn't let Nvidia deploy their "WebDrivers" anymore). I could use a gfx card with an AMD GPU, but that leads to other driver issues: an 11 year old MacPro doesn't get that much love anymore... ;) and Catalina (10.15)... dropped 32 bit support, deprecated OpenGL...
For me, it's currently better to keep my system as-is.
Isn't that handled over Nebula login?Yes. It should be. Knossos should download/fetch that mod and its versions from the server, and then delete it. That's what I am saying.
You need to have FS2 installed to install any mod that isn't a total conversion. You might also need to point Knossos to the exact location of your FS2 directory.Yeah, but the point is ngld hasn't updated his repository, so I decided to take this into my own hands along with the FSO code.
Just because ngld doesn't have time right now you don't need to go to github and break everything.I just merely want to take a look into it and see if I can improve it.
Just because ngld doesn't have time right now you don't need to go to github and break everything.It's not possible to break anything since only ngld can make changes to the "root" repository so no need to worry ;)
~/Downloads/knossos-0.14.0-rc.1$ pipenv install
Warning: Your Pipfile requires python_version 3.6, but you are using 3.7.5 (/home/p/.local/share/v/k/bin/python).
$ pipenv check will surely fail.
Installing dependencies from Pipfile.lock (4724d7)…
Ignoring dmgbuild: markers 'sys_platform == "darwin"' don't match your environment
Looking in indexes: https://pypi.python.org/simple
Ignoring etaprogress: markers 'sys_platform == "win32"' don't match your environment
Looking in indexes: https://pypi.python.org/simple
Ignoring pywin32: markers 'sys_platform == "win32"' don't match your environment
Looking in indexes: https://pypi.python.org/simple
🐍 ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 25/25 — 00:00:04
To activate this project's virtualenv, run the following:
$ pipenv shell
I've installed Python 3.6, so I don't know why this is happening. Not sure if it really matters either.~/Downloads/knossos-0.14.0-rc.1$ yarn install
00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'install'
Not the first clue what I'm doing wrong. I'm sure this is some basic idiocy of mine and I don't want to take up a whole lot of time. Is there some primer that could help explain building and installing for dummies? I'd RTFM I just don't know which one or where to start!~/Downloads/knossos-0.14.0-rc.1$ sudo add-apt-repository ppa:ngld/knossos
[sudo] password for perihelion:
Ubuntu packages for Knossos.
https://github.com/ngld/knossos
More info: https://launchpad.net/~ngld/+archive/ubuntu/knossos
Press [ENTER] to continue or Ctrl-c to cancel adding it.
Hit:1 http://us.archive.ubuntu.com/ubuntu eoan InRelease
Ign:2 http://ppa.launchpad.net/ngld/knossos/ubuntu eoan InRelease
Get:3 http://us.archive.ubuntu.com/ubuntu eoan-updates InRelease [97.5 kB]
Hit:4 http://archive.canonical.com/ubuntu eoan InRelease
Get:5 http://security.ubuntu.com/ubuntu eoan-security InRelease [97.5 kB]
Err:6 http://ppa.launchpad.net/ngld/knossos/ubuntu eoan Release
404 Not Found [IP: 2001:67c:1560:8008::15 80]
Get:7 http://us.archive.ubuntu.com/ubuntu eoan-backports InRelease [88.8 kB]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/ngld/knossos/ubuntu eoan Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Target Sources (main/source/Sources) is configured multiple times in /etc/apt/sources.list.d/ngld-ubuntu-knossos-eoan.list:2 and /etc/apt/sources.list.d/ngld-ubuntu-knossos-eoan.list:5
Never had this come up before; I just reinstalled Mint on a new SSD a week ago and had no errors connecting to ngld's repository at all. This is something new in the last couple days.
I've installed Python 3.6, so I don't know why this is happening. Not sure if it really matters either.
$ python --version
Python 2.7.17
$ python3 --version
Python 3.6.9
python-pyqtwebengine
as dependency into https://aur.archlinux.org/packages/fs2-knossos/ (https://aur.archlinux.org/packages/fs2-knossos/)?It might matter? To find out; what output do you get when you run python --version? Here's two examples from my PC (default python2 & python3). You might need to run the correct version of pipenv.Sorry, first week back at work after the end of year vacation, and all free time evaporated! Back in the fray now. My python version info is:Code: [Select]$ python --version
Python 2.7.17
$ python3 --version
Python 3.6.9
$ python --version
Python 2.7.17
$ python3 --version
Python 3.7.5
So maybe the issue is that I've got a later version of Python3 shipping with Ubuntu than Pipenv knows what to do with? That's what I'd kind of guessed initially, and that's why I tried to manually install Python 3.6, but it didn't seem to take. I tried removing Python3 so I could install just the 3.6 version... yeah, that didn't go too well. I didn't realize how much of what Ubuntu ships with is dependent on Python3. So, reinstalled Ubuntu to try again. Now I'm back at the same place and not really sure if a version of Pipenv exists that works with Python 3.7.5. The version of Pipenv I installed came from the Synaptic Package Manager, so maybe it isn't the freshest build out there.Hi ngld.
Would you mind addingCode: [Select]python-pyqtwebengine
as dependency into https://aur.archlinux.org/packages/fs2-knossos/ (https://aur.archlinux.org/packages/fs2-knossos/)?
Else compilation fails under Arch Linux.
You can try and edit repository and in only Knossos ppa change distribution from eoan to disco.Thanks for the advice, tomimaki. I was able to figure out how to set that repository to disco rather than eoan. That worked! I was able to install from ngld's repository and tried to install knossos. Unfartunately...
$ sudo apt-get install knossos
[sudo] password for perihelion:
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
Depends: python3-raven but it is not installable
E: Unable to correct problems, you have held broken packages.
This sounds vaguely familiar, so I'm going to search a bit through this thread and a few others and see if I'm right and someone else ran into something like this before.Found a hit on deb https://packages.ubuntu.com/ disco universe. But my Software & Updates started getting attitude when I tried to add that repository and locked up.Never ever do this. One thing is editing small ppa, but changing basic ubuntu repo wil break things.
Post it on the Github page via the Issues section.
Post it on the Github page via the Issues section.
Nobody follows orders here. You may request, not acting like a pre-nursery school principal who cant control the class
Post it on the Github page via the Issues section.
Nobody follows orders here. You may request, not acting like a pre-nursery school principal who cant control the class
Bryan's comment was actually something valid.
Ign:1 http://ppa.launchpad.net/ngld/knossos/ubuntu eoan InRelease
Hit:2 http://cn.archive.ubuntu.com/ubuntu eoan InRelease
Err:3 http://ppa.launchpad.net/ngld/knossos/ubuntu eoan Release
404 Not Found [IP: 91.189.95.83 80]
0.14 RC3 is now available: https://github.com/ngld/knossos/releases/tag/v0.14.0-rc.3
Sorry if this is a stupid question, but how can you make a mod use the MediaVPs if it doesn't already? I need to do that for Into the Depths of Hell. Does Knossos have a mod.ini equivalent I need to edit, or is there some other procedure?
Sorry if this is a stupid question, but how can you make a mod use the MediaVPs if it doesn't already? I need to do that for Into the Depths of Hell. Does Knossos have a mod.ini equivalent I need to edit, or is there some other procedure?
It's possible to do this by editing Knossos's configuration files, but you should not do this for ItDoH unless you feel like doing some very extensive debugging. That mod already has a number of warnings that FSO silently accommodates, and introducing MediaVPs would risk adding additional incompatibilities. Also, the mod uses retail backgrounds, so you would have to manually create new MVP backgrounds. Finally, the mod uses several retail-era custom models for which there are no high-poly equivalents, so these would not benefit from the MVPs anyway.
Sorry if this is a stupid question, but how can you make a mod use the MediaVPs if it doesn't already? I need to do that for Into the Depths of Hell. Does Knossos have a mod.ini equivalent I need to edit, or is there some other procedure?
It's possible to do this by editing Knossos's configuration files, but you should not do this for ItDoH unless you feel like doing some very extensive debugging. That mod already has a number of warnings that FSO silently accommodates, and introducing MediaVPs would risk adding additional incompatibilities. Also, the mod uses retail backgrounds, so you would have to manually create new MVP backgrounds. Finally, the mod uses several retail-era custom models for which there are no high-poly equivalents, so these would not benefit from the MVPs anyway.
All right. I didn't know the lack of MediaVPs was intentional. Thanks for letting me know.
You're welcome. I hope that didn't come across as too harsh. It would certainly be nice if ItDoH had MVP support, but it would take a lot of work to get there. Hats off to anyone stalwart enough to slog through it.
In general, mods are set to use a specific version of the MediaVPs and Knossos takes care of making sure you have the right version for whatever mod. The MediaVPs makes sure retail missions still work as intended, but cannot make sure every mod ever still works as intended. Some changes made can affect mods so it is highly encouraged that mod authors test their mod and publish updates to Knossos that set the correct MediaVPs version. For this reason, I never recommend to alter a mod to use the newest MediaVPs unless you are willing and able to deal with potential mod errors.
One more question: Is there something preventing ItDoH from accepting changes to the HUD or fonts? I assumed it wouldn't be a problem because it's still FSO, even without the new graphics, but when I tried copying the appropriate tables and other files, I didn't see any change in-game. I've done this before for other mods, and it worked, so I'm not sure why it's not working here.
There isn't one for 0.14.0 final yet, been having a hard time building with the Mac CI lately. I plan to try my hand at building it again the next time I'm stuck inside as I was put on furlough last Friday.
https://github.com/ngld/knossos/releases
Latest for mac is 0.14.0 RC 1.
https://github.com/ngld/knossos/releases
Latest for mac is 0.14.0 RC 1.
The mac version doesn't seem to be available. thnx... :(
I'm trying to install Knossos on my Ubuntu laptop but I'm not having much luck.QuoteIgn:1 http://ppa.launchpad.net/ngld/knossos/ubuntu eoan InRelease
Hit:2 http://cn.archive.ubuntu.com/ubuntu eoan InRelease
Err:3 http://ppa.launchpad.net/ngld/knossos/ubuntu eoan Release
404 Not Found [IP: 91.189.95.83 80]
Kara, I think ngld did not make a package for a distribution past "Cosmic." I'm using an extended support version of Mint, so I'm still on "Bionic" and I can get the authentications to work properly. But when I was messing around with Ubuntu to see if I could get Knossos to play nicer on it than it was on Mint, I kept running into the same problem you are. There hasn't been a package made for "Eoan." The newest package I can get for "Bionic" is still only 0.13.3, and only about 50% of mods installed correctly on it last time I checked (which was several months ago).I'm trying to install Knossos on my Ubuntu laptop but I'm not having much luck.QuoteIgn:1 http://ppa.launchpad.net/ngld/knossos/ubuntu eoan InRelease
Hit:2 http://cn.archive.ubuntu.com/ubuntu eoan InRelease
Err:3 http://ppa.launchpad.net/ngld/knossos/ubuntu eoan Release
404 Not Found [IP: 91.189.95.83 80]
Still getting this on Ubuntu. When I try to do an apt-get update it also complains about the lack of a release file. Am I the only one getting this error?
It's probably FSPort related and not an issue of Knossos itself.
Knossos can't cause that. It's something in FSPort, I suspect with the localization files Yarn added a few years back.
;-------------------------------------------------
; File: MainHallMenu.cpp
;-------------------------------------------------
353, "(fr)Exit FreeSpace 2"
354, "(fr)Barracks - Manage your FreeSpace 2 pilots"
355, "Salle de départ - Commencer ou continuer une campagne"
356, "(fr)Tech room - View specifications of FreeSpace 2 ships and weaponry"
357, "(fr)Options - Change your FreeSpace 2 options"
358, "(fr)Campaign Room - View all available campaigns"
359, "Multijoueur - Lancer ou joindre une partie multijoueur"
360, "Vous n'avez pas défini le type de connexion Internet. Lancez le programme d'installation, sélectionnez l'option Installation puis l'onglet Réseau pour choisir le type de connexion."
361, "Winsock n'est pas installé. Il vous faut TCP/IP et Winsock pour jouer à FreeSpace en mode multijoueur."
362, "(fr)You have selected TCP/IP for multiplayer Freespace, but the TCP/IP protocol was not detected on your machine."
363, "Vous avez sélectionné la Connexion via modem pour vous connecter à l'Internet. Vous n'êtes pas connecté pour l'instant. Connectez-vous à votre prestataire de service Internet avant d'aller plus loin. "
364, "Vous avez indiqué que vous utilisez une connexion LAN pour les parties en réseau. On dirait que vous êtes connecté à votre prestataire de service Internet. Veuillez vous déconnecter, ou choisissez "
365, "Quitter le jeu ?"
366, "Les pilotes multijoueurs n'ont pas accès à la salle de campagne"
367, "Pilote mutlijoueur non valide !"
368, "'Charger mission' invalide pour pilotes multijoueurs"
369, "Démarrage rapide invalide pour pilotes multijoueurs "
370, "Niveau de difficulté: %s."
371, "Appuyez sur F1 pour afficher l'aide"
sudo apt install nodejs npm python3-wheel python3-setuptools pyqt5-dev pyqt5-dev-tools qttools5-dev-tools qt5-default curl
sudo apt-get install python3-pyqt5.qtwebengine python3-pyqt5.qtwebchannel python3-requests-toolbelt python3-ply
wget http://ppa.launchpad.net/ngld/knossos/ubuntu/pool/main/p/python3-semantic-version/python3-semantic-version_2.3.1-1_all.deb
wget http://ppa.launchpad.net/ngld/knossos/ubuntu/pool/main/k/knossos/knossos_0.13.3-1~cosmic1_all.deb
wget http://ppa.launchpad.net/ngld/knossos/ubuntu/pool/main/p/python3-token-bucket/python3-token-bucket_0.2.0-1_all.deb
wget http://de.archive.ubuntu.com/ubuntu/pool/universe/p/python-raven/python3-raven_6.3.0-2_all.deb
curl https://raw.githubusercontent.com/pypa/pipenv/master/get-pipenv.py | sudo python3
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt update && sudo apt install yarn
pipenv install
yarn install
sudo dpkg -i *.deb
I don't know how to handle "\override_dh_link"! I only know fso:// .
Any ideas?echo 'exec python3 /usr/share/knossos/knossos/__main__.py "$@"' | sudo tee /usr/bin/knossos
Here we go, easy as 1, 2, 3Code: [Select]sudo apt install nodejs npm python3-wheel python3-setuptools pyqt5-dev pyqt5-dev-tools qttools5-dev-tools qt5-default curl
sudo apt-get install python3-pyqt5.qtwebengine python3-pyqt5.qtwebchannel python3-requests-toolbelt python3-ply
wget http://ppa.launchpad.net/ngld/knossos/ubuntu/pool/main/p/python3-semantic-version/python3-semantic-version_2.3.1-1_all.deb
wget http://ppa.launchpad.net/ngld/knossos/ubuntu/pool/main/k/knossos/knossos_0.13.3-1~cosmic1_all.deb
wget http://ppa.launchpad.net/ngld/knossos/ubuntu/pool/main/p/python3-token-bucket/python3-token-bucket_0.2.0-1_all.deb
wget http://de.archive.ubuntu.com/ubuntu/pool/universe/p/python-raven/python3-raven_6.3.0-2_all.deb
curl https://raw.githubusercontent.com/pypa/pipenv/master/get-pipenv.py | sudo python3
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt update && sudo apt install yarn
pipenv install
yarn install
sudo dpkg -i *.deb
After running "knossos" from command line there is an error message popping upCode: [Select]I don't know how to handle "\override_dh_link"! I only know fso:// .
Any ideas?
Sorry, this is a bug in the current Ubuntu package. This will hopefully be solved by the next release. In the meantime you can solve the issue by replacing "\override_dh_link" with "$@" in /usr/bin/knossos.
[ 2567.716064] traps: QtWebEngineProc[3964] trap int3 ip:7f45a9d10cd3 sp:7ffdb95e8ee0 error:0 in libQt5WebEngineCore.so.5.12.8[7f45a561c000+4fac000]
[ 3351.918255] traps: QtWebEngineProc[4239] trap int3 ip:7fe7189f0cd3 sp:7ffe25160e90 error:0 in libQt5WebEngineCore.so.5.12.8[7fe7142fc000+4fac000]
Try 0.13 as described above. It works here in MATE 20.04
Hy people!
Anyone knows how to compile knossos in Ubuntu 20.04 ?
pipenv install fails. Looks like knossos is using a old version of sip and that can't be installed using pip.
An error occurred while installing sip==4.19.8! Will try again.
Installing initially–failed dependencies…
Looking in indexes: https://pypi.python.org/simple00
ERROR: Could not find a version that satisfies the requirement sip==4.19.8 (from -r /tmp/pipenv-22gd3riz-requirements/pipenv-d8e7ucan-requirement.txt (line 1)) (from versions: 5.0.0, 5.0.1, 5.1.0, 5.1.1, 5.1.2, 5.2.0)
ERROR: No matching distribution found for sip==4.19.8 (from -r /tmp/pipenv-22gd3riz-requirements/pipenv-d8e7ucan-requirement.txt (line 1))
Anyone can help?
Thats the output of which command? pipenv install?yes
sudo apt-get update
sudo apt-get install --reinstall python3 build-essential libasound2:i386 libasyncns0:i386 libavahi-client-dev:i386 libc6:i386 libcaca0:i386 libdbus-1-3:i386 libflac8:i386 libgcc1:i386 libglu1-mesa:i386 libjansson4:i386 libjpeg-turbo8:i386 liblua5.1-0:i386 libncursesw5:i386 libogg0:i386 libopenal1:i386 libpulse0:i386 libpulse-dev:i386 libsdl1.2debian:i386 libsdl1.2-dev:i386 libslang2:i386 libsndfile1:i386 libstdc++6:i386 libtheora0:i386 libtinfo5:i386 libvorbis0a:i386 libvorbisenc2:i386 libvorbisfile3:i386 libwrap0:i386 libx11-6:i386 libxau6:i386 libxcb1:i386 libxdmcp6:i386 libxext6:i386 zlib1g:i386
sudo apt-get install --reinstall nodejs npm python3-wheel python3-setuptools pyqt5-dev pyqt5-dev-tools qttools5-dev-tools qt5-default curl python3-pyqt5.qtwebengine python3-pyqt5.qtwebchannel python3-requests-toolbelt python3-ply
sudo add-apt-repository ppa:linuxuprising/libpng12
sudo apt-get update
sudo apt-get install libpng12-0
You better c/p those lines
Python 3.8.2
It worked here
sudo apt install build-essential git p7zip-full libopenal-dev ninja-build pipenv pyqt5-dev pyqt5-dev-tools qttools5-dev-tools qt5-default
sudo apt install nodejs npm yarnpkg
sudo apt install python3-semantic-version python3-pyqt5.qtwebengine python3-requests-toolbelt python3-ply
sudo apt install libsdl2-dev
git clone https://github.com/ngld/knossos.git
cd knossos
pip3 install token-bucket
yarnpkg install
python3 configure.py
ninja run
sudo python3 setup.py install
sudo install -Dm644 ./releng/ubuntu/debian/knossos.desktop /usr/share/applications/knossos.desktop
sudo install -Dm644 ./knossos/data/hlp.png /usr/share/knossos/knossos/data/hlp.png
sudo apt install curl
curl https://raw.githubusercontent.com/pypa/pipenv/master/get-pipenv.py | sudo python3
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt update && sudo apt install yarn
and usingyarn install
yarnpkg install
I just released version 0.14.1: https://github.com/ngld/knossos/releases/tag/v0.14.1
Thanks to the tireless work of chief1983 we now have Mac builds again! There are no other functional changes in this release.
pipenv run python3 configure.py
Warning: Python 3.6 was not found on your system…
python3 version here is 3.8.2 in 20.04. Ideas?
I just released version 0.14.1: https://github.com/ngld/knossos/releases/tag/v0.14.1
Thanks to the tireless work of chief1983 we now have Mac builds again! There are no other functional changes in this release.
@anagram: did you try it in 20.04? As I am no python/programming expert: How to revert your installation instructions, especially the "sudo install" lines?
git pull
sudo python3 setup.py install
sudo pip uninstall knossos
I am not a python programmer myself but I am learning. If the community wants I can try to make a ppa/deb to make it easier to install.SHUT UP AND TAKE MY MONEY! :yes:
I just released version 0.14.1: https://github.com/ngld/knossos/releases/tag/v0.14.1
Thanks to the tireless work of chief1983 we now have Mac builds again! There are no other functional changes in this release.
Hi, no idea where to put this but I'm having issues with the client not showing any mods and with it not downloading from or opening when I click fso://open/ links on fsnebula.org
I have given the Knossos client firewall permissions and the fsnebula.org all Chrome permissions and checked the box for the web association for the client when installing.
I would really appreciate some help...
Hi, no idea where to put this but I'm having issues with the client not showing any mods and with it not downloading from or opening when I click fso://open/ links on fsnebula.org
I have given the Knossos client firewall permissions and the fsnebula.org all Chrome permissions and checked the box for the web association for the client when installing.
I would really appreciate some help...
There is a server side issue ATM
Hi, no idea where to put this but I'm having issues with the client not showing any mods and with it not downloading from or opening when I click fso://open/ links on fsnebula.org
I have given the Knossos client firewall permissions and the fsnebula.org all Chrome permissions and checked the box for the web association for the client when installing.
I would really appreciate some help...
There is a server side issue ATM
Understood, thank you. It appears my problem is fixed now, I reinstalled and deleted all data in Knossos folder in AppData folder.
INFO:MainThread:launcher.main: Running Knossos 0.14.1 on PyQt5 and Python 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 23 2018, 23:31:17) [MSC v.1916 32 bit (Intel)].
INFO:MainThread:launcher.main: OpenSSL version: OpenSSL 1.0.2q 20 Nov 2018
INFO:MainThread:util.call: Running ['C:\\Program Files (x86)\\Knossos\\7z.exe', '-h']
INFO:MainThread:integration.init: Activating Windows integration...
ERROR:MainThread:web.reportError: JS Error: TypeError: Cannot read property 't' of null
at qrc:///html/dist/bundle.js:39:166392
at Object.<anonymous> (qrc:///qtwebchannel/qwebchannel.js:353:35)
at QWebChannel.handleResponse (qrc:///qtwebchannel/qwebchannel.js:137:42)
at Object.QWebChannel.transport.onmessage (qrc:///qtwebchannel/qwebchannel.js:86:25)
ERROR:Thread-1:util.get: Failed to load "https://cf.fsnebula.org/storage/repo.json"! (404 Not Found)
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20180725 (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-20181111 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20181113 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20181114 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20181218 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 20.1.0-20200614 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 20.1.0-20200613 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20191223 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20191228 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20200114 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20200107 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20200119 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 3.8.1-20200129 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 20.1.0-20200206 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 20.1.0-20200209 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 20.1.0-20200412 (FSO)> is empty, ignoring it!
WARNING:Thread-1:repo.add_mod: Mod <Mod "FSO" 20.1.0-20200420 (FSO)> is empty, ignoring it!
git clone -b master https://github.com/ngld/knossos.git
should do it
Just downloaded Knossos and wanted to do some coop with my buddy. Having same issue of nothing but installed mods showing up in Explore tab. It was working fine like 2 days ago, not sure what changed. Is this still the server issues or is there something wrong with my install?
Thanks!
sudo add-apt-repository ppa:linuxuprising/libpng12
sudo apt update
sudo apt install libpng12-0
@flipdark95, if you read the previous page of posts, you'll know as much as everyone else. TL;DR This is an ongoing issue, and volunteers are working on it when they can.
A critical error occurred! Knossos might not work correctly until you restart it.
The error has been reported and will hopefully be fixed soon.
If you want to help, report this bug on our Discord channel, in the HLP thread or on GitHub. Just click a button below to open the relevant page.
I'm going to guess this is a Linux Mint thing because that was happening even with the 0.13.1 Knossos that ngld packaged months ago. Which stinks, but I have a Windows 10 install I can play on. It just is on an old spinny-type hard drive instead of the solid state one Linux is on, so it runs a bit slower. That's fine. Not being able to figure out how to build current (unpackaged) versions of Knossos in Linux was driving me batty, and finally being able to scratch that particular itch feels wonderful! I'm still pretty much a useless leach as far as this community is concerned, but I'm now one step closer to usefulness in a bug testing capacity.ValueError: Invalid requirement specification: '~4.2.3-'
File "knossos/web.py", line 296, in install
windows.ModInstallWindow(mod, pkgs)
File "knossos/windows.py", line 661, in __init__
self.show_packages()
File "knossos/windows.py", line 679, in show_packages
all_pkgs = center.mods.process_pkg_selection(pkgs)
File "knossos/repo.py", line 336, in process_pkg_selection
deps = pkg.resolve_deps()
File "knossos/repo.py", line 733, in resolve_deps
version = util.Spec.from_version(dep.get('version', '*') or '*')
File "knossos/util.py", line 931, in from_version
return Spec(version)
File "semantic_version/base.py", line 449, in __init__
subspecs = [self.parse(spec) for spec in specs_strings]
File "semantic_version/base.py", line 449, in <listcomp>
subspecs = [self.parse(spec) for spec in specs_strings]
File "knossos/util.py", line 919, in parse
res.append(semantic_version.SpecItem(spec_text))
File "semantic_version/base.py", line 393, in __init__
kind, spec = self.parse(requirement_string)
File "semantic_version/base.py", line 408, in parse
raise ValueError("Invalid requirement specification: %r" % requirement_string)
You should be able to see the same error in your log (either on the terminal or ~/.config/knossos/log.txt).Is there any guide on how to properly make mods from scratch for knossos? My google-fu is failing me.
Starting mod "The Aftermath Reboot II" with cmdline "['-orbradar', '-ship_choice_3d', '-3dshockwave', '-soft_particles', '-fxaa', '-fb_explosions', '-enable_shadows', '-dualscanlines', '-targetinfo', '-rearm_timer', '-ballistic_gauge', '-weapon_choice_3d', '-3dwarp', '-warp_flash', '-missile_lighting', '-post_process', '-no_deferred', '-noscalevid', '-mod', 'AftermathReboot2-1.0.0,AftermathReboot-1.1.0,MVPS-3.7.2', '-parse_cmdline_only']" and tool "/home/oliver/FS2/bin/FSO-3.8.0-3/fs2_open_3_8_0_x64.AppImage".
INFO:Thread-19:runner.run: Launching FS2: ['/home/oliver/FS2/bin/FSO-3.8.0-3/fs2_open_3_8_0_x64.AppImage', '-orbradar', '-ship_choice_3d', '-3dshockwave', '-soft_particles', '-fxaa', '-fb_explosions', '-enable_shadows', '-dualscanlines', '-targetinfo', '-rearm_timer', '-ballistic_gauge', '-weapon_choice_3d', '-3dwarp', '-warp_flash', '-missile_lighting', '-post_process', '-no_deferred', '-noscalevid', '-mod', 'AftermathReboot2-1.0.0,AftermathReboot-1.1.0,MVPS-3.7.2', '-parse_cmdline_only'] in /home/oliver/FS2/FS2
AL lib: (EE) ALCpulsePlayback_streamStateCallback: Received stream failure!
I haven't compiled the respective DEBUG build yet, maybe you guys find something or have an ideaHey guys
I'm having an issue with Knossos. Loaded up my computer today and whenever I go to start a game from Knossos I get a brief second of "FSO is launching" up in the top bar and then nothing happens. has this happened to anyone else and if so how did you fix it?
I have a challenge here under Ubuntu 20.04. When running Herkie's Aftermath TBG with Knossos 0.14.1 the game crashes after some minues with wrong colors using 3.8.0 and 19.0.0, seems some VGA stuff?! Card is NVIDIA 1030 with 440. Now I tried compiling 3.7.4 here as Herkie recommended in the release thread, but the game only starts in Window mode (renamed 3.7.4 to 3.8.0.AppImage) and shows "wrong resolution", but it is the correct one. How to fix that? Command line errors from "ninja run" areCode: [Select]Starting mod "The Aftermath Reboot II" with cmdline "['-orbradar', '-ship_choice_3d', '-3dshockwave', '-soft_particles', '-fxaa', '-fb_explosions', '-enable_shadows', '-dualscanlines', '-targetinfo', '-rearm_timer', '-ballistic_gauge', '-weapon_choice_3d', '-3dwarp', '-warp_flash', '-missile_lighting', '-post_process', '-no_deferred', '-noscalevid', '-mod', 'AftermathReboot2-1.0.0,AftermathReboot-1.1.0,MVPS-3.7.2', '-parse_cmdline_only']" and tool "/home/oliver/FS2/bin/FSO-3.8.0-3/fs2_open_3_8_0_x64.AppImage".
I haven't compiled the respective DEBUG build yet, maybe you guys find something or have an idea
INFO:Thread-19:runner.run: Launching FS2: ['/home/oliver/FS2/bin/FSO-3.8.0-3/fs2_open_3_8_0_x64.AppImage', '-orbradar', '-ship_choice_3d', '-3dshockwave', '-soft_particles', '-fxaa', '-fb_explosions', '-enable_shadows', '-dualscanlines', '-targetinfo', '-rearm_timer', '-ballistic_gauge', '-weapon_choice_3d', '-3dwarp', '-warp_flash', '-missile_lighting', '-post_process', '-no_deferred', '-noscalevid', '-mod', 'AftermathReboot2-1.0.0,AftermathReboot-1.1.0,MVPS-3.7.2', '-parse_cmdline_only'] in /home/oliver/FS2/FS2
AL lib: (EE) ALCpulsePlayback_streamStateCallback: Received stream failure!
THX
EDIT: All I had to do was select a joystick or no joystick apparently. This is a...really weird bug.Thank you so much for this priceless hint! I almost gone crazy by shuffling video card drivers and drilling holes into my firewall until I came across this....
What OS are you running this on?
This is one reason I usually just create different pilots for different mods. The system is much more reliable than it used to be, but this campaign quirk still causes me to find different pilots easier to work with.
You could ping ngld on Discord too.
You could ping ngld on Discord too.
Out of curiosity, what is the Hard Light discord invite link?
Still nothing. I had already tried launching as admin, and I've confirmed neither Malwarebytes or Windows Defender are blocking the program.This may not help, but try installing the most current version of the Microsoft Visual C++ libraries (https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads). Some programs need those libraries in order to run properly. If you have a 64-bit OS, you can (and probably should) install both the x86 and x64 versions.
I always get the rare technical issues no one else has, it seems. :/
Glad to see the site back online.
Glad to see the site back online.
Agreed. Curious I didn't have to log back in though. :shrug:
I've got another problem that I've been completely unable to solve the past few days. I think the previous fix may have deleted all my pilot data or something, because I found that none of my save files existed anymore. I then found out that there was like, 50-60GB being eaten up on my PC from old MediaVPS versions, which I didn't know were all being saved separately. So since I lost all my files, I basically decided to start fresh and delete everything, reinstalling Knossos. However, no mods will launch now. If I click "play" on a mod, it says it was last played "a few seconds ago" and it appears to try to load for about 1/10th of a second, then stops. I have uninstalled and reinstalled Knossos, tried installing it to a different folder, etc and nothing is fixing this. "Retail FS2" won't work, either, and presently it is all I have installed on Knossos. Is there some sneaky little leftover file from the old Knossos that's messing everything up or something?Hmm, there's a known issue that uninstalling Knossos doesn't remove Knossos settings/cache folders, even if you check the "Remove Settings" box when uninstalling. I'm working on a fix.
Sorry for all the trouble guys.No problem; we're here to help. :)
And even if I did keep MVPs, I feel like there should be a better way in Knossos of handling optional mods like MVPs, cause it seems like it will always use it if it's there.
Those strings appear in the retail FS2 strings.tbl game file:Code: [Select];-------------------------------------------------
; File: MainHallMenu.cpp
;-------------------------------------------------
353, "(fr)Exit FreeSpace 2"
354, "(fr)Barracks - Manage your FreeSpace 2 pilots"
355, "Salle de départ - Commencer ou continuer une campagne"
356, "(fr)Tech room - View specifications of FreeSpace 2 ships and weaponry"
357, "(fr)Options - Change your FreeSpace 2 options"
358, "(fr)Campaign Room - View all available campaigns"
359, "Multijoueur - Lancer ou joindre une partie multijoueur"
360, "Vous n'avez pas défini le type de connexion Internet. Lancez le programme d'installation, sélectionnez l'option Installation puis l'onglet Réseau pour choisir le type de connexion."
361, "Winsock n'est pas installé. Il vous faut TCP/IP et Winsock pour jouer à FreeSpace en mode multijoueur."
362, "(fr)You have selected TCP/IP for multiplayer Freespace, but the TCP/IP protocol was not detected on your machine."
363, "Vous avez sélectionné la Connexion via modem pour vous connecter à l'Internet. Vous n'êtes pas connecté pour l'instant. Connectez-vous à votre prestataire de service Internet avant d'aller plus loin. "
364, "Vous avez indiqué que vous utilisez une connexion LAN pour les parties en réseau. On dirait que vous êtes connecté à votre prestataire de service Internet. Veuillez vous déconnecter, ou choisissez "
365, "Quitter le jeu ?"
366, "Les pilotes multijoueurs n'ont pas accès à la salle de campagne"
367, "Pilote mutlijoueur non valide !"
368, "'Charger mission' invalide pour pilotes multijoueurs"
369, "Démarrage rapide invalide pour pilotes multijoueurs "
370, "Niveau de difficulté: %s."
371, "Appuyez sur F1 pour afficher l'aide"
My guess is that the French translation was never finished, and the (fr) prefix indicated that the string still remained to be translated.
My question then, Rajive, is how you managed to play a version of the game that did not have this issue. Did you reinstall FSO using a different method -- GOG, Steam, or CD?
Try verifying the file integrity.
P.S.: BPcomplete is version 1.1.1 here!
Can any Mac Mojave users assist below?Thanks for posting here about this. I'm not on Reddit but am working on some Mac fixes for FSO and Knossos. If a Mac player is up for trying out a test build, they can PM me on HLP for details. If they post on #knossos on Discord, I'll probably see it, but a PM here is more reliable.
https://www.reddit.com/r/freespace/comments/jgh64x/does_freespace_open_work_on_mac_mojave_10146/
I have updated to version 1.1.1, it is still not working.A Knossos log would provide more details on the errors. Can you post yours as an attachment?
I have tried to launch other mods in the Knossos launcher. Mods such as Exile, Inferno Nostos, Aftermath Reboot, Sync, etc. are also not working.
I have updated to version 1.1.1, it is still not working.A Knossos log would provide more details on the errors. Can you post yours as an attachment?
I have tried to launch other mods in the Knossos launcher. Mods such as Exile, Inferno Nostos, Aftermath Reboot, Sync, etc. are also not working.
If you're on Windows, you can find the log by opening Explorer (Windows key + E) then in the address bar, type %appdata%\knossos and press Enter. The log file is called log.txt.
EDIT: I know that the error message says that the error has been reported, but only ngld has access to those reports.
D:\Games\Knossos\FS2\Inferno-1.0.0\user.json
chkdsk d: /f
and see if that fixes it (wondering if it's a dirty shutdown in the middle of updating \Inferno-1.0.0\user.json)
Thanks for providing a log. It was very helpful.
Whenever you run the game, Knossos updates the timestamp for when you last played that specific mod. The log says that Knossos is getting a "permission denied" error when it tries to update the relevant file in your Knossos library folder.
The example from your log is for Inferno:Code: [Select]D:\Games\Knossos\FS2\Inferno-1.0.0\user.json
Can you check if this file exists? Open Windows Explorer, paste D:\Games\Knossos\FS2\Inferno-1.0.0 into the address bar, press Enter, and check if the file user.json is there.
If the file does exist, is there some reason why Knossos would not have permission to access it?
You can try running Knossos as administrator, although I'm not sure that should be necessary.
Thanks for providing a log. It was very helpful.
Whenever you run the game, Knossos updates the timestamp for when you last played that specific mod. The log says that Knossos is getting a "permission denied" error when it tries to update the relevant file in your Knossos library folder.
The example from your log is for Inferno:Code: [Select]D:\Games\Knossos\FS2\Inferno-1.0.0\user.json
Can you check if this file exists? Open Windows Explorer, paste D:\Games\Knossos\FS2\Inferno-1.0.0 into the address bar, press Enter, and check if the file user.json is there.
If the file does exist, is there some reason why Knossos would not have permission to access it?
You can try running Knossos as administrator, although I'm not sure that should be necessary.
Yes, the user.json file exists in the folder I have in my personal computer.
rico@AORUS:~$ sudo add-apt-repository ppa:ngld/knossos
Cannot add PPA: ''This PPA does not support focal''.
sudo apt-get install python3 git build-essential libasyncns0:i386 libavahi-client-dev:i386 libc6:i386 libcaca0:i386 libdbus-1-3:i386 libflac8:i386 libgcc1:i386 libglu1-mesa:i386 libjansson4:i386 libjpeg-turbo8:i386 liblua5.1-0:i386 libncursesw5:i386 libogg0:i386 libopenal1:i386 libpulse0:i386 libpulse-dev:i386 libsdl1.2debian:i386 libsdl1.2-dev:i386 libslang2:i386 libsndfile1:i386 libstdc++6:i386 libtheora0:i386 libtinfo5:i386 libvorbis0a:i386 libvorbisenc2:i386 libvorbisfile3:i386 libwrap0:i386 libx11-6:i386 libxau6:i386 libxcb1:i386 libxdmcp6:i386 libxext6:i386 zlib1g:i386 python3-wheel python3-setuptools pyqt5-dev pyqt5-dev-tools qttools5-dev-tools qt5-default curl python3-pyqt5.qtwebengine python3-pyqt5.qtwebchannel python3-requests-toolbelt python3-ply git p7zip-full libopenal-dev ninja-build pipenv yarnpkg python3-semantic-version libsdl2-dev
sudo add-apt-repository ppa:linuxuprising/libpng12
sudo apt-get update
sudo apt-get install libpng12-0
git clone -b master https://github.com/ngld/knossos.git
cd knossos
pip3 install token-bucket
yarnpkg install
python3 configure.py
ninja run
From the howto I made: https://wiki.ubuntuusers.de/Howto/Knossos/
Is there a "clean-up" function anywhere, computing a dependency graph for all the currently installed games/mods and then removing everything not referenced by that graph anymore?
On that note, a verify all that verifies all the installed mods/games in order would be very nice too ;7.
Generally, you can delete all but the most recent versions of all mods (...)
Also, I am absolutely sure that incremental updates (that is, downloading only files/archives that were modified between mod updates) and cleanup of leftovers are definitely in the plans if ngld gets his free time back.As I understand it, they're supposed to already be in, but there might be some bugs there. As an example, I just updated BP from 1.1.1 to 1.1.2. The first thing the update process did was go over every installed file looking for ones that haven't changed. Once that was done, all the unchanged packages were removed from the "to be downloaded" list; instead of reinstalling the whole thing, I only had to download the updated "visuals" packages (1, 3, 4, and 5). Then, the unchanged old files were copied over. And then, since I had no mods depending on 1.1.1, the 1.1.1 folder was emptied out; the old (empty) folder unfortunately sticks around, but at least my harddrive doesn't have 7+ gigs of duplicate data.
As I understand it, they're supposed to already be in, but there might be some bugs there. As an example, I just updated BP from 1.1.1 to 1.1.2. The first thing the update process did was go over every installed file looking for ones that haven't changed.This is correct. Knossos compares the checksums to find identical files, however this doesn't always work. Sometimes the reason is that while the VP contents haven't changed, the VPs were repacked which caused the file checksums to change as well.
This is for Ubuntu. (and in German... :D )I've made the last release available to the new distros as well. However, I can't rebuild the package right now so I have no idea if it even works. It's not even the latest version (the PPA still has 0.13.3 instead of 0.14.3) because I never got around to updating the Ubuntu build scripts. You'll probably be better of building from source.
I tried the Ubuntu package, unsucessfully. I guess that I have no choice but try to compile Knossos from source.
I will give it a try.
Thanks.
Found it. Gosh, it is python-based :sigh: and some web-stuff on-top (or is Node-JS used for Python today as well?) Anyway, not my cup of tea.It's even worse: Python, PyQt5, Qt5, Chromium (QtWebEngine) and Vue (UI framework in JavaScript). The Node.JS stuff is only used to compile the web assets.
Which does not mean that the community, including myself, does not appreciate your work, ngld :) .
Dare I say it, as cool as Knossos is, it seems to focus too much on the fresh install and not on maintaining one.I think a better way to put it would be that Knossos is paranoid about accidentally deleting something you might want to keep. Having to manually delete old mod versions seemed the lesser evil at the time.
It should be possible to compute a dependency graph for all the currently installed games/mods and to remove everything not referenced by that graph anymore. Thoughts?Knossos doesn't track whether mods were installed by the user or to satisfy a dependency. That would have to be added first but aside from that it sounds like a good idea.
It would be wonderful if someone could get Knossos installable again by simply getting it from a PPA, but I gather that is quite a bit of work and requires a decent amount of maintenance to keep it functioning. Praseodym and Anagram have both provided instructions for successfully building Knossos 0.14.3.Here's the build script for Ubuntu (https://github.com/ngld/knossos/blob/1f60d925498c02d3db76a54d3ee20c31b75c5a21/releng/ubuntu/auto-build.sh#L44-L82). Essentially, you have to create an archive with Knossos' sources (see the tar -czf line in the linked script), create a new empty folder, place that archive and the releng/ubuntu/debian folder inside, update the changelog and run "dpkg-buildpackage -us -uc". If anyone can make that work (and the built .deb file works), send me that folder (with the .orig.tar.gz and debian folder) and I'll publish it on the PPA.
While this would be more stable, I worry about users that have many different space-hogging copies of MVP versions or the like only differing in tiny compatability changes because various mods point at slightly different versions. This is already an issue to some extent.
- Dependencies always point to a fixed version of each dependency. Users will always get exactly the release specified by the uploader. I've tried to avoid this because it means that someone has to update all mods depending on MVPs after each MVPs release. However, this will prevent mods from breaking after a dependency updates.
To balance this change, users will get a screen where they can easily edit (add/remove/change) dependencies. I'll put a disclaimer on that page that those changes aren't supported and might cause breakage. Hopefully, that's enough to prevent people from messing up their mods.I'll probably have to do this on the mod installation screen as well. One of the issues with the current dependency resolution is that Knossos always prefers installed versions over available versions which means that as an uploader or mod developer, it's hard to tell which combination of mod versions a user will play with. Pinning dependencies makes the result reproducable and most of all consistent.
I worry about users that have many different space-hogging copies of MVP versions or the like only differing in tiny compatability changesEDIT: I roughly remember m!m implementing some kind of VFS in FSO which could be used to avoid duplicate files for cases like this. Not sure, I'll have to look it up again.
QuoteTo balance this change, users will get a screen where they can easily edit (add/remove/change) dependencies. I'll put a disclaimer on that page that those changes aren't supported and might cause breakage. Hopefully, that's enough to prevent people from messing up their mods.I'll probably have to do this on the mod installation screen as well. One of the issues with the current dependency resolution is that Knossos always prefers installed versions over available versions which means that as an uploader or mod developer, it's hard to tell which combination of mod versions a user will play with. Pinning dependencies makes the result reproducable and most of all consistent.
If we can find some way to guarantee that a mod will work with all possible dependency versions, I'd support it but I don't see that as realistic (not unless we somehow manage to automate testing and build a mod CI).
Also helpful I think would be very prominent display of the versions of each mod being loaded somewhere on the launching interface, right along with the easy overrides you're talking about.That's a good idea. I'll also record the specific mod versions an uploader used to test the mod and display those next to the version you're currently using. That might help with troubleshooting.
This is some unexpected but incredibly welcome news. Great to see you back! :yes:I'm glad to be back and it's nice to see quite a few familiar faces again.
However, this doesn't quite work because "required" packages are not bundled as `.vp` files even if we tell Knossos we want those specific packages bundled.That's a bug. The required/recommended/optional status doesn't influence whether VP packing works (see for example the MediaVPs they have several required packages that contains VPs built by Knossos). Most likely you were affected by a bug that causes Knossos to not reupload a package if the only change is whether Knossos is packing the VP or not. Once you modify a file and upload again, the VP packing should work. That said, this shouldn't be an issue in the rewritten version.
When a user downloads a mod via Knossos it places all the files for each selected package into a single folder combining the packages together.I originally implemented it that way to be compatible with existing FSO launchers. I don't think this matters as much now and reducing the differences between mods in dev and user mode is more important (mostly due to the issues you brought up). The new implementation will create one folder for each package, most likely even if they're packed as VPs since it simplifies the logic involved. As a side effect, VP load order in FSO no longer matters since it'll receive one folder in the -mod list for each package. That should guarantee that the load order is consistent. It creates a few folders that would be unnecessary with the current system but I think it's worth the benefits.
- To balance this change, users will get a screen where they can easily edit (add/remove/change) dependencies. I'll put a disclaimer on that page that those changes aren't supported and might cause breakage. Hopefully, that's enough to prevent people from messing up their mods.
However, this doesn't quite work because "required" packages are not bundled as `.vp` files even if we tell Knossos we want those specific packages bundled.That's a bug. The required/recommended/optional status doesn't influence whether VP packing works (see for example the MediaVPs they have several required packages that contains VPs built by Knossos). Most likely you were affected by a bug that causes Knossos to not reupload a package if the only change is whether Knossos is packing the VP or not. Once you modify a file and upload again, the VP packing should work. That said, this shouldn't be an issue in the rewritten version.When a user downloads a mod via Knossos it places all the files for each selected package into a single folder combining the packages together.I originally implemented it that way to be compatible with existing FSO launchers. I don't think this matters as much now and reducing the differences between mods in dev and user mode is more important (mostly due to the issues you brought up). The new implementation will create one folder for each package, most likely even if they're packed as VPs since it simplifies the logic involved. As a side effect, VP load order in FSO no longer matters since it'll receive one folder in the -mod list for each package. That should guarantee that the load order is consistent. It creates a few folders that would be unnecessary with the current system but I think it's worth the benefits.
EDIT: I roughly remember m!m implementing some kind of VFS in FSO which could be used to avoid duplicate files for cases like this. Not sure, I'll have to look it up again.Do you mean the support for explicitly telling FSO what roots/VPs to use in what order? It's still in a PR but I never got around to fixing up the cross-platform issues unfortunately...
It might prevent some future troubleshooting headaches if, wherever there are settings to customize or change things like this, there is also a "reset to default" option (but you might have already set it up so that this capability is either inherent or included).This is a good idea.
What about being able to set a mod as mod type "Modder's Resource" to indicate the mod isn't intended to be launched directly but instead be used only as a dependency of other mods. This way such mods don't need the full set of dependencies applied as that would be handled by the mod they are a dependency of... which in turn reduces the risk of dependency conflicts and other dependency related issues likely to crop up over time for mods that hardly ever change.That idea had been brought up before but has been veto-ed because Knossos can't filter mods (tags and filtering by tags have been on my TODO list forever). I'll think about adding that type once the rewrite is done but I'll have to think about how it affects dependencies before I can make a definitive decision on this matter.
And what about being able to set a mod's mod type to "Mod Pack" to indicate that the mod adds nothing in and of itself but instead is simply combining other mods via dependencies.An empty mod isn't functionally different from a mod with content. :-P I'd rather solve this about more general tags than an additional mod type. Mod types change how Knossos handles them (i.e. TC doesn't require FS2, engine can only contain executables) but that's not the case in your example.
Also, since your talking about having packages handled as separate `-mod`s anyway... what about package-level dependencies? That way even if i have every FSU MediaVPs package installed when I play a mod that doesn't require the Animglows package the animglows package isn't added to the list of `-mod`s (unless I, as a user, have manually specified otherwise).This is simple enough and already something Knossos can do... but only if the relevant mods are installed in dev mode (yet another reason to get rid of user mode).
Sorry in advance for shotgunning you with ideas. lol :-PI think I'll start a workboard on GitHub too keep track of the different suggestions. As long as I don't lose track of the different ideas, everything's fine. I can't guarantee that everything will make it into the final version, though. :lol:
Do you mean the support for explicitly telling FSO what roots/VPs to use in what order? It's still in a PR but I never got around to fixing up the cross-platform issues unfortunately...Oh, yeah. That's exactly what I was thinking of. Well, I guess I'll have to live without that.
What about being able to set a mod as mod type "Modder's Resource" to indicate the mod isn't intended to be launched directly but instead be used only as a dependency of other mods. This way such mods don't need the full set of dependencies applied as that would be handled by the mod they are a dependency of... which in turn reduces the risk of dependency conflicts and other dependency related issues likely to crop up over time for mods that hardly ever change.That idea had been brought up before but has been veto-ed because Knossos can't filter mods (tags and filtering by tags have been on my TODO list forever). I'll think about adding that type once the rewrite is done but I'll have to think about how it affects dependencies before I can make a definitive decision on this matter.And what about being able to set a mod's mod type to "Mod Pack" to indicate that the mod adds nothing in and of itself but instead is simply combining other mods via dependencies.An empty mod isn't functionally different from a mod with content. :-P I'd rather solve this about more general tags than an additional mod type. Mod types change how Knossos handles them (i.e. TC doesn't require FS2, engine can only contain executables) but that's not the case in your example.
The only special part is that you don't actually need packages. However, adding a single (empty) package isn't too much of an issue IMO.
Also, since your talking about having packages handled as separate `-mod`s anyway... what about package-level dependencies? That way even if i have every FSU MediaVPs package installed when I play a mod that doesn't require the Animglows package the animglows package isn't added to the list of `-mod`s (unless I, as a user, have manually specified otherwise).This is simple enough and already something Knossos can do... but only if the relevant mods are installed in dev mode (yet another reason to get rid of user mode).
Sorry in advance for shotgunning you with ideas. lol :-PI think I'll start a workboard on GitHub too keep track of the different suggestions. As long as I don't lose track of the different ideas, everything's fine. I can't guarantee that everything will make it into the final version, though. :lol:
I'm not sure what the best solution is here. Having some way to manually override the version dependencies (with a hefty warning attached to it) would be good, though I think jr2's idea of a reset function would be a necessity for it, since we're just asking for support headaches otherwise.That's the plan right now.
If there's any way you have of being able to automatically detect potential conflicts with an updated dependency, that'd be fantastic, but I can't imagine that's an easy problem to solve. Maybe the best solution is a human one, i.e. making sure there are enough people who have permissions on these mods to test them out when a new MediavPs version drops and verify them for it in a timely manner. That's especially important for the more classic community mods that may have had just one person upload them to Knossos in the first place.I'm planning on adding a moderator role for Nebula which would allow a user to edit dependencies, block (hide) mods, edit mod teams and maybe more. The idea is that I shouldn't be the only person to fix issues on Nebula. I still have no idea who to give that role to but I guess I'll cross that bridge when I get to it.
Maybe this is an instance where the community could help. Maybe a system where Knossos asks if you would like to test a mod on a newer version of a dependency, and we crowd source getting the mod to accept a newer version? Maybe this is only done when the new version has been out a week or two to give maintainers the chance to vet it themselves, and possibly blacklist it to avoid users being asked to test a known broken version.If we have something like the mod CI I described before, we could probably do this if a mod doesn't have any obvious issues. However, I'd limit this testing to a group of testers because I don't want to confuse people that just want to play FS2 and have no idea how modding works and I want to avoid issues caused by several people missing less-obvious problems.
Sorry in advance for shotgunning you with ideas. lol :-PI think I'll start a workboard on GitHub too keep track of the different suggestions. As long as I don't lose track of the different ideas, everything's fine. I can't guarantee that everything will make it into the final version, though. :lol:
That is essentially what my changes to the command line parsing do. They allow a launcher to specify exactly what VPs or directories should be used in what order. In that case, FSO does not discovery of directories or VP files and just takes what it gets from the launcher.
I wonder what the cross-platform issue is. Case sensitivity?:confused: What do you mean? I am not aware of any platform issues apart from how Windows is stupid and does weird things with the standard output or a GUI process.
I wonder what the cross-platform issue is. Case sensitivity?:confused: What do you mean? I am not aware of any platform issues apart from how Windows is stupid and does weird things with the standard output or a GUI process.
EDIT: I roughly remember m!m implementing some kind of VFS in FSO which could be used to avoid duplicate files for cases like this. Not sure, I'll have to look it up again.Do you mean the support for explicitly telling FSO what roots/VPs to use in what order? It's still in a PR but I never got around to fixing up the cross-platform issues unfortunately...
Oh, I was just referring to some compilation issues on Windows ;)
The problem of FS2 missing has not been fixed. I have a copy on my laptop from GOG and it still gives the same message. Your mod is the only one with this problemCould be the package's dependencies the problem? I want to seek clarification.
You know that 'save' button you have to hit to save your settings changes and if you don't they don't get applied. Please make that button visible on the settings screen without scrolling down. ****ed me up goodI second it, General Battuta.
I'm now at a point where I have to start working on the new UI. (...) I've made a quick mockup. I'm not quite happy with the result but it's a starting point. (...) At this point, I'm open to any changes since it's still in a very early stage.Hi ngld,
You know that 'save' button you have to hit to save your settings changes and if you don't they don't get applied. Please make that button visible on the settings screen without scrolling down. ****ed me up goodI'll definitely fix that. I'm trying to have the dialogs always use the complete available height which means you'll likely see less scrollbars overall. If a dialog requires scrolling, it'll hit the bottom of the window which will hopefully make it more obvious.
What I always wanted is the ability to rate the mods I've played (nothing online, just for me so I know which ones I want to revisit) and to mark the mods I have completed (currently I am using a separate txt file), so I've incorporated several versions of rating icons. You might notice that stars are so well-established for rating that circles and boxes look like progress indicators or something while stars are clear. The checkboxes on the sidebar of the rightmost mod are for update status (replacing the triangle in 0.14.3) and completion status.One of the planned features for the Knossos rewrite are user tags which give users the ability to assign tags to installed mods. If you have bought games on GOG, you can check their implementation for an example how this could look. IMO that's a more powerful system since you could put mods into several categories (backlog, completed, todo, replay after next update, ...) instead of just having a single completed yes/no checkbox.
Also tried to unclutter the UI a bit and add a bigger tile for the last played mod that the user is most likely to return to (no big tile if the last played mod was marked completed (= played through) by the user).I don't really like the uncluttered UI. The version number is displayed in the title bar to make it easier to spot in screenshots (since that part is usually part of screenshots but parts in the bottom area aren't always captured.
Brightened the tooltip to separate it from the background.That's actually a good idea.
Perhaps it should be either round or sharp corners, not both mixed.The only sharp corners right now are the mod tiles which are sharp because they're part of a grid and rounded corners don't really work with grids IMO.
Regarding the settings: applying directly without confirmation is becoming the standard so perhaps you could remove the main save button and only keep the one for the global flags, since these settings are more complex and need more deliberation.The current settings screen has a save button due to the way it's implemented. Saving after every change would require a lot of work to detect the various changes and would be pretty slow. I'll try to fix that in the rewrite but I can't promise anything right now.
Btw: any chance of getting AUR updates again? With the help of the comments there, it was an easy fix, but if you don't have the time, perhaps somebody else can maintain it?I'll take a look tonight. My main issue is that I'm not using Arch nearly as often as I used to so testing has become a bit harder. If anyone wants to take over and can give the package the love it deserves, I'd be happy to hand it over.
Btw: any chance of getting AUR updates again? With the help of the comments there, it was an easy fix, but if you don't have the time, perhaps somebody else can maintain it?I'll take a look tonight. My main issue is that I'm not using Arch nearly as often as I used to so testing has become a bit harder. If anyone wants to take over and can give the package the love it deserves, I'd be happy to hand it over.
[...] considering nuKnossos is (if I understand correctly) not a python application, and will no longer need it.That's correct. NuKnossos is a C++ application with a few bundled libraries which should make it much easier to distribute.
You know that 'save' button you have to hit to save your settings changes and if you don't they don't get applied. Please make that button visible on the settings screen without scrolling down. ****ed me up goodI'll definitely fix that. I'm trying to have the dialogs always use the complete available height which means you'll likely see less scrollbars overall. If a dialog requires scrolling, it'll hit the bottom of the window which will hopefully make it more obvious.
After being a stubborn wxLauncher user for years, and being constantly told that I am handicapping myself by remaining with that launcher, I've finally decided to migrate to Knossos, but my first impressions are leaving a sour taste in my mouth. I can't launch FSO. I've got the latest build selected and it IS in the bin folder, but as soon as I select a downloaded mod and select Play, I get a split-second message in the space next to the search button saying "starting FSO...", but nothing happens. I check in windows' processes, and there's no fso build running.
I am at a loss. Am I S.O.L.?
Thanks for responding, and while I DO have a Thrustmaster 1600, the only switch I can find changes it between right and left handed mode.
Update:
*Headslap*
For some reason, my FSO build within the specific mod, was set to a FRED build. I don't know how THAT happenned, also I hadn't specified my Thrustmaster stick but I doubt that had anything to do with it. Anyway, it's working smoothly now as far as I can tell.
Sorry about my outburst earlier.
This (FRED build selected) should come back with a more useful error for the user IMHO. As well as any hardware issues. Maybe print the last 10 lines from the log to an error message with a button to open the entire log file if nothing else. Otherwise the user is left clueless and frustrated.Knossos should always display an error when FSO launching doesn't result in FSO running for at least a few seconds. However, for whatever reason there is a bug that causes FSO launching to fail without any message. The most common reason seems to be not having any joystick selected (selecting a specific joystick or just "No joystick" and saving the settings seems to fix the issue). I have no idea what the cause is and my only guess is that it's caused by an uncaught exception somewhere but heck if I know where. It's one of the many reasons I'm rewriting Knossos from scratch. I can't reproduce this bug, noone else has any clue why this happens and I can't reproduce it. :banghead:
@ngld
User tags sounds good - being able to tag favorite mods for replaying or to create a tag for any number of stars would make a separate rating system obsolete. Tags could have user-assigned colors that would be displayed on the mod tiles so the user does not have to click on each mod to see the tags.
Some adjustments
- version number relocated
- one type of corners
- tags
- centered play/explore/build/ as well as screenshot/filter/settings
- active tasks more visible (if you still prefer it at the top, I'd recommend an animated busy icon instead of the text)
It's one of the many reasons I'm rewriting Knossos from scratch. I can't reproduce this bug, noone else has any clue why this happens and I can't reproduce it. :banghead:
I could send you my old slightly broken thrustmaster with the PC - PS3 switch, that could probably replicate it.
I really like what you've done with the version numbers and tiles.Thank you!
Regarding the tasks: Would it make sense to turn it into an icon and add it to the icon bar? It'd be a darker shade by default but become bright like the other icons once at least one task is running. I could also add a badge to show the amount of currently running tasks.If it is not too difficult, I would use a animated icon, like in internet browsers. Users are used to having to wait when they see something like this. If it is a bad idea to close Knossos while background tasks are active, you could catch the window close event and display a warning that it is not advisable to close now.
I'll have to test how annoying the new position of the tabs (Play/Explore/Build) is since spreading them out means you have to move your cursor further to reach the ones further right (most of the important stuff is on the left).The clickable area could be maximized so there are no gaps inbetween. For development/heavy use, assigning shortcuts like ASD or Del/End/PgDwn (energy management keys) would reduce mouse movement.
Would it make sense to add themes as an option? Most of this is only CSS after all, so it wouldn't be hard to add themes through CSS files which would allow users (or TCs?) to tweak the way Knossos looks.There might be some people wanting to customize everything - interesting idea to offer TCs the option to go the extra mile. From my point of view, there's not much need for customization as long as the default is using a dark theme. Just being clean and functional with a touch of scifi might be good enough.
EDIT: I forgot to add that some of the info you put on your mockup is kinda hard to obtain. The last played mod and time spent are easy to figure out since Knossos can easily track both. Progress, current campaign, current mission and difficulty would require parsing pilot files. The difficulty is pretty easy to retrieve for modern JSON pilot files but much harder for older pilots. Campaign saves are still stored in a binary format. I'd have to figure out how that changed between FSO versions and how hard it is to parse but it's probably not worth the effort.That's okay, I was just putting in stuff that crossed my mind.
I could send you my old slightly broken thrustmaster with the PC - PS3 switch, that could probably replicate it.Thanks for the offer but I'm hoping that NuKnossos won't share the same issue (since it works completely differently). I'll get back to you if the issue reappears.
If it is not too difficult, I would use a animated icon, like in internet browsers. Users are used to having to wait when they see something like this. If it is a bad idea to close Knossos while background tasks are active, you could catch the window close event and display a warning that it is not advisable to close now.An animated icon sounds like a good solution. I might remove it later if it proves too annoying but that seems unlikely. If you try to close Knossos while background tasks are still running, you'll get the same message you get now (with the addition of an option to cancel running tasks which isn't possible right now).
There might be some people wanting to customize everything - interesting idea to offer TCs the option to go the extra mile. From my point of view, there's not much need for customization as long as the default is using a dark theme. Just being clean and functional with a touch of scifi might be good enough.The idea with TCs comes from way back before Knossos even was a thing. A few TCs wanted a nice installer and IIRC there even was a modified version of wxLauncher for Diaspora? Not sure, it's been too long.
Hot damn, it's really fantastic to see Knossos being worked on again. You're a godsend, ngld. So I figured I would sneak in a couple of my thoughts on the subject because I also have some ideas and feedback.It's nice to be back again. :)
Firstly, about the Nebula moderators (or as I would prefer to call it, the Caretaker role): in my opinion, there should be at least two of such active users in the community, obviously trustworthy, with some level of access to all mods for housekeeping reasons. Updating old mods to higher dependancy versions based on player feedback (after determining that it's properly playable, of course) would be the obvious task to do, but I can also think of resolving duplicates (there are two "Rogues!" mods in Knossos at this point in time, for example), assigning tags, helping people manage their mods in general, or maybe removing things that are widely not accepted (that is, responding to possible troll action). There are a couple other things but that'd depend on what features nuKnossos would have.I mostly agree. Depending on how things go we might end up having caretakers (for public mods) and moderators (which can also access private mods to resolve disputes if necessary or remove obvious abuse i.e. if someone starts uploading stuff that has nothing to do with FSO as a private mod).
Secondly, the interface. From my perspective as a player, a big part of the interface telling me what mod I played recently is completely unnecessary, as when I sit at my computer, I know pretty well what I want to play :P And well, difficulty and campaign progress are player file specific, so getting that right might be quite difficult to do.The idea reminded me of the way Steam shows your recent games as the default home screen. Showing the most recently played mod in some capacity might be useful since you're most likely to play that mod again unless you've finished it already.
Before anything, in my opinion a way to make the interface a bit more straightforward is to allow the users to hide modding resources in a similar way to how FSO builds are handled currently in Knossos. This has been a source of unnecessary clutter lately. I also think that the Explore tab (maybe Home too, depends) needs a little bit of categorising: modding resources could be fully hidden in Home tab but could get a separate category at the tail end of Explore. Total conversions should definitely get their own category too. As for the rest of Freespace content, I'm not too sure how to specifically categorise it... discuss?My current plan is to use tags for this instead of rigid categories. Certain tags would be hidden by default (engine, mod resource, test mod, ...) but the user would be able to add or remove tags from that list to tweak which mods they see (or don't want to see). This could also handle other edge cases like Novachen's translations.
Another useful thing would obviously be sorting mods. For now I can think that current sorting methods are definitely fine, but I would suggest adding "download size (minimum packages)" and "download size (all packages)" to Explore tab sorting, I think it might be of use for people who at the point in time have no decent Internet connection but still want to download something new. Happens to me a lot.Calculating those download sizes might be an interesting challenge since those should include dependencies (but ideally only dependencies that you don't have installed already). Other sorting methods I've thought of are most recently played, most recently updated
In my opinion, Knossos would benefit from a piece of interface that would act as a news outlet, so to say. I think it could be just a minimal several line long text box near the top that would report new events happening on Nebula (and possibly in the community forum), for example think of something like this:This idea has been thrown around for old Knossos as well and was actually planned but never became a reality because it's not easy to implement and I was running out of free time by the time the other parts for Knossos were done. The update / release events themselves are fairly easy to implement. The hardest part for that is where they should appear on the UI but I think this fits nicely with your idea of the new Home tab in the next section.
[Update] Blue Planet Complete v1.2.3 now available!
[Update] Uncharted Territory v1.5.0 now available!
[Release] Dragon's Roar has been released!
[Forum] Screencap contest 04/2021: winner announced!
And it would be absolutely fantastic if it would have been linked to a similar active news box here in the forum. For me that could completely replace the "Last played" part of the interface, but I also thought that it's possible to have both.
How about splitting the current Home tab into two, a Home tab and Library tab? The Home tab could host, for example: the entire "Last played" interface, a "suggested" list/box under it, displaying the tiles of several previously played mods or something, and then a more exhaustive list of news underneath. The Library tab would then just take over the current functionality of current Home tab, that is browsing through all installed mods.I fully agree on the idea of the news box. As I mentioned before, the main issue with that with old Knossos was that there wasn't an obvious place for it in the UI and that it wasn't trivial to implement.
The reason why I'm pushing the idea of an immediately visible news box is for attracting and keeping the attention of players. Seeing a bunch of news about updates, releases and activities happening every couple days around here pretty strongly tells newcomers one important thing: Things Are Constantly Happening Here. This game is the furthest away from "dead" since its release. There's a lot of content, and activity is constantly buzzing. And it doesn't come from the optional and rare visit to the forums, or the Discord - as soon as you launch the game, you get to know that there's lots of activity around it.
As for rating mods, I believe that was discussed back in the day and ended with a "no" both for technical and, well, interpersonal reasons. I think it's pretty understandable that it's hard to give someone a bad score without it feeling hurtful. I personally would be one for some short reviews/comments instead (obviously moderated by the Caretakers), possibly combined with star ratings if the users rating it would explain why they picked this specific score.I definitely want to add an easy way to leave comments and feedback. Something like "Hey, you just finished this campaign / mod. Do you want to leave a comment for the author?". I'm not sure if that comment should stay on Nebula / Knossos or if it should be posted to the forum (release thread?) and/or Discord.
Besides this, I have a couple more ideas forming but for now let me just suggest a tiny detail: in Yasuo's suggested layout, the "up-to-date" box looks interactive, and I presume it isn't. How about changing it to just a green tick, without the box?Not sure, I'll probably end up using one of the icons from an icon collection that's already used in Knossos, though, to stay consistent with the other icons. It'd also be easier than adding a new icon set just for that.
git clone https://github.com/ngld/knossos.git
cd knossos
pip3 install raven
pip3 install token-bucket
yarnpkg install
./task.sh
which gives./task.sh
Building build-tools...
build github.com/ngld/knossos/packages/build-tools: cannot load io/fs: malformed module path "io/fs": missing dot in first path element
Ideas?
./task.sh
Building build-tools...
build github.com/ngld/knossos/packages/build-tools: cannot load io/fs: malformed module path "io/fs": missing dot in first path element
Same resultdpkg -l golang | grep ii
ii golang 2:1.13~1ubuntu2 amd64 Go programming language compiler
sudo add-apt-repository ppa:longsleep/golang-backports
sudo apt-get update
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 52B59B1571A79DBC054901C0F6BC817356A3D45E
sudo apt-get install golang-go
./task.sh
//tasks.star:118:29: Running ldconfig -p
//tasks.star:118:29: Skipping unexpected line from ldconfig: 1937 Bibliotheken im Cache »/etc/ld.so.cache« gefunden
Failed to parse tasks
Traceback (most recent call last):
//tasks.star:248:22: in configure
//tasks/knossos.star:61:25: in knossos_configure
//tasks/helpers.star:138:31: in find_library
//tasks/helpers.star:124:10: in find_static_lib
Error in error: Could not find static library for liblzma! Please make sure it's installed.
Could not find static library for liblzma! Please make sure it's installed.I thought that message is fairly self-explanatory. For Ubuntu, you’ll have to install the following packages: libgtk-3-dev liblzma-dev libzstd-dev zlib1g-dev
./task.sh libknossos-build
...
# github.com/ngld/knossos/packages/libarchive
/usr/bin/ld: i386 architecture of input file `/lib/i386-linux-gnu/libz.a(crc32.o)' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `/lib/i386-linux-gnu/libz.a(inflate.o)' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `/lib/i386-linux-gnu/libz.a(inftrees.o)' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `/lib/i386-linux-gnu/libz.a(zutil.o)' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `/lib/i386-linux-gnu/libz.a(adler32.o)' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `/lib/i386-linux-gnu/libz.a(inffast.o)' is incompatible with i386:x86-64 output
/usr/bin/ld: /lib/i386-linux-gnu/libz.a(adler32.o): in function `adler32_combine':
(.text+0x62b): undefined reference to `__moddi3'
/usr/bin/ld: /lib/i386-linux-gnu/libz.a(adler32.o): in function `adler32_combine64':
(.text+0x6fe): undefined reference to `__moddi3'
collect2: error: ld returned 1 exit status
Failed task libknossos-build:
exit status 2
[0501/201156.258044:WARNING:file_dialog_manager.cc(301)] No file dialog runner available for this platform
@mjn: Thanks for the feedback! I just tried to modernise the UI a bit and I'm certainly better at it than I was back when I started working on Knossos but it still needs a lot of polish. :lol: I'm currently trying to finish the first alpha which should implement the basic Knossos functionality (install, update, remove and launch mods). Once that's done, I want to add some polish before I start working on the dev tab.
Regarding the tabs: I want to let modders create new tabs which they can fill with BBCode content. Having an actual changelog and a staff list could be very helpful, though. Especially since I can fill them with at least some useful info (i.e. usernames, release dates, etc.) even for mods that don't currently have a changelog / staff list.
What do you think about letting users connect their Nebula account to their forum account and adding a PM link to the staff list. That seems like the easiest way to let people contact mod uploaders directly.
/task.sh js-lint
build-tool: nothing to do (output is 54.945247 seconds newer)
fetch-deps: tool fetch-deps
yarn-install: nothing to do (output is 426.513694 seconds newer)
install-tools: nothing to do (output is 433.747071 seconds newer)
proto-build: nothing to do (output is 436.308760 seconds newer)
js-lint: node .yarn/releases/yarn-2.4.1.cjs lint
src/pages/mods/list.tsx:37:83 - error TS2345: Argument of type '{ limit: number; offset: number; query: string; }' is not assignable to parameter of type 'ModListRequest'.
Property 'sort' is missing in type '{ limit: number; offset: number; query: string; }' but required in type 'ModListRequest'.
37 const response = await gs.runTwirpRequest(gs.client.getModList.bind(gs.client), {
~
38 limit: 300,
~~~~~~~~~~~~~~~
...
40 query,
~~~~~~~~~~
41 });
~~~
../api/api/service.ts:171:5
171 sort: ModListRequest_SortType;
~~~~
'sort' is declared here.
Found 1 error.
src/lib/ws-dev-api.ts:1:1 - error TS1208: 'ws-dev-api.ts' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.
1 type Listener = (msg: ArrayBuffer) => void;
~~~~
src/lib/ws-dev-api.ts:4:1 - error TS2578: Unused '@ts-expect-error' directive.
4 // @ts-expect-error We never defined these as properties on window
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/lib/ws-dev-api.ts:9:1 - error TS2578: Unused '@ts-expect-error' directive.
9 // @ts-expect-error We never defined these as properties on window
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Found 3 errors.
src/pages/local-mod.tsx:159:22
⚠ 159:22 flag is already declared in the upper scope on line 152 column 21. no-shadow
src/pages/remote-mod.tsx:1:17
✖ 1:17 useState is defined but never used. @typescript-eslint/no-unused-vars
✖ 2:10 action is defined but never used. @typescript-eslint/no-unused-vars
✖ 2:18 makeAutoObservable is defined but never used. @typescript-eslint/no-unused-vars
✖ 9:3 Checkbox is defined but never used. @typescript-eslint/no-unused-vars
✖ 12:3 HTMLTable is defined but never used. @typescript-eslint/no-unused-vars
✖ 19:10 Release is defined but never used. @typescript-eslint/no-unused-vars
✖ 19:19 ModType is defined but never used. @typescript-eslint/no-unused-vars
✖ 21:8 RefImage is defined but never used. @typescript-eslint/no-unused-vars
src/pages/remote-mod-list.tsx:7:10
✖ 7:10 launchMod is defined but never used. @typescript-eslint/no-unused-vars
✖ 56:11 Unsafe assignment of an any value. @typescript-eslint/no-unsafe-assignment
✖ 56:18 Unsafe member access .toString on an any value. @typescript-eslint/no-unsafe-member-access
✖ 56:18 Unsafe call of an any typed value. @typescript-eslint/no-unsafe-call
✖ 73:9 Unsafe assignment of an any value. @typescript-eslint/no-unsafe-assignment
✖ 73:16 Unsafe member access .toString on an any value. @typescript-eslint/no-unsafe-member-access
✖ 73:16 Unsafe call of an any typed value. @typescript-eslint/no-unsafe-call
1 warning
15 errors
Failed task js-lint:
exit status 1
./task.sh libknossos-build
build-tool: nothing to do (output is 23.215984 seconds newer)
fetch-deps: tool fetch-deps
yarn-install: nothing to do (output is 424.767891 seconds newer)
install-tools: nothing to do (output is 442.314043 seconds newer)
proto-build: nothing to do (output is 445.433336 seconds newer)
libarchive-build: nothing to do (output is 122.142570 seconds newer)
libknossos-build: go build -o ../../build/libknossos/libknossos.so -buildmode c-shared ./api
# github.com/ngld/knossos/packages/libknossos/pkg/storage
pkg/storage/mods.go:80:39: rel.Type undefined (type *common.Release has no field or method Type)
pkg/storage/mods.go:155:45: release.Type undefined (type *common.Release has no field or method Type)
Failed task libknossos-build:
exit status 2
and./task.sh js-lint
build-tool: nothing to do (output is 23.215984 seconds newer)
fetch-deps: tool fetch-deps
yarn-install: nothing to do (output is 424.767891 seconds newer)
install-tools: nothing to do (output is 442.314043 seconds newer)
proto-build: nothing to do (output is 445.433336 seconds newer)
js-lint: node .yarn/releases/yarn-2.4.1.cjs lint
src/pages/local-mod-list.tsx:47:26 - error TS2339: Property 'title' does not exist on type 'Release'.
47 {mod.title}
~~~~~
src/pages/local-mod.tsx:270:58 - error TS2339: Property 'title' does not exist on type 'Release'.
270 <span className="text-3xl">{mod.mod?.title}</span>
~~~~~
src/pages/local-mod.tsx:311:28 - error TS2339: Property 'type' does not exist on type 'Release'.
311 {(mod.mod?.type === ModType.MOD || mod.mod?.type === ModType.TOTAL_CONVERSION) && (
~~~~
src/pages/local-mod.tsx:311:61 - error TS2339: Property 'type' does not exist on type 'Release'.
311 {(mod.mod?.type === ModType.MOD || mod.mod?.type === ModType.TOTAL_CONVERSION) && (
~~~~
Found 4 errors.
sudo apt-get install python3 build-essential libasyncns0:i386 libavahi-client-dev:i386 libc6:i386 libcaca0:i386 libdbus-1-3:i386 libflac8:i386 libgcc1:i386 libglu1-mesa:i386 libjansson4:i386 libjpeg-turbo8:i386 liblua5.1-0:i386 libncursesw5:i386 libogg0:i386 libopenal1:i386 libpulse0:i386 libpulse-dev:i386 libsdl1.2debian:i386 libsdl1.2-dev:i386 libslang2:i386 libsndfile1:i386 libstdc++6:i386 libtheora0:i386 libtinfo5:i386 libvorbis0a:i386 libvorbisenc2:i386 libvorbisfile3:i386 libwrap0:i386 libx11-6:i386 libxau6:i386 libxcb1:i386 libxdmcp6:i386 libxext6:i386 zlib1g:i386 python3-wheel python3-setuptools pyqt5-dev pyqt5-dev-tools qttools5-dev-tools qt5-default curl python3-pyqt5.qtwebengine python3-pyqt5.qtwebchannel python3-requests-toolbelt python3-ply git p7zip-full libopenal-dev ninja-build pipenv yarnpkg python3-semantic-version libsdl2-dev libgtk-3-dev liblzma-dev libzstd-dev zlib1g-dev
sudo add-apt-repository ppa:linuxuprising/libpng12
sudo apt-get update
sudo apt-get install libpng12-0
Additionally, as written earlier on this page, do not link to the static libs via./task.sh configure static_deps=false
git clone https://github.com/ngld/knossos.git
cd knossos
./task.sh
./task.sh check-deps
./task.sh libarchive-build
./task.sh configure static_deps=false
./task.sh libknossos-build # Up to today, it stucks from here, see above
./task.sh client-build #follow the instructions in the terminal.
./task.sh client-ui-build
./task.sh front-build
./task.sh client-run
The final lines used to work, however, I wasnt able to point to the FS2 folder as also shown here.
./task.sh configure build=Release static_deps=false
./task.sh client-run
The build system resolves and handles dependencies automatically and the configure step has to be run before you can run any task (your example would fail on check-deps). You can run it again at any point but that's only useful if you want to change the parameters. If you do that, you should generally remove the build folder to avoid mixing files built with the old options and the new options.libknossos-build: go build -o ../../build/libknossos/libknossos.so -buildmode c-shared ./api
# github.com/ngld/knossos/packages/libknossos/pkg/storage
pkg/storage/mods.go:80:39: rel.Type undefined (type *common.Release has no field or method Type)
pkg/storage/mods.go:155:45: release.Type undefined (type *common.Release has no field or method Type)
Failed task libknossos-build:
exit status 2
[...] With the new "configure" command as step 2 before "check-deps" [...]Why are you running "check-deps"? As "./task.sh -l" will tell you, it only tells you whether the dependencies listed in DEPS.yml have available updates. It doesn't download anything. You're probably looking for "fetch-deps" instead. Also, "front-build" builds the frontend for Nebula and is useless on its own. If you want Nebula, you'd have to run "server-build" as well.
git clone https://github.com/ngld/knossos.git
cd knossos
git checkout d257775c
./task.sh
./task.sh fetch-deps
./task.sh libarchive-build
./task.sh libknossos-build
./task.sh configure build=Release static_deps=false
./task.sh client-build
./task.sh client-ui-build
./task.sh client-run
/home/$USER/knossos/packages/client/launcher/browser/knossos_handler_linux.cc: In member function ‘void KnossosHandler::OpenFolderDialog(CefRefPtr<CefBrowser>, std::string, std::string, CefRefPtr<CefRunFileDialogCallback>)’:
/home/$USER/knossos/packages/client/launcher/browser/knossos_handler_linux.cc:169:42: error: could not convert ‘callback’ from ‘CefRefPtr<CefRunFileDialogCallback>’ {aka ‘scoped_refptr<CefRunFileDialogCallback>’} to ‘std::vector<std::__cxx11::basic_string<char> >’
169 | folder.c_str(), callback);
| ^~~~~~~~
| |
| CefRefPtr<CefRunFileDialogCallback> {aka scoped_refptr<CefRunFileDialogCallback>}
At global scope:
cc1plus: error: unrecognized command line option ‘-Wno-undefined-var-template’ [-Werror]
cc1plus: all warnings being treated as errors
make[3]: *** [launcher/CMakeFiles/knossos.dir/build.make:193: launcher/CMakeFiles/knossos.dir/browser/knossos_handler_linux.cc.o] Fehler 1
make[3]: *** Auf noch nicht beendete Prozesse wird gewartet …
make[2]: *** [CMakeFiles/Makefile2:1152: launcher/CMakeFiles/knossos.dir/all] Fehler 2
make[1]: *** [CMakeFiles/Makefile2:1159: launcher/CMakeFiles/knossos.dir/rule] Fehler 2
make: *** [Makefile:586: knossos] Fehler 2
Failed task client-build:
exit status 2
Ideas?
git clone https://github.com/ngld/knossos.git
cd knossos
./task.sh configure build=Release static_deps=false
./task.sh client-run
[0514/201824.120295:INFO:knossos_resource_handler.cc(142)] [65536;0 # 0/0]
[0514/201824.147077:INFO:knossos_resource_handler.cc(142)] [65536;2 # 2/2]
[0514/201824.147236:INFO:knossos_resource_handler.cc(142)] [65534;0 # 2/2]
Failed task client-run:
exit status 139
Ideas?
/task.sh configure build=Release static_deps=false
Building build-tools...
Failed to parse tasks
Traceback (most recent call last):
//tasks.star:112:43: in configure
Error in getenv: getenv: got 2 arguments, want 1
[00:00]: Fetching remote index
[00:00]: Failed with error: failed to fetch index mods.UpdateRemoteModIndex.func1:github.com/ngld/knossos/packages/libknossos/pkg/mods/modsync.go:149 remote mod not found mods.UpdateRemoteModIndex:github.com/ngld/knossos/packages/libknossos/pkg/mods/modsync.go:139 storage.ImportRemoteMods:github.com/ngld/knossos/packages/libknossos/pkg/storage/remote_mods.go:33 bbolt.(*DB).Update:go.etcd.io/[email protected]/db.go:694 storage.ImportRemoteMods.func1:github.com/ngld/knossos/packages/libknossos/pkg/storage/remote_mods.go:42 mods.UpdateRemoteModIndex.func1:github.com/ngld/knossos/packages/libknossos/pkg/mods/modsync.go:149
Yes, the modsync logic currently doesn't work (unless you run Nebula locally) because the server hasn't been updated, yet, and doesn't serve the files that NuKnossos is looking for.
EXE="/home/$USER/knossos/build/client/launcher/Release/chrome-sandbox" && sudo -- chown root:root $EXE && sudo -- chmod 4755 $EXE
Obviously, "client-run" in the first place "only" does not ask this, as it doesn't ask for the PW. Is that command necessary, and why?
The instructions regarding the SUID binary come from Chromium and shouldn't be necessary on any modern Linux system. The chrome-sandbox binary is only used as a fallback if seccomp-bpf isn't available (any Linux kernel older than 3.5). For reference, here's the relevant Chromium doc (https://source.chromium.org/chromium/chromium/src/+/main:docs/linux/sandboxing.md).Slight correction to the above: Chromium uses user namespaces (a kernel feature introduced in 3.8) instead of the setuid binary in modern kernels. Seccomp-BPF is used in addition to that if it's available to further harden the sandbox (with Seccomp you can restrict the available syscalls).
So I was using Knossos under Windows 7-64bit, but I recently upgraded my PC with an SSD and installed Windows 10-64bit onto it. It unfortunately prevented me from booting Win7 after that, so I copied my FS2 core over to the SSD and reinstalled Knossos. Now however, whenever I update to a new build of FSO, I not only lose the ability to access older builds, but I lose all of my command-line settings. The older builds are still in the bin folder, but Knossos won't read them. What am I doing wrong?
If you switch to the Home tab, click Details on the FSO entry and open the versions drop down on the Details page, do you see more than one version? The Update button by default installs the new version and deletes the previous version (since it handles FSO like any other mod). The easiest way around that is to switch to the details page for FSO (from the Explore tab), select the version you want to install and click the Install button.THANK you! That was the missing piece of the puzzle. During my previous Knossos install, I had not installed FSO as a mod, but rather would update it through another mod's modify options.
At this point I'm not concerned with reviving Win7, and to be clear, Win7 was installed on a 4TB hard drive, which is still connected and accessible, while Win10 is on a 1TB SSD. I'm trying to find out why my Knossos (the copy I've installed on the SSD) seems to want to deny me access to any but my most recently installed build, any why it wants to forget all of my command line settings each time I update to a new build.
bcdboot D:\Windows
I've been trying to get this to work on pop os for weeks now i keep getting exit status 1I'm not clear on the differences between Pop!_OS and Ubuntu, but to be honest, I'm a bit doubtful you'll be able to get the game working on it. That said, if you'd still like to try, see my other response below.
Failed task client-run:
Task client-run failed due to its dependency client-build: exit status 1
It's been a long time and I suddenly had the cravings to play some Freespace 2! :DThere are slightly outdated build instructions (https://github.com/ngld/old-knossos/wiki/Building-instructions) that should point you in the right direction. The list of dependencies is a bit long, but I think you should be able to get everything from the Ubuntu repositories (plus the required Python modules using the pip tool).
I'm on Ubuntu 20.04 and wanted to try knossos but the one in the repository is the older 0.13.3 . So I set out to compile this. I tried "./task.sh configure static_deps=false"
and got the following error:
//tasks.star:151:9: found inputs but no outputs
Can someone tell me what I need to do?
Thanks.
Hope that helps. BTW, you'll likely have better luck getting help on the HLP Discord (https://discord.gg/QFdueKEYrN) than on the forums.
QT_AUTO_SCREEN_SCALE_FACTOR=1 python3 -m knossos
Task client-run failed due to its dependency client-build: Task client-build failed due to its dependency libknossos-build: Task libknossos-build failed due to its dependency libinnoextract-build: Task libinnoextract-build failed due to its dependency libinnoextract-cmake-build: exit status 1
What would cause Knossos to suddenly decide it's only JUST been installed?If you're on Windows, rename the folder %appdata%\knossos. If Linux, I think the folder is ~/.knossos.
Hi,The new Knossos isn't yet complete. The current Knossos repo is here (https://github.com/ngld/old-knossos).
just for development: Building the latest Knossos 1.0 on Ubuntu 20.04 ./task_sh client-run results in
*snip*
So, open Knossos, when it asks where to install everything, I select that folder, then it will say "Oh, everything is there, I don't need to do anything, go ahead and play"?What would cause Knossos to suddenly decide it's only JUST been installed?If you're on Windows, rename the folder %appdata%\knossos. If Linux, I think the folder is ~/.knossos.
Looks like I misunderstood your question.So, open Knossos, when it asks where to install everything, I select that folder, then it will say "Oh, everything is there, I don't need to do anything, go ahead and play"?What would cause Knossos to suddenly decide it's only JUST been installed?If you're on Windows, rename the folder %appdata%\knossos. If Linux, I think the folder is ~/.knossos.
I can't get on Discord. I've tried three times and it keeps failing.Can you give more details on "keeps failing"? What happens when you try? Do you see an error message?
I'm on a desktop PC. I've tried the links that are "invites", I put in a username, it asks me to confirm that I'm not a bot, then it gives the "something out of the ordinary" page and asks for a verification. Now, it seems that whether its successful or not, Discord saves the usernames I've attempted to use in the past, and most importantly, the cellphone number to use for it to send security code. Made my first attempt back in October, but for some reason it didn't take. My attempts more recently have failed ultimately because Discord recognizes that my number has been used before, so it won't let it be used to even attempt to certify another account.
The only method that I haven't explored is using something other than my browser to view Discord in (there is an option for a separate install), but I may still encounter the same stumbling blocks when trying to create an account.
Regardless, this is a moot point with respects to my Knossos problems, as I decided to back-up all of my work and go with the reinstall thing. Fortunately, it auto-detected my current install and the only thing I lost was my command line settings and a few other preferences, easily fixed.
Given how often I will play the game, a work around is completely fine. :)
Where would I check, if such a mapping in windows is active?
I'm having some issues with Knossos after not playing the game for a long time. Is there a way to reset the path to the retail data? I can't load anything because the game exe (which is in the Knossos library folder) doesn't detect the retail files.First, close Knossos, then assuming you're on Windows, go to the "Run..." menu (Windows Key + R), type %appdata% and press Enter, then rename the folder knossos to, say, knossos_old.
Also, one suggestion I have is to somehow highlight the "Freespace Upgrade MediaVP" and "Freespace Port MediaVP" as the options a new player should be using when they first set this up. I had the same issue as this guy (https://www.reddit.com/r/freespace/comments/r7toop/in_case_youre_wondering_if_the_mediavps_work/).Thanks for sharing. I thought the first-run wizard mentions the FS2 MVPs at some point in the process, although I think it just tells you about them; you still have to go find them yourself. No mention of FSPort MVPs, but that was just an oversight.
And stopped using Knossos for a week, and now it's having a stroke. Stuck in endless loops, whether trying to download new content or load any mods. I tried an uninstall and reinstall no joy.
Final option is download and manually install missing packages: https://launchpad.net/~ngld/+archive/ubuntu/knossos/+files/python3-token-bucket_0.2.0-1_all.deb http://mirrors.kernel.org/ubuntu/pool/universe/p/python-raven/python3-raven_6.3.0-2_all.deb
I recommend using one of the newer development builds instead. Give this one a try and see if it works any better for you: https://pxo.nottheeye.com/files/test/knossos/knossos_0.15.0-dev+73b131a_all.deb
pip install ./knossos-0.15.0.dev0+73b131a.tar.gz
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
Processing ./knossos-0.15.0.dev0+73b131a.tar.gz
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/six/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/six/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/six/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/six/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/six/
Could not fetch URL https://pypi.org/simple/six/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/six/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping
ERROR: Could not find a version that satisfies the requirement six (from knossos) (from versions: none)
ERROR: No matching distribution found for six
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping
$ pip install https://pxo.nottheeye.com/files/test/knossos/knossos-0.15.0.dev0+73b131a.tar.gz
Traceback (most recent call last):
File "/usr/bin/pip", line 33, in <module>
sys.exit(load_entry_point('pip==20.3.4', 'console_scripts', 'pip')())
File "/usr/bin/pip", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 790, in exec_module
File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/pip/_internal/cli/main.py", line 10, in <module>
from pip._internal.cli.autocompletion import autocomplete
File "/usr/lib/python3/dist-packages/pip/_internal/cli/autocompletion.py", line 9, in <module>
from pip._internal.cli.main_parser import create_main_parser
File "/usr/lib/python3/dist-packages/pip/_internal/cli/main_parser.py", line 7, in <module>
from pip._internal.cli import cmdoptions
File "/usr/lib/python3/dist-packages/pip/_internal/cli/cmdoptions.py", line 23, in <module>
from pip._vendor.packaging.utils import canonicalize_name
File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 94, in <module>
vendored("requests.packages.urllib3.contrib.pyopenssl")
File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 36, in vendored
__import__(modulename, globals(), locals(), level=0)
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 664, in _load_unlocked
File "<frozen importlib._bootstrap>", line 627, in _load_backward_compatible
File "<frozen zipimport>", line 259, in load_module
File "/usr/share/python-wheels/urllib3-1.26.5-py2.py3-none-any.whl/urllib3/contrib/pyopenssl.py", line 50, in <module>
File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", line 8, in <module>
from OpenSSL import crypto, SSL
File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 1556, in <module>
class X509StoreFlags(object):
File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 1577, in X509StoreFlags
CB_ISSUER_CHECK = _lib.X509_V_FLAG_CB_ISSUER_CHECK
AttributeError: module 'lib' has no attribute 'X509_V_FLAG_CB_ISSUER_CHECK'
System: Kernel: 5.4.0-156-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
Desktop: Cinnamon 4.6.7 wm: muffin dm: LightDM Distro: Linux Mint 20 Ulyana
base: Ubuntu 20.04 focal
Machine: Type: Desktop Mobo: Micro-Star model: B450 GAMING PLUS MAX (MS-7B86) v: 3.0
serial: <filter> UEFI [Legacy]: American Megatrends v: H.10 date: 07/22/2019
CPU: Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ rev: 2
L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102387
Speed: 1375 MHz min/max: 1550/3200 MHz Core speeds (MHz): 1: 1381 2: 1373 3: 1550
4: 1377 5: 1383 6: 1369 7: 1455 8: 1544 9: 1550 10: 1378 11: 1380 12: 1374 13: 1380
14: 1555 15: 1381 16: 1377
Graphics: Device-1: NVIDIA GM206 [GeForce GTX 950] vendor: eVga.com. driver: nvidia v: 470.199.02
bus ID: 29:00.0 chip ID: 10de:1402
Display: x11 server: X.Org 1.20.13 driver: nvidia
resolution: 1920x1080~60Hz, 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 950/PCIe/SSE2 v: 4.6.0 NVIDIA 470.199.02
direct render: Yes
Audio: Device-1: NVIDIA GM206 High Definition Audio vendor: eVga.com. driver: snd_hda_intel
v: kernel bus ID: 29:00.1 chip ID: 10de:0fba
Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel bus ID: 2b:00.3 chip ID: 1022:1457
Device-3: Sunplus Innovation type: USB driver: snd-usb-audio,uvcvideo bus ID: 5-2.4:16
chip ID: 1bcf:2284
Sound Server: ALSA v: k5.4.0-156-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
driver: r8169 v: kernel port: f000 bus ID: 22:00.0 chip ID: 10ec:8168
IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 2.30 TiB used: 459.06 GiB (19.5%)
ID-1: /dev/nvme0n1 vendor: A-Data model: SX8200PNP size: 953.87 GiB speed: 31.6 Gb/s
lanes: 4 serial: <filter>
ID-2: /dev/sda vendor: Hitachi model: HDS721050CLA362 size: 465.76 GiB speed: 3.0 Gb/s
serial: <filter>
ID-3: /dev/sdb vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB
speed: 6.0 Gb/s serial: <filter>
Partition: ID-1: / size: 937.33 GiB used: 459.06 GiB (49.0%) fs: ext4 dev: /dev/nvme0n1p5
Sensors: System Temperatures: cpu: 38.0 C mobo: N/A gpu: nvidia temp: 46 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
1: deb https: //dl.winehq.org/wine-builds/ubuntu/ focal main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com ulyana main upstream import backport #id:linuxmint_main
2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http: //archive.canonical.com/ubuntu/ focal partner
Active apt repos in: /etc/apt/sources.list.d/starws-box-deadbeef-player-focal.list
1: deb http: //ppa.launchpad.net/starws-box/deadbeef-player/ubuntu focal main
Info: Processes: 345 Uptime: 2d 1h 07m Memory: 31.36 GiB used: 5.33 GiB (17.0%) Init: systemd
v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Client: Unknown python3.8 client
inxi: 3.0.38
I know everyone's busy, but has anyone else had problems with recent nightlies and SC builds failing to run from Knossos? I haven't heard anyone else complaining so I'm guessing this is a Linux thing. Older builds still launch and run like normal. But anything from late July onward just fails to launch without even an error message or any entry in the log that I can see, unless maybe there is some other log specific to Knossos I don't know how to find?
Alas, at this point classic Knossos is now mostly outdated. I highly recommend folks switch to using KNet. It is a highly improved launcher, including having orders of magnitude faster loading, better joystick setting, easier option handling, smaller file size, and more 🙂. Moreover, you can install and use KNet without have to change your mod library folder at all, since KNet uses the same file structure as classic Knossos.
https://github.com/KnossosNET/Knossos.NET/releases (https://github.com/KnossosNET/Knossos.NET/releases)