[PROGRAM] X Plugin Manager : V1.87 : 2024-01-06

Post by **Cycrow** » Sun, 1. Jul 12, 16:30

i found one slight problem with the beta, but its now fixed and the full version is ready to be used

1.45 is now available

Fixed several memory problems (includes failing to install some ships and crashes)
Fixed 0byte file error
Fixed conflicts detection in installed fakepatchs/mods

Aegyen · Post by **Aegyen** » Sun, 1. Jul 12, 16:48

Nice!..

Been without power for a couple of days, mother nature is not loving us, here across the pond..

Will give everything a run through again here soon...

Ook · Post by **Ook** » Sun, 1. Jul 12, 20:54

New version is working well & the ships show up ingame fine.

As a side note the about window says v1.46

Post by **Cycrow** » Sun, 1. Jul 12, 22:08

i wouldn't worry about the version, i musta incremented the number after the beta

ill just make sure the next version would be 1.47

Akdor 1154 · Post by **Akdor 1154** » Tue, 3. Jul 12, 18:04

Is this able to use its fakepatch managing capacity to deal with mods that are distributed as .dat/.cat? Or can it only muck with its own generated fakepatches?

Post by **Cycrow** » Tue, 3. Jul 12, 19:09

it can only control fake patches that are installed via the plugin manager.

so if you have a cat/dat file you installed manually, then it will just assume they are part of the game.

if you want it to control the fake patches, you can add the cat/dat files into a spk using the creator and then install them.

if there normal mods and not fake patches, then in the creator you can right click and select the option for fake patch, and it'll convert them for you

ad cat/dat file thats in a zip or rar file can also be installed directly using the install archive option

Etyneo · Post by **Etyneo** » Wed, 4. Jul 12, 00:46

I decided it would be best to continue this discussion in this thread, as it deals specifically with the Plugin Manager.

I've been trying to install a few xsp ships from the complete list thread. Specifically the Daedalus, F302, Aurora, and Puddle Jumper. However, I've been having an issue where it won't tell me that it successfully installed and also, after initially selecting a single file (the xsp for the Daedalus) it will act as though there are dependencies (see screencap).

[ external image ]

It should be noted that the dependencies are up to date and attempting to reinstall them leads to failed to install errors. Trying to install the Daedalus without these others ticked will result in some files being copied, but no completion message, and no ship showing up ingame.

As it turns out, this seems to be the result of corrupted records and clearing them fixes the problem.

I figured it'd be a good idea to post my steps for coming up with this problem so that Cycrow can see about tracking it down.

1. Install the Daedalus with uncorrupted records, it installs fine and even has a completion message.
2. Oops, I forgot to back up my edited tships.txt. Uninstall the Daedalus to restore the original to make a backup of.
3. After making said backup, reinstall the Daedalus. Problems noted above occur here, records become corrupted, etc.

Also should note that when the records are corrupted, the program will not exit cleanly and Windows 7 gives me a 'nice' popup window telling me that it has encountered a problem and needs to close.

In addition, I have a feeling I'm going to have issues with my custom tships.txt either being overwritten, or the new ships not appearing. What would be the best approach to remedy this?

Edit:
As it turns out, my tships.txt was not overwritten, but it is simply being ignored.

Edit 2:
I've used X3 Editor to merge the files, but have noted that the Daedalus is named incorrectly (it's supposed to be the 304, not the 303) and am trying to find the t file in /t that contains the name. Anyone know which file I should look for?

{Oversized image altered to a linked thumbnail - Terre}

Post by **Cycrow** » Wed, 4. Jul 12, 09:58

have u made sure u're running the latest version of the plugin manager ?

if you dont have much installed, it might be worth clearing out all the plugin manager data and installing things from scratch. As u might still have a bug from a previous version in the data files

also check the about screen to view all the versions and make sure they are correct

Etyneo · Post by **Etyneo** » Wed, 4. Jul 12, 11:51

Version 1.46 as the window states. I ended up deleting the records for Plugin Manager and uninstalling/reinstalling it. I can install the ships I was looking to install. However, if for any reason I uninstall them, the data gets corrupted at some point between uninstalling them and reinstalling them, as when I attempt to reinstall, I get the incomplete install issue and program no exiting cleanly. This is repeatable for me all day.

