Community Projects > The FreeSpace Campaign Restoration Project
RELEASE: Sync
MrxPL:
Hi, I cannot play this with Media VPs, any of them. I'm using wxLauncher downloaded with FSO installer. Sync was also downloaded with it. When I activate Sync I cannot activate any of the media VPs packages...
ngld:
You can only have one mod active at a time. However, that mod might need other mods to work (the 2014/3.7.2 MediaVPs in this case). If you have a MediaVPs_2014 folder in your FS2 directory, Sync should work as expected and automatically use the updated models, etc. from the MediaVPs.
MrxPL:
Well I downloaded all possible mediaVPs packages that were offered in FSO downloader and still nothing but I managed to overcome this problem by downloading Knossos
Ferret:
Been trying to replay Sync today and have run into a couple of issues. I assumed they were related to changes that had been made in more recent FSO versions but I was even more confused when I noticed the `mod.json` file for Sync had been update to require FSO >= 23.0.0.
Here's the couple of issues I came across:
In SyncE2M7 "...Is To Invite Destruction" the freighter Qetesh is supposed to start zooming away towards the node at some point but doesn't move at all, causing the mission to lock-up. I had to skip it.
In SyncE2M8 "Lost Souls" there are a few ships that are supposed to disappear, but they don't. They stick around but are untargetable, making some of the dialogue pretty hilarious. I suspect this happened in another mission if the same method of removal is being used, but I don't remember specifically which one.
I managed to play through the rest of the campaign without issues beyond these. Wouldn't have reported them if the min-FSO version hadn't been pinned to 23.
This was using FSO 23.1.0-20230423.
Admiral Nelson:
Hi Ferret,
Thanks for the report. You should really only be using nightlies when you want to test out some new feature that they add, and not for playthroughs of campaigns that don't have any of those new features. I tried the two missions you mentioned without incident on 23.0.0.
It is now pinned to use the current FSO since it also is using the current mediavps.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version