IronMike

are you sure that the wingsweep handle is in the spider detent and down? if it is not, the cover will not close. Tried on my side as well and works as intended.

We will do that, once we are done with the Jester overhaul. This will still take a bit unfortunately. But as things may likely still change, doing it now and changing it again later would break your profiles yet again, hence we opt to wait with that for now.

Just gave it a quick try, worked as intended here. "Hey what are you doing" is an indication that the plane is moving during ground crew ops, like air, elec power, refuel or rearm. Are you sure the carrier is not turning maybe? On what map did you try? Mind you that even overcast presets can have very bright, almost sunny spots. The shadows projecting onto the aircraft seems to be a DCS wide issue, at least I remember seeing some reports of that in general. I just tried it quickly, and the screenshots below is the difference I see between overcast and sunshine weather. I also tried the hornet quickly, and the difference is very similar, albeit the hornet pit looks a bit darker in general in both weather conditions, except when illuminated directly by the sun.

Thank you!

Some reported that you have to press twice. The option not working as preselect is a bug currently, and the double press for the button is likely a result from that. We initially had it fixed, but for some reason it broke again after the upload. Should be fixed in the next patch. Our apologies.

Do you have a log, a track even and could you share the mission please? Also describe please when and how the crash happens, is it just by turning Lantirn on, or when designating, lasing or dropping a bomb, before or on impact etc etc. Also can you reproduce it, or was it a one off? Thank you.

Unfortunately the extra animations, like hand signals, etc were not really doable without IK, but we intend to expand on that in the future as feasible. The triplicate Top Gun liveries are a bug in the repo, and will get cleaned out.

Our apologies, but we really do not. Currently there is a bug in the repo which triplicates the Top Gun livery for some reason, which we need to clean out, but the rest is as intended. It is also not true, I just checked: all other liveries combined are 33.5 GB (rounded) vs 12GB in the Tomcat. Disc space is incredibly cheap nowadays, and having a module within 15Gb is nothing unusual, in fact between 10 and 15 GB is normal industry standard in flight sims (DCS is actually really on the lower end of the spectrum, but not the norm). We cannot throttle development or lower quality or offer less choice for "GPUs that are lacking VRAM". If you really think that liveries are causing crashes, then you can always delete them from the coremods folder except one for the A and B, albeit you will have to do it after each update.

Can you please post your system specs and game settings? Also page file size please. We want to know as much as possible so we have a chance to reproduce it as close to your circumstances as possible. So far we had issues reproducing the freezes at all. Thank you!

This is a bug, we fixed it before uploading but for some reason it is back again. We'll fix it again.

Thank you!

Hi Santa! I need a 4090ti please, k, thanks! You are the best.

Thanks for the feedback. Well, I hope Santa brings you some nice things for a new PC then.

Great to hear. Missiles intercepting missiles is ED side.

Could you show a screenshot, video or post a short track even please? Thank you. Does anyone else experience this in VR? I do not have VR myself, but it looks fine for me in non VR (which ofc is not much to say).

With changes brought about in 2.8 our testers discovered that the parking brake issue is now fixed. Please be so kind and try again if this is also the case for you, mind you this was not an active fix on our part but discovered during testing. What exactly led to this lucky fix, we cannot say unfortunately.

Dear all, unfortunately this patch around there is no real changelog for the Viggen. Our main focus was on updating it to work with the 2.8 update, which still required substantial input from our side. We would still like to kindly ask you for your feedback, as such major version progressions always can bring issues with them, although we hope that everything should work as it did during testing for 2.8. Thank you! To be noted: with 2.8 it seems that the parking brake issues has been fixed. This was not an active fix on our part, but came about due to the changes in 2.8 and is a positive by-product our testers discovered. If you experienced any issues with the parking brake + rudder pedals, please try if it now works for you as well. Thank you! In the meantime we have been focusing on updating the damage model of the Viggen in the background, which we hope we can bring to you the coming patch, including more other fixes and updates of course. Thank you all for your very kind patience.