However, after playing around with the ships in question for a bit, I've decided that to make them work better, I have to mod them to use entirely new cockpit setups, which will allow me to have them use the weapons I want without having those weapon types appearing on ships I don't want them on...I also want to see about adding all new turrets to the ships (missile only turrets) and am not certain how to do that...

Post by **Cycrow** » Wed, 4. Jul 12, 13:11

does it make a difference if u close the problem between uninstalling and reinstalling, and does it matter which ships you uninstall ?

ie, does it just happen with certain ships, or all of them

Etyneo · Post by **Etyneo** » Wed, 4. Jul 12, 19:12

I was closing the plugin manager between uninstalling and reinstalling so I could make the backups I wanted to. It happens with the Daedalus, the Aurora, the F302, and the Puddle Jumper (all by Balogt.) Package Explorer claims they are older xsps that need converted to be viewable. When converted and viewed, only the loading screen jpg, a pbd, and a few pbbs are listed in the contents of the xsp.

Post by **Cycrow** » Wed, 4. Jul 12, 20:02

the files seem normal, most ships will only have a pdb and pbb files.
i just tried the f302 and it seems to work fine for me.check the about screen and check what version it says for the spk libraries.

also, you could run the plugin manager with the flag, --debug:4
this will enable the debug log.
then just repeat the process until it crashes and send me a copy of the log

grindooo · Post by **grindooo** » Wed, 4. Jul 12, 22:46

new here....looked over the stickies, faq, searched and searched. could not find a solution to my issue. downloaded your plugin manager, an when starting i get an application error....
the application failed to initialize properly (0xc0000135). click on ok to terminate the application.

what could be causing this....tried uninstalling and reinstalling in different directorys, hard drives, and what not....installed latest vc++ and nothing changed.

Etyneo · Post by **Etyneo** » Wed, 4. Jul 12, 23:37

Not certain where to look for a debug log, and not certain if it even entered debug mode. However, I got a screencap of the About screen, and I also manually exported a log showing what happens when I install the F302, uninstall it, then attempt to reinstall it without closing the program once. Unfortunately, the log probably won't show the cause of the exception causing it to not close cleanly. It will run until I tell it to exit, then I'll get that friendly popup telling me that Windows needs to close it...

[ external image ]

And the log can be found here. It will remain available for 1 month as I don't want to leave things up on pastebin permanently (it's rude...)

Post by **Cycrow** » Thu, 5. Jul 12, 01:22

the About screen looks file.
the debug log is in My Documents/Egosoft/pluginmanager.log

it'll be created when you install any package. If its not there, then its likly you havn't enable debug mode.

make sure you run the plugin manager with the correct switch

XPluginManager.exe --debug:4

Etyneo · Post by **Etyneo** » Thu, 5. Jul 12, 02:55

Found it, and have pastebinned it here. Same 1 month limit applies.

I'm not exactly certain what stage it begins at, or if it gets overwritten each time (I hope it appends...) However, the final stage is a successful installation of the Daedalus, F302, Aurora, and Puddle Jumper. Hopefully what you need is in there, if it doesn't append, then I can recreate the problem again easily enough and pastebin the log now that I know where to find it.

Post by **Cycrow** » Thu, 5. Jul 12, 09:58

cant see any problems with the actual installing, the log shows that everything seems to have worked as it should.

which ship did you uninstall and reinstall, and when was it done ?

perhaps the problem is somewhere in the uninstall, i will add some more debug output to the uninstall routines as well

Etyneo · Post by **Etyneo** » Thu, 5. Jul 12, 10:08

I've had it happen with the 302 and the Daedalus for certain, haven't tested the other two yet.

Ook · Post by **Ook** » Thu, 5. Jul 12, 23:28

Cycrow wrote:the About screen looks file.
the debug log is in My Documents/Egosoft/pluginmanager.log

it'll be created when you install any package. If its not there, then its likly you havn't enable debug mode.

make sure you run the plugin manager with the correct switch

XPluginManager.exe --debug:4

Does the package creator support this flag?

ps. package creator crashes when supplying this arg.

Package creator also crashes when attempting to customise the data (press the Ship Data->Customise Ship button) of this ship.

https://dl.dropbox.com/u/3462312/171_Ot ... 8.2007.xsp

Post by **Cycrow** » Thu, 5. Jul 12, 23:37

no it doesn't support debugging yet, althou not sure y its crashing it, will have to check that

egosoft.com

egosoft.com

[PROGRAM] X Plugin Manager : V1.87 : 2024-01-06