Neuse

I have this in MP once in a while.

Are you still looking in to the damage model or is this final? From MP experience with and against the F14 i have the feeling it often takes more damage then it should. Other people on our MP server stated aswell that the F14 took two missles and still was able too rtb. From my experience flying it this seems to be often the case that i get hit but no crucial systems stop working, no fuel bleeding eg....i fell kinda tanky^^ Thought i dont know how this was in real life, so it just might be that way.

Im also getting random stutters when looking around that i dont get in other planes. (4k, 2080ti) Nothing i can reproduce regularly thought...also not to much.

Is there any possibility to use the weapon in MP? In the Viggen alot of possibilitys were introduced by using the map and kneeboard to programm weapons/waypoints. It seems like the perfect way to use for the sea eagle. Would be nice so it would get some more use in MP.

I´d doubt those values are for tanker sized objects. Might be more for fighters. Try it with a helicopter if its still 20 it might be buggy.

Yeah CTD still happen. Just had one when locking at target in a ACM. Jester Said Target 8 nm and then crash. No log file generated no entry in the standard log.

expectations are expectations...mine might be high...yours might be low. To say if realistic or not...you might have the insight in ED numbers and working conditions...i havent. So you could be right and they simply dont have the people to fix things faster or the contracts to work weekend shifts after big releases. I as a customer see a not working expensive product, i read the fix was out emediatly, i get no communication by ED that there are problems they are working on that would delay a fix. Then i get a happy weekend newsletter saying everything is fine. Thats where i feel like they are making jokes on us. And this is just one of many things like visibility, performance, introducing new bugs with every patch that annoys me. It´s ok you think this is the way you should communicate with your customers....i dont. Thats what i wanted to tell them, in a tone that should say, i am not happy with how things go in you support. I still dont see an insult or bad manners. It´s a forum, its there to express opinions, i didn´t use any bad language (at least from my little school english).

Surely having high expactations isn´t a sign of bad manners and it should come to your mind that not everyone here is a native english speaker and formulations seem more or less insulting than they are ment to be. Please go ahead and delete the thread (i cant) if in your interpretation something is insulting to anyone, thats not been my attention. And if all the excuses you try to find for them are true then there is still a lack in communication towards the customer of the modules. They even announced a "weekend news" claiming the CTD bug was fixed...

Already testing :-) still it should be mentioned that apparently it wasnt HB´s fault.

This is not about a beta having bugs....this is about the developer HB fixing bugs but not having the ability to deliver the patch until ED releases it. Just saying the way a 3rd party developer can deliver updates seem lackluster. And of course ED has to review the changes, but after the release of the biggest, hyped and loved product that supports their sim a crucial fix that is ready should be applied emediatly and not after 5 days.

Thx for reply. Opend a thread for ED asking why they delay fixes on purpouse although day are available for days. If a developer like hb is working hard on fixing issues fast then ED has some work to do in their update policy.

After the recent patch the CTD in the F14 continued. HB statet one day after the patch (Thursday) that they found the problem and would deliver the fix to you ED. Yet there is no hotfix till monday. Why are you holding back such crucial fixes for gamebreaking issues when they are available. If you have a new release there must be the possibility for the developer to release hotfixes on a daylie basis till the worst issues are done.

Any new on this? Why is there no hotfix for days? It´s CTD all the time...isolated to the tomcat.

3-4 of this today: 2019-03-31 20:48:54.457 WARNING LOG: 1 duplicate message(s) skipped. 2019-03-31 20:48:54.457 ERROR SOUND: invalid source_params(woLA-16785959:aircrafts\engines\f110afterburnerrearclose): gain

2019-03-31 09:35:55.375 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:damage\structuralgroan): gain 2019-03-31 09:35:55.413 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_impact): gain 2019-03-31 09:35:55.413 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_missileimpact): gain same again....just in heavy g pulls

Anything new on this?` Just had to more ctd in instant action, when engaged and going high g 2019-03-29 10:28:42.316 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_impact): gain 2019-03-29 10:28:42.316 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_missileimpact): gain 2019-03-29 10:37:20.390 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:damage\structuralgroan): gain 2019-03-29 10:37:20.486 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_impact): gain 2019-03-29 10:37:20.486 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_missileimpact): gain

Same here...already reported this last patch. Dont know why its so hard to fix

Yeah always doing after patch....reinstalled the whole module now...well see

Same here...opened a thread already but just in case: I was happy i could finally go and enjoy the F14 in MP after the patch but no... Crashing as usual in combat in MP, no crash log last lines of normal log directly with the crash: 2019-03-27 15:22:31.110 ERROR WORLDGENERAL: waParts f-14b_damageparts_stabilizer (//models/f-14b_damageparts_stabilizer.edm): box is invalid, skip render 2019-03-27 15:22:31.128 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_impact): gain 2019-03-27 15:22:31.130 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_missileimpact): gain Pls hotfix this...not wanna wait another week.

Guys report this in another thread thats a different issue. Im talking about a simplet ctd like before the patch...no freezes or sth.

I was happy i could finally go and enjoy the F14 in MP after the patch but no... Crashing as usual in combat in MP, no crash log last lines of normal log directly with the crash: 2019-03-27 15:22:31.110 ERROR WORLDGENERAL: waParts f-14b_damageparts_stabilizer (//models/f-14b_damageparts_stabilizer.edm): box is invalid, skip render 2019-03-27 15:22:31.128 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_impact): gain 2019-03-27 15:22:31.130 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:foley\damage_missileimpact): gain Pls hotfix this...not wanna wait another week.

I Hope they bring some improvements to Jester today. Doesnt feel like an ai atm.

Since the last update my mouse cursor is wider then high{the cross when over buttons) Playing in 4k. Nothing else is stretched

still happens after update

Still persisting after update