[COMPILATION] Final Mod Pack (FMP)

[arrakis69ct]

dia would be way not useful for FMP
i use https://gephi.github.io/ to work with bigger graphs
the vanilla+FMP connection-network has 600 nodes and 1900 connections (after removing all elements that are not connected)
i attached the image1 as a legend
2 pdf files one with all connections and one "only" with research
its obviuos such a tree is difficult to read
if i would have to do it would do it in gephi itself because there is some nice functionality so you can see what connections are where (image2-detail)
and last but not least the gephi file itself

Madre de dios XD

Guitaaaa con los researchs

[Aldorn]

dia would be way not useful for FMP
i use https://gephi.github.io/ to work with bigger graphs
the vanilla+FMP connection-network has 600 nodes and 1900 connections (after removing all elements that are not connected)
i attached the image1 as a legend
2 pdf files one with all connections and one "only" with research
its obviuos such a tree is difficult to read
if i would have to do it would do it in gephi itself because there is some nice functionality so you can see what connections are where (image2-detail)
and last but not least the gephi file itself

Or in Excel, Visio, ... and manually
But it's right that it's difficult given that there are many requires, needitem, dependencies, getOneFree, unlocks, ...
It's a chinese puzzle

This below is absolutely not the FMP, and it's just to help me building global tech tree. Sure it is no enough...

The tool you used at beginning of FMP seemed interesting

[gerv]

I'm afraid FMP does not work on case-sensitive filesystems. There are several files which are referenced in the ruleset using a different case to the one used for the file in the filesystem. So OpenXcom refuses to start.

Attached is a patch to fix it; one could, of course, rename the files instead.

Gerv

[gerv]

Also:

mv TERRAIN/ufoL83.PCK TERRAIN/UFOL83.PCK

This caused a crash on going to Battlescape. Perhaps it would be a good idea to check the case on all the files? I did an automated check on the paths in the ruleset, and my patch fixes all those. But it seems some files are not referenced so obviously.

Gerv

[Nerevarine64]

I have a slight problem
After researching Dart Rifles, I started manufacturing 14 of them but canceled it at 13 since I didn't actually want a full set, and I cannot manufacture anything else after canceling.

[Nerevarine64]

I have a slight problem
After researching Dart Rifles, I started manufacturing 14 of them but canceled it at 13 since I didn't actually want a full set, and I cannot manufacture anything else after canceling.

Holy shit I'm retarded, I didn't have enough money to start the manufacturing so it didn't go into the next screen. I have a pretty good grasp on the save file code now at least.

[Solarius Scorch]

I'm afraid FMP does not work on case-sensitive filesystems.

Many thanks. I am aware of the problem, but it's not always easy to catch all the bugs, even with tools. Your list will make things much easier.

Holy shit I'm retarded, I didn't have enough money to start the manufacturing so it didn't go into the next screen. I have a pretty good grasp on the save file code now at least.

Good

[gerv]

Also, the cute little single-square smoke-firing HWP looks like it's going nuts and rotating rapidly on the spot when it drives. I assume there's some mistake with the graphics, like referencing the wrong one or something?

Gerv

[Solarius Scorch]

Also, the cute little single-square smoke-firing HWP looks like it's going nuts and rotating rapidly on the spot when it drives. I assume there's some mistake with the graphics, like referencing the wrong one or something?

I can't confirm anything like this, it drives normally for me.

I guess yours has just a really funky AI.

[Arthanor]

Also, the cute little single-square smoke-firing HWP looks like it's going nuts and rotating rapidly on the spot when it drives. I assume there's some mistake with the graphics, like referencing the wrong one or something?

Gerv

Since you already mentioned being on a case sensitive OS, are you using Linux by any chance? If the sprites for the scout vehicle are split into many files in a folder, the Linux OpenXCom does not access the right ones. It can cause issues with weapon mods, new aliens and most likely little robots too..

[Solarius Scorch]

Since you already mentioned being on a case sensitive OS, are you using Linux by any chance? If the sprites for the scout vehicle are split into many files in a folder, the Linux OpenXCom does not access the right ones. It can cause issues with weapon mods, new aliens and most likely little robots too..

Aaaah, that would be it. I should have thought about it myself.

The reason I didn't was because I thought I moved everything to sheets long ago... But I missed the drone.

Oh well, it'll be fixed in the next version.

[Arthanor]

This sprite issue is tricky. It works for everyone except (the few) Linux users, so when we have an issue everyone is like: "Works for me! You must be doing something wrong "

The more of us who know, the more likely we are to think of it

[guille1434]

I just want to report a little bug: In the ruleset file of the Final Mod Pack, in the Ufopaedia entry for the Autocannon AA Clip, the section line (number 12768) says: "WEAPON AND EQUIPMENT"... this causes that the AC_AA_Clip to appear in the game ufopaedia. As I see that all other Alien Alloy ammo clips are not shown as individual entries of the ufopaedia, I think that this would be a little mistake. In consequence, I believe that the line in question shoud read "section: STR_NOT_AVAILABLE".

[Solarius Scorch]

I just want to report a little bug: In the ruleset file of the Final Mod Pack, in the Ufopaedia entry for the Autocannon AA Clip, the section line (number 12768) says: "WEAPON AND EQUIPMENT"... this causes that the AC_AA_Clip to appear in the game ufopaedia. As I see that all other Alien Alloy ammo clips are not shown as individual entries of the ufopaedia, I think that this would be a little mistake. In consequence, I believe that the line in question shoud read "section: STR_NOT_AVAILABLE".

It's actually intentional. The game only shows up to 3 clips per weapon, so if I added a 4th one to the Auto-Cannon, it would be invisible. That's why I made a new Ufopaedia article.

[guille1434]

Yes, you are right... The fourth ammo type will not show in the Auto Cannon page... Sorry! :-)