LE Appeal to close down a savegame-dangerous mod

[ilDuderoni]

FINAL EDIT: Issue has been resolved.

 

EDIT: Topic title messed up... Sorry about that. It should say

Appeal to close down a badly oudated, and potentially savegame dangerous mod

If a moderator could edit that to "Appeal to close down a savegame-dangerous mod", I would be most grateful.

<Done>~Lisnpuppy

 

First things first, I debated whether I should put this in the General Mod Author Discussion or the Skyrim one. Eventually chose the latter.

If this is incorrect, feel free to correct the location of the topic.

However, I would prefer it stayed within the Mod Authors forum, because I believe that an issue as serious as this deserves to be brought forward to this level.

That, and I fear it would just drown in the other forums and miss the attention it, I personally believe, deserves.

But of course, I don't have the last call on that.

 

Without further ado:

 

I want to discuss the current state of a former great mod called Tytanis - The Ultimate Mod and bring forth potential issues that continuation of its public availability can have.

 

First and foremost, Tytanis - TUM started out as a great overhaul mod, picking out great parts of (then) popular mods and combining them into one successful package.

It reminded me a little of FOOK and FWE, but both for different reasons.

Sadly, today, even though the page says it has been recently updated, there have been no actual updates found. This includes description, files and images.

An estimate of four months was made by some commenters, for Tytanis to have seen the latest, actual activity.

Now, of course, a mod that has gone out of date is no problem and has no harm. It just dies a slow death, right?

 

Sadly, Tytanis - TUM does not share that fate entirely.

There have been two cases where usage of Tytanis has been seen to corrupt savegames. Whereof one is mine, shared by others.

 

First:

Tytanis - TUM has been said by several commenters to cause crashing to the Magic-selection screen. I did not share this bug so I've not followed up on it. If you dig through the comments section, though, I'm sure you'll find something soon enough.

 

Second:

The mod is capable of corrupting your Savegame upon uninstallation. You can read this in the following topic:

http://forums.nexusm...l-stats-screen/

This has befallen upon me, and I have done my best to find help for this issue. So far, no such luck.

 

In a nutshell:

Upon Uninstalling Tytanis (seeing it was severely out of date) and running Skyrim again, I would go to my General Stats, causing an instant CTD, each and every time. Once I re-installed Tytanis, the CTD no longer occurred again.

As you can read in the linked topic, we have narrowed it down to Tytanis - TUM, or in some relation, to Midas Magic. Suspicion is the implementation of Midas in the mod must be faulty to some extent.

But I am no modder, I can not tell how a mod can affect the General Stats when Tytanis didn't even have the Creation Kit back then.

 

What the most disturbing fact is, is that it is not reproduce-able for all users of the mod. Some users have reported having no additional issues using a savegame that had it installed, having uninstalled it before, as a way to test the theory.

I can question their length of using Tytanis, which MAY be related, but it remains just a theory that it could be of influence. But still it happens to others.

 

So make the math.

- "Some" users of the mod get stricken with the General Stats CTD upon uninstall issue

- So far, no pattern found which sets them apart from others

- It continues to happen today, with the latest Skyrim update.

- Tytanis has been active/online according to his forum profile but has not responded to his comments nor PMs sent to him (by me)

- People also seem to continue to have the Magic-screen crash bug

 

Sounds to me like we should start limiting damage to everyone's savegames, because my posts of warning in the comments section are pushed down to page through within a handful of hours: Not a viable method to warn others.

 

So, I have a set of suggestions that we can do:

1. A moderater makes a notice in beautiful yellow on the Tytanis-TUM description that the mod may be bugged/is unsupported
2. Someone takes it down if the above is not found suitable
3. We round up a few capable modders who can help figure out what exactly of TUM could be affecting the General Stats/Magic Selection screen, and make a new mod for it to fix it, if possible.

 

On a bottom note...I am just one man who is alarmed by the fact that Tytanis-TUM is capable of corrupting saves, and found out that the means I am capable of for warning others is not sufficient.

