F-14 A/B feature follow-up, wish list and beyond

[JupiterJoe]

@NaquaiiWith all due respect, there is no way for the community on this forum to know if a bug is already being tracked or not.  There are hundreds (perhaps thousands) of disparate threads, many relating to the same bugs in some circumstances. On more than one occasion there have been cases where a long-standing bug has again been brought to a Developer's attention, only to have them say 'Oops, our bad, we forgot all about that.'.  To say 'if it's not acknowledged here it's acknowledged on Discord'; and vice-versa, is a feedback loop from which there is no escape.

As an example, I posted two bugs on July 4th and there's been no acknowledgement whether they're already tracked, or if it's the first time they're being brought to HB's attention:

 As I've stated before, our frustration is what has organically brought threads like this into being.  I ask HB to reconsider their policy of not sharing a current list of tracked bugs with the community.  After all, the bug list featured at the beginning of this thread is not very long.  In the building trade it would be referred to as a Snag List.

[Naquaii]

9 minutes ago, JupiterJoe said:

@NaquaiiWith all due respect, there is no way for the community on this forum to know if a bug is already being tracked or not.  There are hundreds (perhaps thousands) of disparate threads, many relating to the same bugs in some circumstances. On more than one occasion there have been cases where a long-standing bug has again been brought to a Developer's attention, only to have them say 'Oops, our bad, we forgot all about that.'.  To say 'if it's not acknowledged here it's acknowledged on Discord'; and vice-versa, is a feedback loop from which there is no escape.

As an example, I posted two bugs on July 4th and there's been no acknowledgement whether they're already tracked, or if it's the first time they're being brought to HB's attention:

 As I've stated before, our frustration is what has organically brought threads like this into being.  I ask HB to reconsider their policy of not sharing a current list of tracked bugs with the community.  After all, the bug list featured at the beginning of this thread is not very long.  In the building trade it would be referred to as a Snag List.

And with all due respect we're also not asking you as users to keep track of this. We're not asking you to look through all the bug reports, if you at a first glance can't find it then report it. No-ones going to blame anyone for a double report, if it is then it is so, no big deal.

I know Cobra and Ironmike have plans for something like this so it might happen. But for now it's not public and you're just going to have to trust us that we keep track of the reports. Making your own list won't change this. Like I said you're free to do so but don't expect us to use it over our own lists and adding it as an abstraction layer between the users and us is not a good idea.

Edited July 18, 2024 by Naquaii

[scommander2]

As @Naquaii suggestion, our list is just for our own reference. 

It is public for all users who can post any input freely and I have no issue to continue bookkeeping the user's input into our list, but the updates are stayed at the DCS forum only.

However, anyone enters the bug/feedback at discord and update me the link or any reference, I am glad to update our list.  Meanwhile, I have stopped compiling and entering at discord due to @Naquaii recommendation.

Thanks.

 

 

 

[scommander2]

Would like to share the feedback from @Naquaii (thanks) about the AIM-54 implementation (sorry kind of late for sharing):

It seems to me that it makes sense that ED hosts the platform included all kinds of missiles and it will be better to have ED to take over. 

Any suggestion?  Thanks.

 

Edited July 19, 2024 by scommander2

[draconus]

 

7 hours ago, scommander2 said:

AIM-54 implementation

Interestingly Cobra moved it recently on HB Trello as delivered with 2.9.

https://trello.com/b/HsMiJggJ/heatblur-public-roadmap

[scommander2]

38 minutes ago, draconus said:

Interestingly Cobra moved it recently on HB Trello as delivered with 2.9.

Thanks....

Wait... "AIM-54 - Missile API and Control Schema" is not listed in @IronMike July release.

 

[scommander2]

Shared the YouTube video that related to the HB works (unconfirmed) at 6:42:

 

 

Edited August 1, 2024 by scommander2

[royphsle]

Hi HB, can you fix the stopwatch in the Tomcat so it doesn't run when you start in the cockpit? And fix the master/arm cover toggle binding? Close the cover works but not lifting it up.     

[draconus]

9 hours ago, royphsle said:

Hi HB, can you fix the stopwatch in the Tomcat so it doesn't run when you start in the cockpit? And fix the master/arm cover toggle binding? Close the cover works but not lifting it up.     

