Author Topic: Jaded's ModPacks  (Read 2813 times)

0 Members and 1 Guest are viewing this topic.


so going through and reinstalling the mod and ALL of the extras with it even if they have already been installed, i was able to run the freespace2 campaign with the updated visuals, and great job man, now im having issues with this on the blue planet complete. i made sure to install ALL of the files that were available for this install. and i havnt played yet, im just worried about issues. and if this is normal or if i should be informing the mods for blue planet about the issue to possibly get help if its needed.


i really appreciate your work with the mods, i wish i was able to do these things as well. i think it would be fun to tinker with

Hmm, that error usually means something isn't correctly installed. Like an installation partially failed. That's probably not a problem with blueplanet itself, so either my modpack or Knossos is going to be responsible.

Could you run the game in fast debug and then post a log for me? Fast Debug and the option to post a log can be found under the mods `Options` button in `Details`. Similar to the `FSO Settings` above. This should give me a complete list of what files it's failing to find and help me narrow down the source of the problem. Just run the game in fast debug until you get that error then exit and upload the log... then copy the link to me here so i can see it.
« Last Edit: April 07, 2021, 11:08:49 am by jadeddragoon »

 
Hmm, that error usually means something isn't correctly installed. Like an installation partially failed. That's probably not a problem with blueplanet itself, so either my modpack or Knossos is going to be responsible.

Could you run the game in fast debug and then post a log for me? Fast Debug and the option to post a log can be found under the mods `Options` button in `Details`. Similar to the `FSO Settings` above. This should give me a complete list of what files it's failing to find and help me narrow down the source of the problem. Just run the game in fast debug until you get that error then exit and upload the log... then copy the link to me here so i can see it.

Looks like I was wrong... this actually IS an issue in Blueplannet Complete based on info teejaycrunk gave me in discord. There's been a recent change in FSO that affects how sound tables are parsed. It seems the formatting of the BluePlannet Complete sound tables runs afoul of this change.

BPC already has a fix coming down the pipe... i'll release another RC with that version of BPC soon. If you can't wait, make sure you are playing the BluePlanet Complete modpack on 21.0.0 as per here.
« Last Edit: June 29, 2021, 06:58:37 am by jadeddragoon »

 
I really apreciate the work you are doing but i am getting the following:

 
When I try launching your mod collection from Knossos, it says there is no executable found for this mod. What would I need to do to get this to work? Thx.

This looks like a bug in Knossos that I have unwittingly stepped in. Apparently, MJN's Mainhalls must be fully installed even if you only need one mainhall. At least, that's the information I was able to find on the subject. Why that would create this specific error is beyond me. And this one is a bit difficult for me to test.

I'll change the dependencies on the mod in the next release candidate. For now, manually selecting FSO 21.0 should fix the issue.

". Apparently, MJN's Mainhalls must be fully installed"
Jesus.... this is everything that is wrong with Knossos. Please come back wxLauncher!

By the way, i faced this very same problem. It's the same if you try to install 4K Hud, for instance. I had to download Gb of data only for that!


 
Re: Jaded's ModPacks (1.0.0 GOLD!)
Hey guys! Good news. I've been watching for bug reports from these mods for a while now and I'm hearing nothing that can't be traced to knossos bugs. As such I've decided to make the current RCs into the first gold release of my modpacks... with one exception.

The Blue Planet Complete modpack remains in RC status due to it still missing the hd mainhall mod. There's a whole thing behind this, but the good news is it's almost been worked out and the BPC modpack should go gold soon as well. All I'm waiting for is MVPS to update to depend on the 1.4.4 version of the mainhalls mod. Then I'll be able to include them and make one last RC for that modpack. I was originally planning to release the Gold version of the BPC mod without the hd mainhalls... but since we are so close I'm going to go ahead and do so. If I don't get any bug reports it should go gold as well not long after.

Please, if you spot any bugs, don't hesitate to let me know.

 
I really apreciate the work you are doing but i am getting the following:

 
When I try launching your mod collection from Knossos, it says there is no executable found for this mod. What would I need to do to get this to work? Thx.

This looks like a bug in Knossos that I have unwittingly stepped in. Apparently, MJN's Mainhalls must be fully installed even if you only need one mainhall. At least, that's the information I was able to find on the subject. Why that would create this specific error is beyond me. And this one is a bit difficult for me to test.

I'll change the dependencies on the mod in the next release candidate. For now, manually selecting FSO 21.0 should fix the issue.

". Apparently, MJN's Mainhalls must be fully installed"
Jesus.... this is everything that is wrong with Knossos. Please come back wxLauncher!

By the way, i faced this very same problem. It's the same if you try to install 4K Hud, for instance. I had to download Gb of data only for that!



