Cobra847

Latest for a hotfix is likely next week. More info when we converse with ED further! Sorry for the wait.

Sorry for this issue- it's just been fixed today and will ship with any upcoming hotfix

This model is slated to be entirely replaced/remodeled exactly for this reason, likewise with a few of the others. But good feedback and well spotted!

Sure! Here's the current changelog; DCS F-14 Tomcat by Heatblur Simulations NEW: Added DCS VOIP functionality to AN/ARC-159 and AN/ARC-182. Changed ICS default setting to always cold mic on spawn. Overhauled all night lighting in F-14A and -B cockpits for DCS linear space gamma sampling. Floodlights are now operational again in the F-14B cockpit. Forrestal: Adjusted LSO platform view. Forrestal: Tie-downs now render proper cavity map. Fixed potentially long load times due to TACAN initialization. Fix typo which accidentally removed one AIM-9L from this F-14A-135-GR predefined payload: AIM-54A-MK60x1, AIM-7Fx1, AIM-9Lx2, XTx2, Mk-82x2. Adjusted integrated stab trim for flap and DLC operation. Adjusted gear and speedbrake drag. Adjusted flap pitching moment. Adjusted F110 fuel flow for mid-power settings. Adjusted lift while in ground effect. Added VF1 Wolfpack NK100-103 skins by Yae Sakura (thank you!).

Generally the IPD will scale things up or down because it simulates the spacing between your eyes. If one cockpit looks too big or too small with the same IPD as your natural pupillary distance, it means that one or more cockpits are mismodeled; or you think something in reality is bigger/smaller than it actually is (this is frequent ) The Eurofighter is a newer jet; as such it will have a different character than the Viggen or the F-14 and thus may be naturally easier to use in VR; however it will be chock full of the requisite Heatblur texturing quality and mesh accuracy.

Once again, would like to thank everyone for the great feedback and input. The next patch will see little for the Forrestal as we've been leaning heavily towards the Viggen, but we're aiming to ship a larger chunk of changes and fixes in January.

Hi! You need to manually edit the lua. Unfortunately there is not a fourth state we can set. If you open the CV-59.lua; you will see the lighting lines that define which lights turn on in each state. Simply change one of the states to include the island lighting.

There are plenty of F-14 / Forrestal fixes ready / in the pipeline; they just weren't ready for this patch. We just launched a gigantic F-14 patch on October 28th. It's not really realistic to ship changes every single patch (unfortunately). We need time to get feedback (or plan) -> develop -> test -> QA -> deliver. ED sets the patch schedule, sometimes we are not comfortable shipping anything for a specific patch. That said we had a few critical hotfix items (F-14 cockpit floodlights) that mistakenly were not included by us, they'll be available in the next hotfix instead.

To speak in more concrete terms, generally what to expect from this upcoming update is a large revision of either simplistically implemented, non functioning or simply buggy systems/issues in general. Everything from some weapons being fire-able from the ground, to the radar stick animations and it now functioning as a fluid axis, to gear damage not working, to systems such as oxygen and pressurization being incomplete - and finally to more chunky feature additions (cockpit graphical improvements and new soundset, etc). It should end up being a 60-70 item changelog at the minimum and will hopefully bridge the gap between our current standards and the ones we had at the time the Viggen released. We've roadmapped out an additional significant chunk of development resources just after, to iterate on your feedback once shipped to polish away what we'll roughen up (inevitably!) in addition to this.

This is the mid November patch that we initially targeted to ship Viggen changes with (it was originally scheduled for the 14th). It's what I was referencing in my previous post on us moving to the next one instead as the massive F-14 patch took too much out of us to realistically make it. I can understand being frustrated that the Viggen hasn't seen major changes for a while, but not shipping changes with today's update is exactly what I announced in this post. I'm not sure how I can be clearer. I know having to wait is frustrating; it is for us too, but we're trying to make this a great one. FWIW; our entire staff is currently working on the Viggen and we still expect to complete this patch by late November.

It is indeed there. We've tuned it to a large extent, so perhaps it feels less severe now.

Thanks to everyone for the great feedback! Re the darkness of the key grey; I'm pretty confident we have the right albedo value presently. Of note is that we master all of our artwork for a default tonemapper gamma of 2.2.

Hey! Actually- the tilly we added now is the wrong model (just painted yellow) temporarily. The changelog should have reflected. The real NS-60 Tilly will be added in the next update, and then it will be placeable (or default near the island). So to answer your question; the tugs and forklifts currently clutter that area because we are waiting to add the proper NS60.