Take my suggestions as for what they are, suggestions.

 

I hope you, the Moderators and/or Administrators will be able to help me prevent future users from using this dangerously bugged mod, because apparently to some commenters, it's still in the top ten as one of the best mods. Which alarmed me too.

 

And if all else fails, an explanation why you as a Moderator or Admin can not do the suggested actions is always welcome, but not required at all of course.

Edited February 22, 2012 by RJ the Shadow

[Werne]

Well, I highly doubt Tytanis' mod could corrupt a save on it's own, I believe it happens if you have a combination of mods changing several aspects of the same thing (several mods changing a spell or weapon, different things that work together) then removing one or more of them. I used both Tytanis and Midas for some time but I encountered no problems with installing/uninstalling them, even when they were active at the same time.

 

And it could might as well be Bethesda's fault, they don't really have a reputation for making incredibly stabile games that don't corrupt saves, just look at the flying mammoths :biggrin:. Corrupted save problem also happened with Oblivion, Fallout 3, Fallout New Vegas, Skyrim as well (even without mods, happened to me). I don't know did it happen for their older games (Morrowind, etc.) since I didn't play them.

 

Also, in the thread you linked, I see several users saying that they never had Tytanis or they removed it a long time ago before they encountered the problem. I also see a few of them saying it's a problem with Midas Magic and/or combination of Midas and Tytanis.

 

Basically, the reason for problems could be a person's game, maybe PC, combinations of programs and processes running in the background, it could be anything, even your neighbour's dog. For some it makes problems and for others it works like a charm.

 

As for this part:

 

So, I have a set of suggestions that we can do:

1. A moderater makes a notice in beautiful yellow on the Tytanis-TUM description that the mod may be bugged/is unsupported
2. Someone takes it down if the above is not found suitable
3. We round up a few capable modders who can help figure out what exactly of TUM could be affecting the General Stats/Magic Selection screen, and make a new mod for it to fix it, if possible.

 

1. There is no reason for labeling the mod with "this may potentially break your game", ANY mod can break your game if it's combined with the right mod/setting/whatever, also who says it's bugged, many reported having no problems with it. Some users have problems, but considering the ammount of downloads and the ammount of people complaining it's only a minority of users, most of them having problems with mod conflicts and not Tytanis. By the way, if someone were to put that kind of notice on my mod without my knowledge, I'd take it as an insult.

 

2. Unless it's breaking Terms of Service, I don't think that will happen.

 

3. The only bright suggestion in this thread. However, since there aren't many users having that problem it would be hard to find what's causing it. And it may not even be a problem with Tytanis, meaning there's nothing there to fix (basically wasting time trying to figure out what's causing a non-related problem).

 

What I want to say is, you can't make accusation and point fingers at something without proof or any knowledge about the subject, and you have none judging by this post in the very thread you linked:

 

I have no bug expertise whatsoever.

 

