Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Kelovar on August 13, 2010, 02:48:29 am
-
Hello, I've played fs2 open about 2 years ago on this same computer with no issues, but since then, I stopped playing and formatted. Now I had an urge to play and reinstalled the game with the most recent versions of the stuff here (I used the automatic installer, which installed me, among many other things, fs2 open.3.6.12 and FSport v3.1.1.
First of all, I'd like to mention a small issue with those: the mod.ini file of fsport-mediavps points to the mediavps folder. With a fresh install like I had, such a folder doesn't exist, since it seems the new Media VPs folders have numbers (like mediavps_3612). It took me quite a while to figure out why it wasn't working, and I suggest someone corrects it.
Now another issue which I encountered is in the mission Enter the Dragon, where you have to disable a SF Dragon. I first played it on the release version, so I hadn't any messages to notify me of anything wrong. However, I noticed something was wrong when, after 10 minutes, nobody could disable that thing: I had all my wingmen on it, and the very rare shots of the slow-firing disruptor that hit it were absorbed by a shield. I played this mission in the original game 10+ years ago, and about 2 years ago on fsport, and I'm pretty sure the Dragon we meet there should be quite slow and easy to shoot (well, for a Dragon anyways), unlike this quick and perfectly nimble one. I became suspicious, then I noticed that the dragon simply had no texture. It was invisible, except for it's thruster lights (took a while to notice in the action... at first, I just thought it was really dark and mostly hidden by the thrusters and UI). I then tried with the debug version and, surprise surprise, I got a warning while loading the mission. The warning is: "Couldn't open texture 'fighter03-01' referenced by model 'fighter03.pof'". Pretty sure that thing should be this Dragon, but it looks like it is missing from the 3.6.12 release. And I guess the game simply decided to replace it with a fully operational (and invisible!) dragon, which is pretty much impossible to disable...?
If you want me to make log files, I'll do it, but I'd like it if someone would try this mission (Enter the Dragon, from fsport-mediavps 3.1.1) using the 3.6.12d version of Media VPs, since that could be verified quite quickly.
I will be away for the weekend, so, depending on when I get an answer, I may not reply before Monday. Thanks in advance.
-
Correction should be that FSO installer needs to treat different versions of mediavps as different mods. At the moment that is not the case and older mediavps, which are still needed to play older mods like FSPort do not work properly. But neither they work properly if set to use new mediavps, debug errors are almost guaranteed.
FSU - please use different fso installer txt-files for each mediavps. Yes, that means people have to download both but it won't break mods either.
-
So I should use an older version of the Media VPs to play the campaign? (sorry, I'm not sure I understood the part about "fso installer txt-files" in your answer. Which txt files are we talking about here?). Is 3.6.10 the best for this one?
Anyways, I can say that I had encountered no problem whatsoever before this mission, meaning that the new VPs is mostly compatible with fsport. Pretty sure it wouldn't require a very big update to make the Media VPs 3.6.12 fully compatible with fsport (or fsport compatible with the new VPs, as I don't know which would be simpler/is the preferred way to do things here).
Thanks for your help.
-
So I should use an older version of the Media VPs to play the campaign? (sorry, I'm not sure I understood the part about "fso installer txt-files" in your answer. Which txt files are we talking about here?).
Nothing you need to worry about.
Is 3.6.10 the best for this one?
Yes.
-
Thanks.
May I suggest to include the option to also install 3.6.10 with the automatic installer? Wouldn't that make sense because right now, the installer offers to install some (there's probably more than just this one right?) campaigns that are not even compatible with the installed Media VPs.
-
FSPort 3.2 with 3.6.12 compatible MediaVPs should be available by the end of the month.
-
So, since I have an old install and the 3.6.10 Mediavps files in addition to the new MEDiavps once I finish downloading them, will there be a problem with fsport 3.1.1?
Second question: Will my pilot files and saves be compatible with fsport 3.2 once that comes out? They are already made with a 3.6.12 Inferno RC build, so they will (or should) work with 3.6.12 MEdiavps.
-
So, since I have an old install and the 3.6.10 Mediavps files in addition to the new MEDiavps once I finish downloading them, will there be a problem with fsport 3.1.1?
If you followed the installation instructions for the FSPort and the .12 mvps correctly, there won't be an issue.
Second question: Will my pilot files and saves be compatible with fsport 3.2 once that comes out? They are already made with a 3.6.12 Inferno RC build, so they will (or should) work with 3.6.12 MEdiavps.
Yes, they will. The only thing that is important for pilot file compatibility is the engine version you're using. Mods do not matter.
-
Again, thank you! :D
Turey's automated installer seems to be doing a pretty good job of updating things, so I expect everything will work just fine. If something goes wrong, I will then squeak for help, but it shouldn't come to that.
Absolutely awesome work, guys! :D