This turned out to be an intermittent Knossos bug. In practice it seems the mainhalls do not need to be fully installed. The actual solution can be found here. Simply select an FSO build from the list. The 1.0.0 version of the mods are tested with 21.2.0... but 21.4.0-RC1 should work just fine as well.

As for going back to wxLauncher... that would be a huge blow to the community. For all of Knossos's flaws it's dependency management system is something this community has desperately needed for decades... almost since the start. The only reason I decided to de-lurk was when I discoved someone had finally made something like Knossos. And with the complete re-write of Knossos months if not weeks from public beta... moving back to wxLauncher now would be a huge mistake.

In any case, glad you're enjoying the mod packs. :-) I'm planning to release several more for other famous campaigns. But only once I've got these four to the point I want them.
« Last Edit: August 09, 2021, 03:43:09 pm by jadeddragoon »

 

Offline EatThePath

  • 27
  • Laser Lich
    • Twitter
and anyway, you can still manually download packages from Nebula with a browser one at a time if you want...
Name your damn turrets and sounds! Numbers alone aren't helpful!
"if disco is dead then I am the laser lich"
"...[Warmachine] keeps changing as fast as EatThePath can force the engine to do his dark bidding..."

 
I really apreciate the work you are doing but i am getting the following:

 
When I try launching your mod collection from Knossos, it says there is no executable found for this mod. What would I need to do to get this to work? Thx.

This looks like a bug in Knossos that I have unwittingly stepped in. Apparently, MJN's Mainhalls must be fully installed even if you only need one mainhall. At least, that's the information I was able to find on the subject. Why that would create this specific error is beyond me. And this one is a bit difficult for me to test.

I'll change the dependencies on the mod in the next release candidate. For now, manually selecting FSO 21.0 should fix the issue.

". Apparently, MJN's Mainhalls must be fully installed"
Jesus.... this is everything that is wrong with Knossos. Please come back wxLauncher!

By the way, i faced this very same problem. It's the same if you try to install 4K Hud, for instance. I had to download Gb of data only for that!



This turned out to be an intermittent Knossos bug. In practice it seems the mainhalls do not need to be fully installed. The actual solution can be found here. Simply select an FSO build from the list. The 1.0.0 version of the mods are tested with 21.2.0... but 21.4.0-RC1 should work just fine as well.

As for going back to wxLauncher... that would be a huge blow to the community. For all of Knossos's flaws it's dependency management system is something this community has desperately needed for decades... almost since the start. The only reason I decided to de-lurk was when I discoved someone had finally made something like Knossos. And with the complete re-write of Knossos months if not weeks from public beta... moving back to wxLauncher now would be a huge mistake.

In any case, glad you're enjoying the mod packs. :-) I'm planning to release several more for other famous campaigns. But only once I've got these four to the point I want them.

Sorry for the (really) late response, jadeddragoon.

I eventually end up downloading every mod that i need manually, manage the packages myself and have various batch scripts for launching the various campaigns. I'm a bit of a control freak and now that i understand who it works, i prefer it this way.
 
Sorry about the little rant about Knossos. It's a great tool if you just want a Steam like interface for quick download and play the mods (and have spare disk space to do so).  And i have a sweet spot for the framework that was used to develop it (qt), so, it's great to see that. As a software developer myself, i know how hard is to maintain something like that.  Going back to wxLauncher is realistically not doable, i understand that.   

 

Sorry for the (really) late response, jadeddragoon.

I eventually end up downloading every mod that i need manually, manage the packages myself and have various batch scripts for launching the various campaigns. I'm a bit of a control freak and now that i understand who it works, i prefer it this way.
 
Sorry about the little rant about Knossos. It's a great tool if you just want a Steam like interface for quick download and play the mods (and have spare disk space to do so).  And i have a sweet spot for the framework that was used to develop it (qt), so, it's great to see that. As a software developer myself, i know how hard is to maintain something like that.  Going back to wxLauncher is realistically not doable, i understand that.   


Absolutely nothing to apologize for! If anything I should. I'm a huge Knossos evangelist and technically have been since before Knossos was even a thing. I've always felt like this community needed something like Knossos. And now that it's here I can't help but be excited for it. So i'm sorry if I came across as upset. I wasn't... I'm just very hopeful for what Knossos can mean for the community from a systemic perspective.

Of course, not everyone is having a good experience with it. And the reasons why are many. Most are Knossos' own fault. Really hoping nu-knossos can address most of those issues. And there are, as you indicate, personal preference reasons some might have to prefer another approach. There's really nothing wrong with that.

Again, sorry if I came across as harsh. Wasn't my intention.