That sentence alone means you're suggesting moderators to take down Tytanis' mod (or label it buggy) because it corrupted your save (a common problem that's often unrelated to anything) and all that because you suspect it :rolleyes:.

 

EDIT: Fixing typos, and more typos, and MORE typos :facepalm:

Edited February 20, 2012 by Werne

[Arthmoor]

A call to arms based on such thinly investigated causes? No, I don't think that would be appropriate at all.

[ilDuderoni]

A call to arms based on such thinly investigated causes? No, I don't think that would be appropriate at all.

A call to arms would be calling it a bit too much. I am simply acting on the information I had available on me, which so far was just my experience, that of a few others suffering the issue and virtually no assistance, even though it was posted on the appropriate forums. It did give me a sense of camaraderie with a few other users.

 

If anything, you could call this topic a drastic step to seek out bug support on how to rescue your savegame. But I'm not out to get Tytanis lynched. In fact, I'd go so far as to say, if he reboots Tytanis-TUM, it'll live a life of having to make up for former bad experiences. But if Tytanis made a new mod altogether, I'm sure it'd simply be awesome yet again with little grudges from others.

 

What I want to say is, you can't make accusation and point fingers at something without proof or any knowledge about the subject, and you have none judging by this post in the very thread you linked:

I have no bug expertise whatsoever.

 

That sentence alone means you're suggesting moderators to take down Tytanis' mod (or label it buggy) because it corrupted your save (a common problem that's often unrelated to anything) and all that because you suspect it :rolleyes:.

I partly misspoke there. Although I do not claim to be an expert on bugs, I do have various experiences, mainly in the Gamebryo games. The biggest experience being the way we were taught to narrow down the source of an issue we're having. It's also not encouraging when there is still no FO3Edit -equivalent for Skyrim, which would save me a gigantic amount of work.

 

So please don't paint me off as an inexperienced nobody on the assumption of a single sentence. Bug reports and investigation results is as much evidence as you can get on the internet without sharing files. And I am well willing to do the latter, had you ask.

 

When an issue like this remains unsupported/unhandled, it creates the idea that the bug will never get fixed.

Add to that the, to me, strong implication that Tytanis-TUM is the culprit, and you should understand my alarm when doing the math. (save game corrupting bug + unsupported overhaul + remains in top ten = continuous flow of victims?)

If another new case pops up on the Tytanis comment thread, reporting the very same issue I had, I'll feel like I could have done more.

 

Well, I highly doubt Tytanis' mod could corrupt a save on it's own, I believe it happens if you have a combination of mods changing several aspects of the same thing (several mods changing a spell or weapon, different things that work together) then removing one or more of them. I used both Tytanis and Midas for some time but I encountered no problems with installing/uninstalling them, even when they were active at the same time.

 

And it could might as well be Bethesda's fault, they don't really have a reputation for making incredibly stabile games that don't corrupt saves, just look at the flying mammoths :biggrin:. Corrupted save problem also happened with Oblivion, Fallout 3, Fallout New Vegas, Skyrim as well (even without mods, happened to me). I don't know did it happen for their older games (Morrowind, etc.) since I didn't play them.

 

Also, in the thread you linked, I see several users saying that they never had Tytanis or they removed it a long time ago before they encountered the problem. I also see a few of them saying it's a problem with Midas Magic and/or combination of Midas and Tytanis.

 

Basically, the reason for problems could be a person's game, maybe PC, combinations of programs and processes running in the background, it could be anything, even your neighbour's dog. For some it makes problems and for others it works like a charm.

 

Hearing that, I'm thinking you got some proper experience yourself. And again, it's not so much perfectly indicating that the eventual culprit is Tytanis, it's that there are simply no other suspects save for Midas. And I think Midas still works fine to date.

 

The fact remains, the bug is still there, dominating the savegame I've spend...well worth months on now.

I've asked for help and everyone stayed silent. I was only a command or two away of showing any modder my bugreporting skills when they said they'd look into it. But not even that. So I've come here, carrying the thought I've mentioned a few times by now.

 

What choices would you make when wanting to rescue your savegame? Here's what I did.

- I reported it where I could/appropriate

- Followed up on it

- Found out support is MIA

- Looked to prevent others from getting in the same pickle

 

The fact that there is more then one bug associated with Tytanis is only more alarming.

Personally, I know that the mods I have installed modify the game nowhere as much on their own as Tytanis does. It literally makes no sense that ANY mod would cause a crash on the General Stats screen, yet preventing it requires an installation of Tytanis. I'm calling this a Twilight Zone mystery.

 

Bottom line, if I disable all .esp files, but have to re-install Tytanis and Tytanis only (and enable the plugin file in the load order) in order to no longer reproduce the crash, I am calling it the culprit.

Worse, saving your game with it uninstalled while unaware that you suffer the bug and THEN installing it again, will still produce the crash.

And come on, if you think this topic is ridiculous, what would you have said if I claimed it was the fault of Midas?

 

 

I've just now received a response in the mods Bug Tracker, I'm going look into it further. But as it stands, I believe I've found my culprit but invite everyone to prove me wrong with 'their' evidence.

 

If you have modding skills, please look into it. You obviously must be interested or you would not write such a lengthy post about it.

Edited February 21, 2012 by RJ the Shadow

[Astymma]

You do realize that ALL mods potentially carry these risks? That this is a known problem inherent to modding this engine since Morrowind's days? That calling for action *publicly* is essentially trolling the author? Save files are basically a very fragile linked list database and incorrect removal of a vital link such as a large overhaul mod is almost guaranteed to have consequences. Welcome to TES/Fallout gaming... chalk it up to experience and move on.

 

Personally, I find this appeal against Tytanis reprehensible. If you can substantiate your claims, report the mod through the appropriate method. If you can't, don't slander the mod author publicly...

[Fatalmasterpiece]

I ran into similar problems with NV Bounties and ended up with corrupt save files. After discussing it with the author I came to the same conclussions that Werne describes above. Essentially, I know it sucks but corrupted saves are a fact of life when heavily modding Bethesda games.. I have to agree with the two posters above me.

 

The best thing to do is learn from this experience and start using an alternative save game manager.

[Werne]

Hearing that, I'm thinking you got some proper experience yourself. And again, it's not so much perfectly indicating that the eventual culprit is Tytanis, it's that there are simply no other suspects save for Midas. And I think Midas still works fine to date.

 

Yes, I have some proper experience, I've been able to run FO3 with over 600 mods and no problems for a year or so. I experienced a corrupted save problem only once, I solved it easily by reloading an older save. And Midas might be the problem as well, I've seen many "fine working" mods that make all sorts of problems unrelated to what they change and they start making those problems when you remove a mod that has absolutely nothing to do with them.

 

The fact remains, the bug is still there, dominating the savegame I've spend...well worth months on now.

 

Do you overwrite the save or do you create a new one each time you go to save? If you overwrite it you have a much higher chance of losing it, always save a new one. Always. Also turn off auto-saves and don't quick-save, all that can screw up your save in many ways.

 

What choices would you make when wanting to rescue your savegame? Here's what I did.

- I reported it where I could/appropriate

- Followed up on it

- Found out support is MIA

- Looked to prevent others from getting in the same pickle

 

First of all, you need to ask yourself what did you do to protect it, before it died and you need to rescue it. Judging by this being your first introduction into Bethesda's wonderful world of bugs and glitches you have no previous experience, I can't blaim you for not knowing. But now you do know how to prevent this and you'll hopefully be more cautious next time. And by the way, there is no way to get your save back, at least not for now.

 

The fact that there is more then one bug associated with Tytanis is only more alarming.

 

Not really, the first thing I learned when I started modding is that out of 50 bug reports, there will be 20 different bugs. It all depends on different mods users have active and their load order, in extreme cases the external programs cause problems but those are rare.

 

Personally, I know that the mods I have installed modify the game nowhere as much on their own as Tytanis does. It literally makes no sense that ANY mod would cause a crash on the General Stats screen, yet preventing it requires an installation of Tytanis. I'm calling this a Twilight Zone mystery.

 

Let's take a visual example to explain this:

 

Imagine having a big-ass rock on the floor (Tytanis). Now imagine having a small stone next to it (a small mod). What happens if I throw 20 other stones ( add more mods) on that one next to the rock? It piles up, and when you throw enough stones on that pile it will become bigger than the rock.

 

Now, if I throw that rock on a car (your savegame) it will make a mess. But if I tie those piled-up stones in a sack and throw them on the car it will make even more damage because they exceded the size and weight of the rock.

 

Now technically speaking, you have small mods, but if you combine the things they change they can modify the game into a larger extend than Tytanis alone. The size of one mod has no difference on the impact, the quantity of modified data from the combination does.

 

Bottom line, if I disable all .esp files, but have to re-install Tytanis and Tytanis only (and enable the plugin file in the load order) in order to no longer reproduce the crash, I am calling it the culprit.

Worse, saving your game with it uninstalled while unaware that you suffer the bug and THEN installing it again, will still produce the crash.

 

That still doesn't mean it's the fault of Tytanis, it might as well be that your savegame is damaged and Tytanis changes a variable which rectifies the issue. For example: When the corruped save problem occured for me on FO3 there was one mod that kept it still running, Darnified UI. My first thought was like yours, but I kept digging (cause I'm a nosy bastard) so I transfered my save onto my brother's computer and I installed all the mods I had, along with Darnified UI. When I loaded it, the game crashed immediately just like mine without DUI.

 

Then I've dug even deeper to find out what's causing the different behaviour, since the conditions are the same. And I found it, the reason for the difference was a background process, I had an aditional program running in the background which in combination with DUI kept that save alive. When I stopped the process on my computer that save was crashing again, even with DUI active. So you see, the mod itself could be only a half of the actual problem, if any at all.

 

If you have modding skills, please look into it. You obviously must be interested or you would not write such a lengthy post about it.

 

I was basically interested in it because you requested something based on speculations, though now I'll consider taking a look at Tytanis' files, I really need to get to know the new CK functions. And yeah, I've got modding skills, a year of playing around in GECK gives you some knowledge.

[Shantih]

A big mod like this is a very ambitious project and one that needs to be maintained. Sadly it seems the modder responsible for it is no longer available to support it (for now). Does it mean the mod is dead? We can't tell for sure as sometimes real life can get in the way.

 

My advice would be to track it in order to find out when an update will be available (if any).

 

Bear in mind that this mod was made pre-CK and looking at the description it seems to be a WIP (last version is 0.52 which means it is in an advanced stage and not yet version 1).

 

Assigning the blame to a mod is not necessarily the right move unless you can actually make a case and prove that the mod is breaking things which in turn can help patching it.

 

Basically what I'm trying to say is that if you want a more stable game experience you may be better off using smaller or less extensive mods or wait for a mod overhaul to be thoroughly tested with compatibility issues that are comprehensively documented (something that will take months of hard work at the very least).

 

The modder responsible for this mod is very ambitious but still managed to get many things done (without the CK). That alone is to be commended.

[Sunnie]

A new patch has gone into beta... one of the entries in the patch notes looks like something of interest to the OP...

 

BUG FIXES

 

Fixed occasional crashes when loading a save that relies on plugins/master files that no longer exist

Fixed issue where controls would become unresponsive while charging an enchanted weapon

Fixed issue where controls would occasionally become unresponsive while switching from third to first person while using the Arcane Enchanter

Fixed issue where controls would become unresponsive if activating a crafting station with autorun active

Fixed issue where keyboard would fail if Rename Item was selected before choosing the number of charges, while using Arcane Enchanter

Fixed several issues with remapping buttons while using an Xbox 360 controller

Fixed issue where pressing Escape button after fast traveling but before the loading would cause certain menus to stop working properly

 

This may or not help with the issue with Tytanis (I've heard this from quite a few of its users that try to remove it), but it may be worth trying out the beta patch.

Edited February 21, 2012 by Sunnie

[ilDuderoni]

@ Lisnpuppy

Thankees!

 

You do realize that ALL mods potentially carry these risks? That this is a known problem inherent to modding this engine since Morrowind's days? That calling for action *publicly* is essentially trolling the author? Save files are basically a very fragile linked list database and incorrect removal of a vital link such as a large overhaul mod is almost guaranteed to have consequences. Welcome to TES/Fallout gaming... chalk it up to experience and move on.

 

Personally, I find this appeal against Tytanis reprehensible. If you can substantiate your claims, report the mod through the appropriate method. If you can't, don't slander the mod author publicly...

 

Yes, I am simply doing this to troll. Now excuse me while I take off my sarcasm hat. :wallbash:

The mod has been reported through its appropriate method, it served as part incentive to post it here because that proved primarily ineffective.

 

Also, it is not completely public. Using the Mod Authors forum makes sure of that, since it's only available to people with Premium/Supporters and or Mod Authors. (I'm actually two of three, although my mod wasn't an actual plugin).

Also, by posting it here, I felt I made sure that the majority of responses were of people who knew what they were talking about and/or were up to par in one way or another.

 

The tidal wave of the normal bug forum exists for 80% out of bugs that could easily be solved. (wild assumption)

This means that an actual concerning bug like this doesn't survive longer then 2 hours there before its pushed away to page three or thirteen.

And bumping is against the Nexus rules, if I am not mistaken, so I couldn't do that either.

 

I ran into similar problems with NV Bounties and ended up with corrupt save files. After discussing it with the author I came to the same conclussions that Werne describes above. Essentially, I know it sucks but corrupted saves are a fact of life when heavily modding Bethesda games.. I have to agree with the two posters above me.

 

The best thing to do is learn from this experience and start using an alternative save game manager.

 

I'm about to go check wether Cipscis has made a savegame manager. Throughout all his savegame-handling mods, I have never ever regretted it. Save for the one time he also put in a Quickload button, but he was quick to remove that. (it caused enemies in the Quicksave to be invincible and not even collide with bullets. But they sure as hell still hit you.)

 

EDIT: Not yet, I will look into alternatives, but I somewhat know how CASM makes your savegames, and I'm not sure I'm comfortable using an alternative method I have less faith in.

 

SECOND EDIT: Is this one any good? I've always found executables handling savegames a suspicious thing.

 

Do you overwrite the save or do you create a new one each time you go to save? If you overwrite it you have a much higher chance of losing it, always save a new one. Always. Also turn off auto-saves and don't quick-save, all that can screw up your save in many ways.

 

Autosave has been disabled pretty early on the savegame.

Funny fact: Pressing Quicksave at the PRECISE moment you would get an Autosave (generally speaking, when exiting your house), will both cause a crash and corrupt (to the point it won't load) your quicksave, while the Autosave remains fully intact. I'd be tempted to say it's my "leet" skills, but frankly it's just my terrible, terrible habit.

 

I am for now using Quicksave, but experience from Oblivion on up taught me to never do so during combat or any high-processing event.

If Cipscis comes with a Skyrim equivalent to his manager, I'm downloading it in a heartbeat.

 

First of all, you need to ask yourself what did you do to protect it, before it died and you need to rescue it. Judging by this being your first introduction into Bethesda's wonderful world of bugs and glitches you have no previous experience, I can't blaim you for not knowing. But now you do know how to prevent this and you'll hopefully be more cautious next time. And by the way, there is no way to get your save back, at least not for now.

 

Not really, the first thing I learned when I started modding is that out of 50 bug reports, there will be 20 different bugs. It all depends on different mods users have active and their load order, in extreme cases the external programs cause problems but those are rare.

 

I have experienced bugs ever since Oblivion, which I heavily modded too. But the big one came when my load order reached D0 in Fallout 3.

I still have a picture of what happens. (nothing permanent, luckily).

 

Ever since then, I've kept to a system of minimum 3 saves, 10 with Cipscis' Manager. Always making sure I had one prior to installing a new mod, to make sure it ran fine. I actually refused making a new save until I found out the mod was functioning properly.

This made for many painful hours in FO3 where I hunted for the location of a weapon-mod drop. One overpowered Deathclaw and I'm set back an hour or two.

 

Along comes the fact that I, sadly, have never experienced a plugin bug that guarantees a CTD when selecting a menu. That seems to be a new bug entirely unique to Skyrim.

Back in the Gamebryo days, if your menu's were not up to shape (say, a missing menu file for DarnUI), the game simply would CTD at startup, while TES4Edit or FO3Edit would state nothing was wrong. My first experience with menu errors. But Skyrim is the first game so far that allows you to use the game up to the point you need to use the specific menu. This threw me off greatly.

 

Let's take a visual example to explain this:

 

Imagine having a big-ass rock on the floor (Tytanis). Now imagine having a small stone next to it (a small mod). What happens if I throw 20 other stones ( add more mods) on that one next to the rock? It piles up, and when you throw enough stones on that pile it will become bigger than the rock.

 

Now, if I throw that rock on a car (your savegame) it will make a mess. But if I tie those piled-up stones in a sack and throw them on the car it will make even more damage because they exceded the size and weight of the rock.

 

Now technically speaking, you have small mods, but if you combine the things they change they can modify the game into a larger extend than Tytanis alone. The size of one mod has no difference on the impact, the quantity of modified data from the combination does.

 

That still doesn't mean it's the fault of Tytanis, it might as well be that your savegame is damaged and Tytanis changes a variable which rectifies the issue. For example: When the corruped save problem occured for me on FO3 there was one mod that kept it still running, Darnified UI. My first thought was like yours, but I kept digging (cause I'm a nosy bastard) so I transfered my save onto my brother's computer and I installed all the mods I had, along with Darnified UI. When I loaded it, the game crashed immediately just like mine without DUI.

 

Then I've dug even deeper to find out what's causing the different behaviour, since the conditions are the same. And I found it, the reason for the difference was a background process, I had an aditional program running in the background which in combination with DUI kept that save alive. When I stopped the process on my computer that save was crashing again, even with DUI active. So you see, the mod itself could be only a half of the actual problem, if any at all.

 

I understand now. The simpleton I am (:P), I treated bugs at face value and believed that, because uninstalling Tytanis affected the General Stats screen, it was making changes to that menu.

Tytanis responded once in the comments section, asking if I was actually using a legal copy of Skyrim. I invited him to add me on Steam to prove it, but he never got back to me on that. Adding to my concern.

 

So what it comes down to is, the only thing keeping my savegame from crashing on General Stats is an outdated mod I actually want to get rid of, because its outdated.

I'm not stupid :P Tytanis-TUM was a great overhaul and was pretty much to Skyrim modding months ago as was sliced bread to the first lunch after its invention.

 

I'm willing to be slandered for being a troll by other members if it'll lead to someone finally taking a look into Tytanis. If it proves the mod's innocence? Then it'll be official, and we can refer to this 'investigation', for lack of a better word, and never have to do this again.

 

I remain with one question though: How can I prevent/detect savegame corruption? As much as I appreciate, and even believe, your theory, I can't think of a way to really prove it.

In fact, IF I could prove it, it would mean there might be a way to correct it. So it might pay to brainstorm further.

You do claim to have run with 600 mods at the same time, which is a noteable feat. Surely you managed to keep that all stable in one way or another?

 

My advice would be to track it in order to find out when an update will be available (if any).

No two days go by without me taking a glance at the Tytanis-TUM mod page. Saying it here makes me feel like I'm obsessed.

Frankly, even though I say out loud that Tytanis-TUM would have to fight the bad rep when trying to revive the mod, I'd still get the update in a heartbeat. :sweat:

 

A new patch has gone into beta... one of the entries in the patch notes looks like something of interest to the OP...

 

This may or not help with the issue with Tytanis (I've heard this from quite a few of its users that try to remove it), but it may be worth trying out the beta patch.

 

That does sound somewhat hopeful, but I fear, with what I've learned that you can read above, I think it's no longer a master dependency, but simply savegame data corrupted that Tytanis was actually holding together afterall.

 

I owe the guy an apology...

Tell you what, if he goes active again, I'll apologize :P

 

In the end, I still got something out of it!

The issue has gotten attention and a very viable theory has surfaced, I've learned something useful, and I'm no longer hating on TUM.

Thanks to everyone who contributed, that includes you Werne.

Edited February 21, 2012 by RJ the Shadow