Here's the bugs&problems subforum to make a report:

https://forum.dcs.world/forum/535-bugs-and-problems/

[royphsle]

And what about the master gen switches? Should it always be in the norm position, or turned off during the shut down sequence? Anyway, I think HB should make bindings for the master gen switches. 

[scommander2]

On 7/31/2024 at 4:34 PM, royphsle said:

And fix the master/arm cover toggle binding? Close the cover works but not lifting it up.     

The toggle does not work indeed and not sure what it is for.  But, the master arm cover open/close (2-position on/off switch) does work with my TM HOTAS:

Does it mean that we need to fix the input lua to make the same bind the toggle same as cover open/close (2pos)? Or, we do need the toggle since we have 2pos already?

 

[scommander2]

Checked "..\Mods\aircraft\F14\Input\F-14B-Pilot\Keyboard\default.lua"

{ down=device_commands.WEAP_Master_Arm_Cover, cockpit_device_id=devices.WEAPONS, value_down=-1.0, name=_('Master arm cover toggle'), category=_('ACM Panel')},

It seems that the toggle function for the master arm cover is just  for close (down=...) only not for open (no defined for open=...)

[scommander2]

On 7/31/2024 at 4:34 PM, royphsle said:

the stopwatch in the Tomcat so it doesn't run when you start in the cockpit

What kind of "start"? Coldstart? or... tried it in the pilot seat:

 

 

 

 

[royphsle]

12 hours ago, scommander2 said:

Checked "..\Mods\aircraft\F14\Input\F-14B-Pilot\Keyboard\default.lua"

{ down=device_commands.WEAP_Master_Arm_Cover, cockpit_device_id=devices.WEAPONS, value_down=-1.0, name=_('Master arm cover toggle'), category=_('ACM Panel')},

It seems that the toggle function for the master arm cover is just  for close (down=...) only not for open (no defined for open=...)

Yes and thats wrong. A toggle button shall both open and close it. I use a button for the cover so I hope they can fix it. 

[scommander2]

Updated the list:

- [ADDED] the master/arm cover toggle binding only works for closing but not opening: https://forum.dcs.world/topic/355201-stopwatch-and-master-arm-cover/?do=getNewComment

 

[royphsle]

12 hours ago, scommander2 said:

What kind of "start"? Coldstart? or...

 

When you start a flight, both coldstart and in the air, the stopwatch starts running without touching it. It shall not do that. 

[scommander2]

On 8/2/2024 at 12:30 PM, royphsle said:

the stopwatch starts running without touching it

I have not found more information/any documentation about stopwatch for F-14 yet.

[RustBelt]

1 hour ago, scommander2 said:

I have not found more information/any documentation about stopwatch for F-14 yet.

They may just mean the Clock? 

[scommander2]

58 minutes ago, RustBelt said:

They may just mean the Clock? 

Yes, it is.

[scommander2]

For the 2D players, I found the control panels for F-14 and others at:

https://www.etsy.com/uk/shop/OnYourTwelve

 

[RustBelt]

There is a better ACM panel out there.

[draconus]

9 hours ago, scommander2 said:

For the 2D players

Why only 2D players?

[Viper33]

So I guess we won't see the early A and A-6 AI this year either now? Why all this silence after F-4 release?

[draconus]

18 hours ago, Viper33 said:

Why all this silence after F-4 release?

https://en.m.wikipedia.org/wiki/Cash_cow

[scommander2]

Indeed, it is quite for a while.

I have learned that DCS will move to MT in the full speed and drop ST so all three-parties will make code changes accordingly.

According to the HB F-14 general channel, A-95-GR early is under HB's radar as well as B(U) because they are the same radar of AN/AWG-9.  The implementation is more possible but not "D" model (it is the different radar system).

About:

Shape of engine nozzles is wrong

It is related to the art work and the art work is required lots of resources so it can be classified the bottom of tasks according to people's comment in the channel.

Jester 2.0 - not sure What is the roadmap of HB for Viggen and Tomcat... This topic is kind of quite down for bit.

 

 

 

Edited September 9, 2024 by scommander2