Author Topic: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)  (Read 67564 times)

0 Members and 1 Guest are viewing this topic.

Offline ngld

  • Administrator
  • 29
  • Knossos dev
Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
The .vp file is only generated during the upload process and as such you'll never see it on your computer (since you don't really need it yourself).

Make sure the status for your package is set to required. As the error mrssage states, you need to have at least one package in your mod which has its status set to "required". If that still doesn't help, put your mod folder (mod1-x.x.x) in an archive and PM that to me (or upload it somewhere and PM me the link).

 

Offline Colt

  • 24
  • Needs more dakka
    • Steam
Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Whoops. Yeah I left it on recommended instead of required.  Mod's uploaded to Knossos now. Thank you for the help guys!

 
Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Hello guys.

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

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

Thank you.
Requiescat in pace

 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Open up nVidia Control Panel, find the performance area, add FreeSpace 2 Open, tell it to use the high performance graphics card.

 

Offline ngld

  • Administrator
  • 29
  • Knossos dev
Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
@woutersmits: That's nothing Knossos can fix. Either use an adaptable HUD (like the one included with the latest MediaVPs) or encourage the SCP coders to fix the issue in the engine.
The targeting bug is a bug in FSO so there's nothing I can do about that. Find a coder with a 4k screen and tell him to fix that bug.
« Last Edit: February 12, 2019, 03:35:01 pm by ngld »

 
Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
sorry wrong topic
knosses bugs somethin itsays not installed

 

Offline ngld

  • Administrator
  • 29
  • Knossos dev
Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Can you give me the full error message? That would be much more helpful.

 
Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
Hey there! I'm back, got a nostalgia attack xd
I spent some time digging the wiki at first and installed FSO & mediavp the old way (tm), only to found this when I was looking for Blue Planet.

First of all: this launcher/manager is awesome!

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

  • 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"
  • 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.
  • 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)
  • 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:
    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

    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.
<Hades> YOU DO NOT UNDERSTAND
<Hades> And neither do I
------------------------------------------------------------
<pecenipicek> can you root my /?
<mura> HEY!
<mura> get a room
<mura> you perverts

 

Offline ngld

  • Administrator
  • 29
  • Knossos dev
Re: PUBLIC BETA: Knossos 0.13.3 (combined launcher/installer)
First of all: this launcher/manager is awesome!
Thanks! :)

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

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

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

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

Which brings me to the reason of the report: MVP 3.8.2 seems like having a checksum mismatch, whenever I "Verify file integrity", packages MV_Music and MV_RadarIcons show as invalid, despite being redownloaded via Knossos.
That's a result of certain bug fixes on the server... I fixed the downloads but forgot about the checksums. Thanks for the reminder!