4.34 - F/A-18 missing needles in all analog gauges
-
Unfortunately bad news when you use old cockpit from 4.33.x then you will encounter another issue. HSI guide system in tacan mode is broken, especially for ils landing. When you switch to TILS on final, arrow is not complete and guide system is working only on hud. I have right ils frequency, course and channel, double checked file station+ils.dat for right theater. In 4.34 hsi tacan mode works but for another change there are broken gauges with needles and other issues. So when you want to fly f-18, then choice is yours… we must hope for patch in earliest falcon weeks.
-
Err. nope. You might have confused pits…
4.33 F18C/E pit HSI-(T)ILS works ok , NO bug on arrow. - dials are ok even when not lighted.
–oh , yes , when in UFC/Radio Backup mode, then just TACAN is swapped , AA-TR <> TR … so when in BACKUP mode, TACAN for ground must be set on AA-TR … but if someone uses that still…4.34 F18C/E – bad pit - strange textures like 0000 on arrows, dials , hsi arrow not centered correctly
Please check again…
There are only 4.33 and 4.34 pit … no 4.xx.x - it doesnt matter, all the same pits , just one’s bugged , older one is OK
F18A/B uses different pit - it is not the same as C/D/E/F/G - those are two completely different pits, different models … look engine control , so cant compare between the two
-
Gone back to 4.33.5 for now, cause I want to fly other aircraft, too.
I really don’t have much hope for the support or bugfixes of other aircraft than the F-16 somewhere in the nearer future. Looks like 4.34 is a step backwards in this case.
Also YAME-Extractor still does not really support 4.34. This is the case for nearly one year now. So I couldn’t see any need for me to upgrade to 4.34 at the moment. I’ll stay with 4.33.5.
In my opinion 4.34.2 is only the better choice for guys which want to fly the F-16 only. I had the hope, as I heard 4.34 will see the light of day, that maybe some cockpits from the already included aircraft like the A-10A and the F-15E will be a bit improved and maybe the F-14D is already on board, too.
But sadly that didn’t happen and it also looks like noone is really interested in other flyables than the F-16 and it’s countless versions anymore.
And it’s not right that Falcon always was intended as an exclusively F-16 only simulation if you look at it’s history. Even in Falcon 3.0 was an A-10 planned as first addon aircraft, but it never made it. Instead the F/A-18 and the Mig-29 came out as addons. For Falcon Allied Force an A-10 was also planned as an later addon.
-
Gone back to 4.33.5 for now, cause I want to fly other aircraft, too.
I really don’t have much hope for the support or bugfixes of other aircraft than the F-16 somewhere in the nearer future. Looks like 4.34 is a step backwards in this case.
I really start to be pissed off big time
You can say you are disappointed that we don’t bring more support for non f16 , but that is total bullshit to say 4.34 is a step backward
Tell me exactly which step you consider backward ?
- the full carrier ATC support ?
- the improved carrier code ? (Cables ? Pitch and roll ? )
3)the f18 improved FLCS ? - the su33 Specific AFM ?
- the gun pod integration for m2kD?
Tell me exactly ? Do you think carriers are for f16?
And if you are not happy , why don’t you start modeling a nice 3D cockpit for the f14 ? Or the su33?
Too easy to complain all the time and critisize us is all the time !!! Fed up with this childish behavior ! Go and fly DCs they have plenty of fantastic module to sell !!
You know why I am talking about DCS?
I have worked years for carrier ops , f18 flcs etc….because one guy in BMS was always teasing me to do it because he was interested in the f18 only. He was supposed to work on the cockpit and so on !!!
I worked literally YEARS
The day The f18 has been released for DCS , this guy left the group saying he was not interested anymore
So YES I am pissed off to read that all this work is considered a step back
-
Gone back to 4.33.5 for now, cause I want to fly other aircraft, too.
And it’s not right that Falcon always was intended as an exclusively F-16 only simulation if you look at it’s history. Even in Falcon 3.0 was an A-10 planned as first addon aircraft, but it never made it. Instead the F/A-18 and the Mig-29 came out as addons. For Falcon Allied Force an A-10 was also planned as an later addon.
Falcon BMS is not Falcon 3.0 and Falcon BMS is not Falcon 4 Allied Force. Your comparisons are irrelevant. It’s actually quite funny that in two of your examples you mention add-ons that were planned but didn’t actually happen, but anyway…
Do you have any real idea how many members of Dev are active today? We are not DCS! Human Resources are extremely limited and already close to breaking point, working harder than we probably should be to continue to develop and improve the core of the sim, but you instead choose to bitch about other aircraft not receiving the attention you want them to.
If you have any affection at all for the F-16 and the work BMS have done, you really need to step back and be thankful for what you have received to date rather than posting naive bullshit like this.
-
Falcon BMS is not Falcon 3.0 and Falcon BMS is not Falcon 4 Allied Force. Your comparisons are irrelevant. It’s actually quite funny that in two of your examples you mention add-ons that were planned but didn’t actually happen, but anyway…
Do you have any real idea how many members of Dev are active today? We are not DCS! Human Resources are extremely limited and already close to breaking point, working harder than we probably should be to continue to develop and improve the core of the sim, but you instead choose to bitch about other aircraft not receiving the attention you want them to.
If you have any affection at all for the F-16 and the work BMS have done, you really need to step back and be thankful for what you have received to date rather than posting naive bullshit like this.
Correct, BMS this is not 150 coders, not even 50 not even 10 not even 5 !!!
-
Really? There’s 4 or less coders and one of them is you Mav-jp? wow……
Every BMS major updates brings the core updates of combat simulator which I can’t expect to see in the another one… I would lose true air combat simulator without you guys. Thank you always and please take care of yourself.
-
Fewer than five?! Oh, my… I would’ve never suspected that. I thought the dev team consisted of at least a dozen gifted individuals organized in smaller groups specializing in separate aspects of the simulation, graphics, campaign, theatre building etc. Now it seems that those few are doing the whole volume of the work necessary to maintain and improve the sim… My respect, gentlemen.
-
Correcto, BMS esto no es 150 codificadores, ni siquiera 50 ni siquiera 10 ni siquiera 5 !!! [/ QUOTE]
:bowd:
:bowd:
:bowd: -
I really start to be pissed off big time
You can say you are disappointed that we don’t bring more support for non f16 , but that is total bullshit to say 4.34 is a step backward
Tell me exactly which step you consider backward ?
- the full carrier ATC support ?
- the improved carrier code ? (Cables ? Pitch and roll ? )
3)the f18 improved FLCS ? - the su33 Specific AFM ?
- the gun pod integration for m2kD?
Tell me exactly ? Do you think carriers are for f16?
And if you are not happy , why don’t you start modeling a nice 3D cockpit for the f14 ? Or the su33?
Too easy to complain all the time and critisize us is all the time !!! Fed up with this childish behavior ! Go and fly DCs they have plenty of fantastic module to sell !!
You know why I am talking about DCS?
I have worked years for carrier ops , f18 flcs etc….because one guy in BMS was always teasing me to do it because he was interested in the f18 only. He was supposed to work on the cockpit and so on !!!
I worked literally YEARS
The day The f18 has been released for DCS , this guy left the group saying he was not interested anymore
So YES I am pissed off to read that all this work is considered a step back
I read this a lot all the time ever and ever again, that BMS is F-16 only, cause of the systems and … It doesn’t make sense to do other aircraft, cause they never will be like in real life. As I said, I think they are realistic enough and you and the guys which made them have done a exceeding work here! Why wasting all this hard, good work?
You said, you’ve done so much work for it, but what’s all this work worth if the aircraft which benefit from it never get bugfixes cause all of the hardcore F-16 flyers have the opinion it’s not worth it or if, somewhere in the far future at best.
Don’t get me wrong! I respect your work and I’m really happy that guys like you did other aircraft and made so much work to get naval operations possible, but if you ask something about anything else as the F-16 here in the forum, you mostly get the answer that BMS is an F-16 simulation and nothing else, so if you want to fly something other go to DCS.
I love BMS and I see so much potential in it, which DCS will never have. That’s why I’m dissapointed that so much guys have this hardcore “F-16 only attitude”. Btw I have all the DCS modules like F-14, F/A-18, F-16, F-5, A-10, AV-8B and even FC3, but I will always prefer BMS over DCS cause it has so much more to offer.
-
Hi white_fang, i checked it out again and yes, it works but little bit another way than i expected (like in 4.34), no matter important is it works. No need to use backup mode and switching between aa-tr and tr (only for tanker or package) , my tacan channel input is on ded not on dials and also know there are different types of cockpits, thanks for your help. Now it works like it works and yea…it’s quite cool. Even yame works with little tuning…btw i found out i MUST use old cockpit from 4.33, otherwise mfd extraction in yame doesn’t work for me. Cheers.
-
YAME is dependent only on those extraction coordinates for LMFD , RMFD , RWR … etc, found in 3dcockipt.dat in /art/cockpitart/planecode … that is extracted shared memory.
eg.hud 24154 -2750 -618 24154 2750 -618 24154 -2750 4902 [color]287 314 573 600[/color] c; pfl 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 [color]0 0 200 86[/color] c; ded 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 [color]201 0 401 86[/color] c; rwr 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 [color]454 164 600 310[/color] c; mfdleft 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 [color]0 88 225 313[/color] c; mfdright 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 [color]228 88 453 313[/color] c;
So make that coordinates right and you’re able to do extraction for any plane, YAME will work for any plane… but yeah … it is pita constantly tweaking and then if you change plane you should change coordinates in yame also. , as different plane , different shared memory setup.
(The game , “BMS” will not “punish” you if you play with those , but, hehe, make backup originals before entering that doors)I don’t use yame anymore… technically is it not hard to setup , but I don’t have touchscreen anymore … so … I went “FalconMFD” , android tablet way … less fuss, but again same principle, shared memory extraction via network to the tablet screen , so = clickable mfd’s … that was the whole point.
BUt , what we were talking about is LOD model for cockpit , that is something different then 3dcockpit.dat, … there’s all magic happening regarding , switches , buttons , and texturing… so in 4.34 that model got ill , dunno why, perhaps not intentionally , but since model from 4.33 is still more/less OK … why not use it ?? is not that something like that is forbidden … I mean , it is not MP crucial , no cheat …
If I would be more proficient in “Lodedit” , maybe I would do it myself … but is pita a bit, as that editor is like from “1947” and I still don’t understand 75% of it … Like MaVJP said … 1000’s of hours … and I understand him … between a rock and a hard place.
Just fly 4.33 pit until stuff gets fixed… a year maybe.
Cheers
-
Where could I found the LOD’s of the cockpits themselfs? I fideled around a bit with the LOD-Editor yesterday and was able to find the aircraft models, but I couldn’t find the cockpit 3D-models. I used the cockpit-parents document as reference but those LOD-Numbers are totally different models (e.g. a Maverick rocket instead of an F-16A pit the reference stated) in the hdr.
Is there a good manual somewhere, on how to edit models? I already made an 3d-pit of the KA-50 Blackshark for EECH Allmods and maybe with some hard work I’m also able to do stuff for BMS. Looks like it’s much more complex in 3D but I will do my best. But I’m not able to do the coding which is needed for instruments to get them running. Don’t know how things working in BMS with the 3D-cockpits, but in EECH you must be able to code in C for such things.
-
aaah, so yame takes data from 3dckpit.dat, another useful experience, now it makes sense, thx. but let’s talk about these two things…
- the previous thing about HSI
My opinion is it should work like arrows shows, pls correct me if i’m wrong. Let’s take this situation as shows the first picture.
arrow 1 shows where the symbols are, arrow 2 shows where the symbols should be, am i right?
- Can we do something about these two things or is it too difficult (3dsMax, DevC++, etc.)? I mean make them buttons light up when you turn it on but without console light as shows circle one and assign the right texture (probably in 2712.dds) to the simMPOTtoggle switch in circle two. I think both things (switch and buttons) is related to bad texture assignment but not sure.
I also noticed in f-18a/b/d it is ok but only in c cockpit model that switch is black…appreciate any ideas like always
-
All that is “very easy” to fix with lodedit … IF you don’t have something more important to do…
It is just matter of saying to the model editor , take this piece of picture (texture) and apply it over that area. … but for more , take a lodedit course , get a fey greys … come talk to me for a year or so…
- ONCE I’ve had a luck to successfully hack re-mod pilots legs and kneboards in F18C/E pit … and I would NEVER return to work with lodedtor … even for zillion local currency. - I don’t have that nerves.
-
i know, it wants nerves of steel…
-
I can go through texture mapping lessons course but tell me please which program you(anyone) would use for opening/editing LOD files and mapping the right texture to them? Thx.
P.S. could it be eg. Blender…? Lod editor looks like it’s usable mostly for viewing than editing….i have been trying save model just for test and it’s unusable then, ogglod.exe will crash and falcon bms too. -
Sorry to all f-18 flyers and naval ops lovers, giving up this thing…for those who got similar idea (i believe there are plenty of them)… i spent hours last dayz and tried to explore f-18a/b/c/d cockpit models in lod editor and tried really maximum what i could do to complete some features.
lighting flaps indicator states - like landing gears when they pulled off, lighting all RWR buttons, yellow textured simMPOTtoggle switchIt is almost comparable difficulty like with cracking in assembler and for common human being looks like impossible. IMO (maybe i’m wrong) only author of these models knows proper nodes and subtrees in lod editor and know how to assign proper textures with included texture mapping tool.
I also wanted to help others to complete these cockpit features for better feeling from playing but white_fang you were right. It was rather wasting of time cause it looks like nowadays usability of lod editor is rather only for viewing models and textures and looking for lod and texture #numbers than for editing. Also is interresting that Lod2dxmconv.exe not included in lod editor pack for trying map these textures in another software. Then If you u want to save lod model (no matter if edited or not) it will screw up whole cockpit model (probably because bad handling with new falcon databases) and after save will falcon crash when u fire up the game. Yea, just don’t think about it when playing and fly with that what we have until patch will come and hope that will be fixed and included in that one day. How sad. Or maybe somebody privy, initiated and dedicated will read this thread and will find some time to do that. God knows. Happy flying.Cheers.
-
@FoxBMS:
Sorry to all f-18 flyers and naval ops lovers, giving up this thing…for those who got similar idea (i believe there are plenty of them)… i spent hours last dayz and tried to explore f-18a/b/c/d cockpit models in lod editor and tried really maximum what i could do to complete some features.
lighting flaps indicator states - like landing gears when they pulled off, lighting all RWR buttons, yellow textured simMPOTtoggle switchIt is almost comparable difficulty like with cracking in assembler and for common human being looks like impossible. IMO (maybe i’m wrong) only author of these models knows proper nodes and subtrees in lod editor and know how to assign proper textures with included texture mapping tool.
I also wanted to help others to complete these cockpit features for better feeling from playing but white_fang you were right. It was rather wasting of time cause it looks like nowadays usability of lod editor is rather only for viewing models and textures and looking for lod and texture #numbers than for editing. Also is interresting that Lod2dxmconv.exe not included in lod editor pack for trying map these textures in another software. Then If you u want to save lod model (no matter if edited or not) it will screw up whole cockpit model (probably because bad handling with new falcon databases) and after save will falcon crash when u fire up the game. Yea, just don’t think about it when playing and fly with that what we have until patch will come and hope that will be fixed and included in that one day. How sad. Or maybe somebody privy, initiated and dedicated will read this thread and will find some time to do that. God knows. Happy flying.Cheers.
I’m not an expert to 3D models, formats etc. But I do know that people within BMS team do mods to the F-16 cockpits, adding and removing stuff, fixing etc. And I don’t think we have the source 3D model (i.e in max format). Again, I’m not sure you are looking for the same, but you can maybe try to contact Cougar from BMS team about how he is modding F-16 cockpits.
Also, I know it may sound like the obvious, but trust me: “i spent hours last dayz…” If I had a Dollar for every time I said that to myself…
From my experience, if you want to get something going:1. Look for the right people - This works same in RL SW work - Sometime you spend days on something that someone else will solve for you in 5 minutes. Yes I know sometimes it won’t be easy to find the right guys and get answers, but usually a PM to some known BMS member who check the forums daily or so will get you the link to the right people.
2. Don’t give up! Again, this is more about communication than anything else. If something has high priority for the community, then we (BMS team) usually try to help. It’s not perfect but I don’t think we ignore the community needs. So if you feel something is important enough and #1 don’t help so you need help with getting possibly source files, you SHOULD make EVERYTHING to get them!
Regarding this specific case of modding the F-18 cockpit, when I think of it, the F-18 cockpit was IIRC created by WaveyDave from BMS team. He isn’t all the time reading the forums here, but again getting contact with him directly or via someone from BMS team will probably get you access to the F-18 source in 3D software (3D max I guess) format. From there it should be easier I assume.
Don’t let the frustration get you
-
@FoxBMS:
Sorry to all f-18 flyers and naval ops lovers, giving up this thing…for those who got similar idea (i believe there are plenty of them)… i spent hours last dayz and tried to explore f-18a/b/c/d cockpit models in lod editor and tried really maximum what i could do to complete some features.
lighting flaps indicator states - like landing gears when they pulled off, lighting all RWR buttons, yellow textured simMPOTtoggle switchIt is almost comparable difficulty like with cracking in assembler and for common human being looks like impossible. IMO (maybe i’m wrong) only author of these models knows proper nodes and subtrees in lod editor and know how to assign proper textures with included texture mapping tool.
I also wanted to help others to complete these cockpit features for better feeling from playing but white_fang you were right. It was rather wasting of time cause it looks like nowadays usability of lod editor is rather only for viewing models and textures and looking for lod and texture #numbers than for editing. Also is interresting that Lod2dxmconv.exe not included in lod editor pack for trying map these textures in another software. Then If you u want to save lod model (no matter if edited or not) it will screw up whole cockpit model (probably because bad handling with new falcon databases) and after save will falcon crash when u fire up the game. Yea, just don’t think about it when playing and fly with that what we have until patch will come and hope that will be fixed and included in that one day. How sad. Or maybe somebody privy, initiated and dedicated will read this thread and will find some time to do that. God knows. Happy flying.Cheers.
I was working on new textures for some elements (especially canopy frame and mirrors), but I just cannot stand that I am not able to correct UFC markings. I mean it is easy to make them correct for day ops, but not possible to make correct backlight