Hey guys, The crunch on the upcoming F-14 release was a bit heavier and more intense than we expected and the entire schedule was somewhat thrown off due to the one week delay (so we've spent additional time on F-14 related hotfixes). This might mean the Viggen patch will arrive towards late November rather than the middle as initially envisioned. Generally, we want to pack it as full as we can, so we can clear most of our remaining todo's and focus on any smaller things that may still remain towards end of year - apologies for this slip. JESTER Lantirn and the Forrestal have been a pair of really big milestones for our team, and we hope to match that level of effort with the next Viggen update - both in terms of new features but equally so in QoL and bug-fixing. We're displeased with it's current state and hope to make it a great one and will be working hard over the next 4 weeks to deliver.

Yes, we love adding unrealistic, reputation damaging features that cost us a lot of time and money to research, implement, test and ship. (and bonus: argue about on the forum!)-- just to make our F-14 better than the competition. /s.

uh, the entire throttle should be making sounds already, including detents. It has since release.

You guys are making it REALLY hard not to buy a 3d printer.

I concur entirely actually. Naturally, this sometimes happens because of changing lives, priorities or focus areas for various people, which means their visibility here will ebb and flow to some extent. The backstop is always that the work gets done; and the growth and professionalization of our team ensures this. It's easy to lean on the Valve model of communicating at least partially through updates, rather than talking about them a lot ahead of time, but the latter can frequently lead to missed deadlines and expectations. We need to make sure that we don't leave what made you all trust and enjoy our work here, so making sure that we communicate more here needs to be a priority even though we are strapped for time. I am filtering this feedback back to the team, for what it's worth, and we will be discussing these topics soonest and take remedial action wherever possible.

Absolutely, that's our feeling too; and I'll be restructuring the teams in a way that will allow for more dynamic allocation of resources to the Viggen on a consistent basis once we get these major features out and can focus on shoring up any new issues that do crop up with every change- regardless whether they're due to our changes or DCS. I'm not a fan of minor issues building up to the point where we need to make major patches just to fix some of them. Keep in mind that every issue that needs to be fixed is an investment of time, effort and energy for us that we could indeed spend elsewhere; so minimizing having to go back and change things constantly is of utmost importance, not to mention of course we'd like it to be that way too for everyone's benefit.

the DCS engine changed the way they sample alphas again (gamma wise). We'll need to tweak and adjust all of this again unfortunately.

Keep in mind- bugs (especially new ones, like the crashing) are rather separate from whether something is EA or not. New bugs and issues will occur regardless of the marketing tag glued to the box. It sucks; but it's just the way it is with a moving platform and especially if we do indeed make changes/additions so please do keep in mind that this is something that will continue in the future. Feature wise, we've certainly exited the typical EA criteria some time ago, though the exact definition of that is perhaps usually quite ambiguous. In hindsight, it's probably been a mistake to have kept the tag and to keep adding features that have added to our criteria. The PBR overhaul is an excellent example of something that is now considered a flaw, bug and error, when it is in fact simply an improvement beyond the original scope of the product (again, as a result of a moving platform!) and is now an EA exit criteria. @Desert Fox Fair enough; though if I had the time; I could copy and paste in all of the Viggen's changelogs and, especially, major additions made during an equal period of time in this thread. Credit where credit is due, I hope. We've added a lot of bonus features and changes into the Viggen since release, with plenty not being on the original roadmap. I am not ashamed of the Viggen nor the effort invested, though there is certainly room to do a lot better. With the major patch due next, we'll also be able to focus more on our own wants and desires for the Viggen (there are lots!) while worrying less about what is an EA exit criteria issue/feature. As for the general topic of this thread; this has been partially mentioned on the forum elsewhere, but we've partitioned our two next releases as follows: Oct 14th: Major F-14 Patch, including JESTER Lantirn, Forrestal class and other major improvements. Nov 14th: Major AJS-37 Patch, including at minimum: PBR overhaul, Cockpit improvement/overhaul, sound set(s), tactical numbering and various other stuff/bugs (radar performance, a few system fixes, et al.) (and ideally, depending on how we feel, EA exit) While most of the Viggen part is nearing completion, we need the breathing room to allow for any hotfixing which inevitably bubbles to the surface post each major patch. Don't read into the order above as another attempt to deprioritize the Viggen.

Sorry you feel that way, I do not condone our team dismissing anything, ever, as that is not our way. We do appreciate feedback, always! You are strongly mischaracterizing why the change was made. It was the recollection of maintainers, who have been exceptional in their knowledge previous to this, that led to the change. We have revisited the issue and will revise based on further feedback for Victory. You must certainly understand how much undocumented detail is in the F-14. We cannot dismiss anecdotal evidence from experts who have replaced every bolt on the real jet. Mistakes happen, we didn't spend development resources for the fun of it. We have better things to spend them on, trust me. We will continue to trust our SMEs however and we will consider future mistakes, that are bound to happen, as a fact of life and development. Thanks for the feedback! It is appreciated, don't take the above to mean any different

Sorry, three fixes in particular were indeed cutoff from this build and erroneously remained in the changelog. They are; Ejection seat safety levers will now animate properly in exterior view and mirrors Fixed hole in rear of canopy frame when canopy open or jettisoned Fixed broken/artifacted normal maps on RIO front panel base They will be in the next minor update. Re the flaps lever; we will actually be reverting this change. This was a case of SME feedback causing us to change it, but based on further SME feedback, it was indeed correct as it was.

@Coxy_99could these be RWR callouts? Jester will callout missiles if they're seen on the RWR.

TID brightness will increase in the next patch.