Problem with LGBs
-
Hi!
I can’t repro … or … I don’t understand you issue.
When I drop wy two GBU12, I still have the TGP image after the 2nd drop.
Please give more info and a repro case following this template: https://www.benchmarksims.org/forum/showthread.php?35644-How-to-make-a-bug-reportRegards.
-
…make sure you’re in a Hornet, Dee-Jay - this sounds like another Hornet specific complaint. And if you’ve also made any improvements to how the Hornet/ATFLIR combination are modeled it could also just be a matter of pilot technique.
-
…make sure you’re in a Hornet, Dee-Jay - this sounds like another Hornet specific complaint. And if you’ve also made any improvements to how the Hornet/ATFLIR combination are modeled it could also just be a matter of pilot technique.
But but…it’s an F16 Study Sim…not to be confused with DCS
-
Yeah…and I just noticed the “fly F-16s only” Config option with BMS 3.45 and finally checked it - wish I’d noticed and done that a LONG time ago!
I only mentioned it because the OP included it in his initial post - and that there are things about the geometry between an F-16 and an F/A-18 that will certainly impact the post-release operation for an LGB if the two are modeled correctly…so I had to ask.
-
But but…it’s an F16 Study Sim…not to be confused with DCS
You are right about this is a F16 sim, but it is not a reason to break something that worked.- This is a new bug since 4,34 hadnt such issue,- And I confirm it only happens to F18C (didnt try with Super Hornets), no problem with Vipers.-
Seems that 4,35 is not friendly to Hornets as some new bugs are reported.- -
but it is not a reason to break something that worked…-
Of course there are reasons. Tons of reasons actually.
Since Falcon4 is an F-16 simulation, F-18 is using 95% of F-16 avionics. When modifications on F-16 avionics or cockpit callbacks are made, F-18 (and some other a/c) is affected.
Since nobody really seriously care about the F-18 (for good reasons … available dev resources is a good reason to me), the F-18 gets some bug because it is not properly maintained by its original working team (whose some left some times ago).
I know only one guys in the team who were used to fly F-18 … I haven’t seen any bug report from him for lonnng time.I know some ppl won’t be pleased about what I am saying, but it is simply a fact.
So now … it i up to you to replace those guys who were the F-18 community members of Falcon4 community (no need to be a BMS team member to get the job done I think). But need at least one person to coordinate. It will not be me.
-
May I suggest two things:
but it is not a reason to break something that worked.
1. to the users: Join the Bug effort and report your F-18 issues here:
So now … it i up to you to replace those guys who were the F-18 community members of Falcon4 community (no need to be a BMS team member to get the job done I think). But need at least one person to coordinate. It will not be me.
2. to the dev, it’s nice to wish for community members to take over and fill the void of dev who left (ask aslo why they left btw) but that wishful thinking is nothing but wind blowing if the dev team doesn’t provide guidance, help and support to integrate that work into the next release. Therefore I wish these initiatives are fully supported like when you say something, you do what you say
Hopefully that will happen and their effort won’t be wasted -
@Red:
2. to the dev, it’s nice to wish for community members to take over and fill the void of dev who left (ask aslo why they left btw) but that wishful thinking is nothing but wind blowing if the dev team doesn’t provide guidance, help and support to integrate that work into the next release. Therefore I wish these initiatives are fully supported like when you say something, you do what you say
Hopefully that will happen and their effort won’t be wastedMaybe you could forward your post to Sting (?) … I know anybody else from BMS team flying the F-18.
On my side (and I know that on BB side also) the bag is already more than full. I am trying from time to time to coordinates some new materials with Luke777, Dema, CCC, VO_101 … etc … it is already difficult like it is added to the “regular” internal work which is enough to spend from 4 to 10 hours a day on BMS Dev task.
Personally, I am not in favor of supporting other a/c in BMS because … because exactly this thread. … Not because I don’t like other a/c. But simply because we have to chose between:
Doing few things correctly.
Doing much more … incorrectly.In both cases, there will be disappointed peoples.
-
I’m not a dev.
I’m not a programmer.
It’s been a bit less than one year since I got FBMS and integrated this forum .So I can really understand the dilemna of this subject , well summerized by Dee-Jay in many post . : FBMS devs have probably way enough work to do with all the core sim and the Viper .
It’s up to us , the users, the modders , to maintain and improve the non F-16 a/c , if we want them to fly at their best . If the modders are modding , while the devs are developping , well , all will be fine .
if ppl could learn to appreciate what they have, with the unavoidable limitations , it would be even better .
If ppl would want to improve by themselves what they can improve , instead of waiting someoneelse to provide what they want , it would be even better than better .It’s exactly what those who made those non F-16 pits , thoses non F-16 a/c , did before us .
And from that point , I agree with Red Dog : Smg like a resource page , a walkthrough dedicated page for example , in this forum , would help those who would like to try to improve the non F-16 situation .
If we want to BMS to improve in all areas, without killing the devs on the task , or discouraging them by exhaustment , the knowledge should be shared .
Not only with informal discussions on the forum : it’s already good , but probably not enough .
I want to take a stupid example : mine (I say this because my contribution in the global effort seems so marginal to me , that I nearly think it’s not a contribution)
thanks to eddroper’s walkthroughs , I 1st learn to change a pit , then to change a pit and wingviews . Doing so , I learned basics LOD editing . With basic LOD editing skills , I could really begin to modify the plane by myself, and now I can do wingview LOD by myself , and little modifications of those LODs . Which leads me now to very soon start to learn 3D modeling . When I will be able to do this , I will be able to build entire planes ; and , with more experience, it will probably lead me to try to build pit . The progression is logical .
As i have absolutely no particular skills , I think it could be the same for every pilot who would like to try . Imagine what could be done … in 2 or 3 years, hundreds of pilots would be able to do many things , in many areas … It would help , not ?
that’s why, in accordance with eddropper , I decided to provide walkthrough to how to do basics retrofits . I(we) could have decided to keep the knowledge for me(us) . We didn’t .
The result is that, one day , my Retrofit Hangar will hopefully become useless . It’s the price . But in the meantime , dozen of pilots will be able to help, and some of them will maybe become modellers (as I want to do) , and maybe even devs (this, i don’t want to ) . THIS will help BMS team .
Everyone will benefit of the general increase of knowledge level .
[I[B]]I think we need a dedicated tutorial section (Vids are best, but maybe also PDF or text if really well explained step by steps).
A bit long to do at start , but then , the birds will leave the nest , and maybe help their parents .
-
I also am not a dev, nor a programmer, and of course not an expert, I am just a simple BMS user, who besides flying the Viper, loves carrier operations but understand the situation and doesnt pretend that to be improved, only expecting to just work as they did before.-
As I said, I am not an expert, but still can understand Dee-Jay reasons about new F18 bugs coming from F16 modifications, but also as a non expert I wonder if it is so dificult to fix them.-
Of course that If should have the skill, I would inmediately put my hands on the job.-