Bold launchers and flak guns now can be damaged and destroyed ... :)

It's interesting that this only works when destroyable=Yes in ubold definition in zone.cfg file. It's the same for rudders and dive planes... So far , the only way to make some equipment unusable is to remove their 3D object from the game... Default Destructable=No value doesn't do anything...

I have just discovered that most of added damage isn't savable if equipment is not compleatlly destroyed(rudders, propelers,etc. )...(FU ubisoft:shifty:)

Now, can this be solved or everything is futile ?:/\\!!

...and bigger problem, damage level for every individual compartment also isn't savable so only thing you need to do if flooding is detected is to save and reload the game...This is so disappointing.:wah:

The problem is ActiveUserPlayerUnits.upc file in the save folder...But why damage for diesels,electric engines and batteries is properly saved and for other equipment is not , i really don't have a clue...

I think there's just one simple answer to your questions: either damage values are not read correctly from the savefile or, more likely, they are not stored at all. The same happens with AI units' damage and with their odnance loadouts: exit the game, or move away from them beyond the "SH5 rendered world", and the above values are reset. :-?

Unfortunately there's no way we can fix these flaws. Atm our only chance to see them ironed out, if ever possible, is TDW to address them :yep:

That is the case ... here's entry from ActiveUserPlayerUnits.upc for engines...

And this is for propellers

So damage isn't stored at all...What's going on with TDW, is hi still around?

Well at least there are entries in the savefiles for the damage levels of all the equiments/compartments, not only the ones whose damage is getting stored correctly.

Try doing this: save a game, update manually damage levels in its upc file, and reload it. Hopefully the game will read damage levels though not storing them. :up:

yes, give him time and he will pop up at some time :03:

When he disappeared last year (last Autumn), he came back only after Christmas :)..

At least we are prepared now :D

Yesssss!, UZO and periscopes are finally destructible ! Although, clicking on UZO station after it's been destroyed will cause CTD sometimes but i can live with that... I was experimenting with wrong periscopes... I should use wire from the beginning...:) Also, i have an idea how to make some compromises because of the save problem. For example, one rudder will be 100% more durable then the other. That way, one will be destroyed with single good shot so if you do save, on next reload you'll have sub with just single rudder. This will affect sub's turn capability...Same for propelers and dive planes...

:yeah:

Have you set the UZO as destructible? Is it physically removed from the boat when its HP's reach 0? I wonder why CTD's only happen with it, and not with periscopes :hmmm:

Just as I said :03:

If I have understood properly, damage levels of some equipments are not saved, unless they get destroyed, in which case they are absent from the bot the next time a save game is reloaded. Is it so?

In any case I don't see your point about giving similar equipments different HPs. How is it going to help? Imo, while we wait for a proper fix, it is better leaving them as they are :)

Yes and Yes...It's something about camera controller. Periscopes are set to destrutable=No and only movement up and down is unavailable ,although you can still look through them and move view but they are pinned to down possition, ext.obj. controller is disabled , i think. When set UZO to destrutable=No nothing happens. I will check some other possibilities also... So far i think that only way to make UZO unusable is to disable his camera contr. Works just fine if you don't hit click spot where UZO were...



Yes...

For now there are two possibilities ... Let's say you have two rudders with 50 HP...One direct hit will leave both of them with ~20HP and their efficiency will be very reduced and sub will be very slow in turns. You escape with no other damage and when you reload game next time, boom, you have perfectly good rudders with no damage at all.Not good...

Other solution, one rudder 50HP, other 25HP...Direct hit will immediately destroy rudder with 25HP . You manage to escape without other hits and when you next time save and reload game you will have sub with just one perfectly good rudder. This way you will have consequences from rudder hit even after reload... See my point now?

It makes sense: not being directly attached to its respective 3d model, but to a dummy bone in a second file, the UZO cam controller can't be damaged/destroyed. Try this then:

- open Uboot_Sensors.GR2 in Goblin Editor;
- merge Uboot_Sensors.zon;
- merge cameras.GR2 (path: data\Library);
- select the 3d UZO(s) and enable the Damage Editor;
- in the "Object linked to" section, select _Dummy_Cam_UZO;
- save the zon file.

In this way, the dummy UZO bone (owner of the camera controller), should be destroyed when the 3d UZO is destroyed. Alternatively, you could assign a damage controller (with sphere and box) directly to the dummy UZO, but I doubt it would work. :hmm2:

In other words, you want to balance an oddity by introducing another oddity. :yep:

In your example the trick you are suggesting seems to work, but in practice there would be many eveniences of it not preventing damaged equipment from being magically fixed after a game reload. Yet, we would always have to live with one propeller, dive plane, etc. whose HPs are set too high/too low. :hmm2:

Something like that...:) There is a third possibility also ...To disable game save...:D

Just kidding...Seriously, the main problem is individual compartment's HP which also cant be saved until HP0, but maybe we shouldn't talk about this, so that people couldn't hear and exploit this "feature"... :)

I hope you don't want to split compartments as well, and give each half a different level of HP :o

:haha:
sometimes censorship is the best remedy!

P.S: let me know if you decide to test the setting I have suggested about the UZO.

I tried this and looks like it's the same in both cases(with dummy bone or 3d object)...Actually, CTD will happen only after game is saved-reloaded, before that, if you click on UZO, camera will go crazy and it's difficult to return to captain view, sometimes movements are disabled also. If entire object is removed(base + binoculars) teleport function is disabled...So far best combination is to avoid clicking on uzo after it's been destroyed (removed, nice visual indication of damage). Also, there is a good way of returning to normal views if you click on UZO after all, you need to go to save-load meny ,save game and return to game without reloading...interesting