Thank you for the feedback, and my apologies for being less present on the Viggen forums, it certainly is not for wanting to be. It is however also very dependent on updates, and the F14 received a major update which requires my presence much more currently. Likely, as you know, I am also present around Viggen patches or major updates. Same as I am not answering daily on Tomcat issues when there is no update/patch/new feature around (though we generally of course still check on all our subforums daily, even if we do not reply to every post). Naturally newer modules receive sometimes more updates, simply because we are further along with the Viggen than we are with the F-14 for example - it simply is much more complete (even with a many items remaining until we call it fully released of course). This does not mean we have abandoned an older module, or do not have the remaining and still outstanding issues with the Viggen on our screen or even care less about it, but sometimes we need to prioritize, as we cannot divide ourselves in half. Just like we prioritized for the Tomcat now, next month we will prioritize the Viggen, and the Tomcat will receive less attention. But as time goes, newer modules will always require by default more attention than older modules, which does not mean that we cherish them more, or care less about older modules. It is the natural course of things and ideally, bug fixes should become less and less over time the older a module gets, which also means it will see less updates in time (and that is again not to say that we are unaware of the many remaining issues, we are). At the same time the progress made in newer modules, benefits older modules in return, as we can over time continue to improve them and modernize at least parts of the technologies that are underlying the various features. I asked a while ago to be so kind to ping me, if something arises, and for a while this worked and I received pings and I hope always answered, but lately I have not seen any. We also specifically brought several outstanding members of the Viggen community on the test team, which help us even more to keep a focus on the Viggen. Lastly please understand that not having a changelog devoted to bug fixing, does not mean that no work has been done on updating the Viggen. It has. 2.8 required substantial input from our side to make everything work, but that just does not fit into a changelog, it is coding related, not feature or bug related. It also does not mean that our testers paid no attention to it (they did), or we are not discussing Viggen issues on an ongoing (almost daily) basis (we do). I've also put up a feedback thread for this patch, as with such major version progressions there can always be new issues, although we luckily did not find anything during testing which we were not able to fix prior to the update. Thank you all for your very kind patience.

Unfortunately with it not being supported anymore that was bound to happen sooner or later. There is always the option to use custom profiles with voice attack still though.

We're sorry to hear that, but we cannot support 3rd party applications (especially if they themselves are not supported anymore), or stop updating ourselves so they may or may not break. That's really not on us.

Dear all, as always we kindly like to ask you for your feedback for the current patch. Thank you! For a more detailed read up on the patch please visit this link: https://forum.dcs.world/topic/311034-f-14-v28-jamming-jester-and-headless-bodies/ Full Changelog: DCS: F-14 Tomcat by Heatblur Simulations Oct 26th 2022 NEW: Introduced Pilot and RIO body for front and back cockpit. NEW: Added jammer detection and tracking functionality in the AWG-9, which adds amongst other features: Noise jammers will now prevent AWG-9 from ascertaining range or range-rate from a target. DDD will show noise returns over the range axis at jammer azimuth in pulse search. DDD will show jamming intensity trace overlay in pulse doppler modes. TID will display jamming strobe in TWS and RWS modes. TID jamming strobe can be toggled via Jam Strobe button below TID. Jam strobes can be shared over Link-4C fighter to fighter datalink, allowing for eyeballed triangulation of actual jammer position. TID angle symbol is hookable. PSTT or PDSTT on jamming target leads JAT (Jam Angle Track). STT-ed target transitioning to jamming outside of burnthrough automatically switches to JAT submode. In STT-JAT submodes both AIM-7 and AIM-54 can employed in HOJ (home on jam). Added jamming targets to JESTER STT options. NEW: Added new list of set commands for JESTER to be used in the Mission Editor. 10017 to 10033 are new. For a full list visit this post here. Reverted AIM-54 loft to state before looping hotfix to revert exceptionally poor performance (by ED). Fixed forward rendering for canopy sealant - will now not appear shadowed at odd angles anymore. Screens and other glass surfaces will now reflect sunlight again. Added non-gfx external args to check the status of JESTER tracking air targets (to be used with scripts): 1026: tracked predefined target; 0.01 - 0.99, same as command 10024; 0.0 - no predefined target tracked. 1027: range to predefined target (only when tracking); 0.xxx - three digits of distance to tracked predefined target in NM. Potential fix for mission freeze including F-14 AI. Made LANTIRN available as laser designator for the AI. Fixed ALT HOLD not working >36k AGL. Fixed flashbang-like sun glare on internal canopy glass. Fixed MiG-23s not taking off in PG Flogger Faceoff Mission. Adjusted all Quickstart BVR missions for new AIM-54s. Removed instances of “color” shader in cockpit due to deprecation Minor cockpit optimizations - fixed some visibility arguments not triggering LoD changes

Ah, now it makes more sense indeed. Apologies for misunderstanding.

Yeah it has been moved once more unfortunately.

I don't see why it would, the aim54 works fine below 30nm as well, when employed correctly. The rest simply means dealing with the same issue as the other guys. It is simply a tactical obstacle to work around, that is all. I am personally not a big fan of these kind of absolute (somewhat panicking) statements, there is always a way to make it work. Also not all targets are jamming, and HOJ shots will still be a threat. On top of that this is a very much lonewolf based thinking. With 2 or more guys in the fold, a lot more is possible. Triangulating jammers, boxing, etc etc...

Best to wait till after today's patch to compare and see.