[The E]

I've had it with your broken installer. Please remove the old INFR1 installers and the install instructions that tell people to put it in their main FS2 folder. It's ****ing annoying.

For reference, this: http://www.hard-light.net/forums/index.php?topic=75426 is happening far too often for my tastes.

[Snail]

(also all your infa downloads are borked)

[Nuclear1]

(also, gargant)

[Snail]

(that too)

[Jeff Vader]

(agreed)

[Woomeister]

INFR1 is for FS2 Retail not SCP, so the install instructions are valid for that, if you do want it working on SCP it probably would need the SCP patch and additional fixes now, especially since it's not mediavp compatible.

You can get INFA here:
http://www.freespacemods.net/download.php?view.94

[The E]

INFR1 is for FS2 Retail not SCP, so the install instructions are valid for that, if you do want it working on SCP it probably would need the SCP patch and additional fixes now, especially since it's not mediavp compatible.

You can get INFA here:
http://www.freespacemods.net/download.php?view.94

That's not the bloody point.

A) Retail compatibility is complete and utter bull**** if it confuses FSO users.
B) I, personally, don't care about Inferno. What I do care about is people who, for whatever reason, follow your instructions and then end up with a ****ed up, non-working install.
C) You already HAVE a package that is FSO-compatible, the Installer downloads it by default. What's so hard about including a readme that says "If you want to use this with retail, you need to do this...." and deleting the other downloads? That would solve the issue quite nicely, I think.

[Zacam]

Retail Compatibility is all well and nice. Really, it is. Posting instructions for how to run the Mod in a Retail setting is all well and good.

But, aside from GoG users or folks that still have the original discs that haven't managed to find us already, they would do well in searching and finding INF into having it lead them to here and using the FSO Build.

Which then means they can use a bloody MOD dir and stop screwing things up when we try to support/troubleshoot everything else they play outside of INF.

So, make the "Retail Mode" a footnote somewhere and discourage this rampant persistence in screwing up good installs. Even FSPort doesn't jack over a good install this way.

[Woomeister]

R1 hasn't been re-released since the SCP started, and like I said to make it mod folder and full mediavp compatible requires a total rebuild of the modpack now cause of the mediavps renaming all the retail maps.
The SCP patch was a quick workaround for old FSO builds, and is probably broken now anyway.

[TopAce]

I could play through R1 fine with a 3.6.13 nightly.

The problem is that if you install according to retail instructions and run another mod with SCP, there's gonna be a mess-up, which you may or may not be able to sort out.

[Qent]

Why are the MediaVPs even in this discussion?

[Dragon]

Perhaps put up two sets of instructions, one for retail and one for SCP (with a link to the patch).

[The E]

Yeah, like that works SO well for the FSPort.

Look, guys, the way you are distributing the mod now is causing problems. You can fix them. Question is, will you? Or do you want to continue causing issues for users?

Let me be clear. The issue is not with the mod data. It is PURELY about how it is distributed to the end user. Fixing that is a different issue from fixing the mod itself.

[Woomeister]

Like I said the patch was for 3.5.5 not for 3.6.12, it's not been updated since so there may be more debug errors to fix and all of our models will load the FS2 RETAIL textures while any none modified pof will load the MEDIAVP ones, this will look weird and we'd get loads of requests to fix it because people would be thinking the mod is broken. It's not as simple as shove new instructions on the website and hope for the best.

R1 was made before the source code was released, before mod directories were around, and before the recent mediavps change all the map names.
If you want to play R1 on SCP wait for the anniversary release, which as a standalone SCP based build will work straight after download.

[The E]

Let me be clear. The issue is not with the mod data. It is PURELY about how it is distributed to the end user. Fixing that is a different issue from fixing the mod itself.

I am not asking you to patch R1 up to current standards. I am asking you to make it impossible for people to accidentally **** up their working FSO installs by following your instructions and getting your downloads. Remember, the FSO installer ALREADY works just fine. It's the people who install INFR1 manually that have problems. Those are the ones you should take care about.

[MatthTheGeek]

Like I said the patch was for 3.5.5 not for 3.6.12, it's not been updated since so there may be more debug errors to fix and all of our models will load the FS2 RETAIL textures while any none modified pof will load the MEDIAVP ones, this will look weird and we'd get loads of requests to fix it because people would be thinking the mod is broken.

No, you won't get any requests, because you will make clear in your install instructions that INFR1 is an outdated mod that will look outdated whatever you do. That's what any sensible being would do.

[Woomeister]

Look, guys, the way you are distributing the mod now is causing problems. You can fix them. Question is, will you? Or do you want to continue causing issues for users?

No because we'd have to do a complete bug hunt, map change and retest and then re-release to make sure its fully SCP ready and that would take weeks and right now we are a small team working on A COMPLETE REBUILD of the original R1. With a very short timeframe. We can't afford to waste time to 'fix' retail R1 for SCP when we're rebuilding it now anyway.

We've never supported R1 working on anything past 3.5.5 as that was the last time it was tested by the team. If someones redistributing it in some kind of 3.6.12 SCP installer then that's their responsibility to have it install into a mod directory

[Woomeister]

No, you won't get any requests, because you will make clear in your install instructions that INFR1 is an outdated mod that will look outdated whatever you do. That's what any sensible being would do.

Then we'll get the 'why is it outdated?' 'why won't you fix it?' threads exactly like this one

[The E]

By offering it up for download, you are implicitly responsible for anything that goes wrong with it. Also, for the third time, you guys already HAVE a solution in place that avoids all these issues. The package that is downloaded by the FSO installer is already set up to play nice with FSO, as far as INFR1 is able to. However, the package that is distributed via your site isn't. The install instructions are still geared towards retail. I am sorry, but I have a hard time believing that changing a few links, maybe repackaging a download, is that hard.

[Woomeister]

Like I said if we had to recompile that version we'd have to fix things up to standard, it would be silly to upload a new version just for a new readme when there's lots of things that have to be fixed like the maps.

I can take down the entire INFSCP site version if you like, that would be the quickest fix for our version, but I can't delete the links as that version was mirrored all over the place by other people so I can't fix those.