diegoepoimaria01

Thanks, we did run into this issue yesterday ... enemy ground troops was VERY happy :P

Hi all I'm experiencing some issue with the navflir on the hud too: 1) The image is cut in half: Only the lower half of the hud is actually displaying flir image. A month ago it was a full picture ( I have a photo of that ). Tried to move the point of view and to move the whole plane ... but the part displayed is still only the bottom half, while in the right MPCD there's the full picture. 2) The image itself is either too bright ( blackhot ) or too dark ( withehot ) on the hud, and, on the ground, no terrain features are recognizable ... only major shapes of mountains are. On the other hand, sea and air are pretty good. Again, on the right MPCD there's a mutch better picture ... I've tried with contrast , but with no luck. At this point, I think that there's a defect in the last patch ( at least, for the point 1 )

Thanks, I'll try ... Maybe ( PROBABLY ) I did solve it by curse, restart, uninstall and reinstall sounds devices and sheer luck ...

Thanks, tried, but no success ... I've also discovered that Normal DCS works fine, but beta does not. Other games works fine too ...

Hi all Tonight I was about to fly with a couple of frineds, but, for no apparent reason and after having done this many times before ( and withouth changing anything ), tonight DCS can't play any sound trough my headphones . I have the Bose quiet comfort 35, and to be able to talk with my friends on discors, I need to activate and use the headphones as a headset, and not as a headphones. But this time, DCS wasn't able to play on that cnannel. I can play trough the speaker, I cna play trough the headphones setting of the bose, but not trough the headset. And of course Discord can't work on the headphones channel. So I can talk with my friends OR I can hear DCS ... Headphones are connected trough bluetooth. Did anyone had this kind of issue ? Suggestions ? thanks, I''m getting crazy here.

Yep, my same doubt too ... That means that we aren't able to buy it yet ?

As far as I know, for the Tomcat it was the opposite ... It didn't have a HUD , but the HUD was projected onto the flat central panel of the windscreen. And the reason was that it had horrible problems with I think glare ( my english here is failing me, and my memory too , so please be kind )... I remember distinctly to have read something about ghost contacts ... Might it be that in the Tomcat HUD and windshield were not parallel but at an angle and so it did create glare ? Anyway, I', curious too :D

Ok, I've been able to <s>harass</s> ... ask to a Hornet pilot, and it seems that the whole BIT batch is rarely used, or at least, not for a "normal" start. It seems that only the FCS reset is performed ( button on the left hand console), then FCS bit is performed ( Y+button on the MDF ), then, if it's cold, FCS Reset button + Y to execute 10 repetitions of surface moving ( but if it's hot, it can even overheat the actuators ), then Fuel Bit ( that it seems to be not working in our DCS Hornet ) and Oxygen bit ( that it's surely not modelled ). And that's it ...

Ok, I had wrote a reply message, but obviously it got cancelled ... :wallbash: I've tried some more, but in the end, I still got the same resutls ... BIT that are not bitting.... Procedure seems to be correct from what I've read on the real hornet manual ... The ED manual does not says mutch about BIT, so ... At this point I think it's a real "issue" ... either it's yet to do or it's a real bug. Now, do devs read this forum or do I have to write somewhere ? Or maybe rere are FAQ's around that I don't know ... I'm a "BIT" ( :P ) confused as of now ...

No, actually the tester is you ... 4 patterns will be displayed and then you press stop. After that, it goes into GO status. :D In the meantime, the Hornet manual reports this: Page 235 2.20.3 Avionic BIT. In most instances, two types of BIT are mechanized, periodic and initiated. Periodic BIT begins functioning upon equipment power application. It provides a failure detection capability that is somewhat less than that provided by initiated BIT in that it does not interfere with normal equipment operation. So ok, Periodic Bit and Initiated Bit. Interesting are: GO => All systems => Initiated BIT completed without failure. PBIT GO => All systems except MC1, MC2, and RWR => IBIT has not been initiated and the system periodic BIT is not reporting any failures. RESTRT => All systems except MC1, MC2, and RWR => Reinitialize BIT; equipment did not respond to BIT command, remained in BIT too long and was terminated by MC. Also, important, I have RWR that is always in RESTRT , so it should means that the IBIT was not properly initiated ...

Oh ... Many many thanks :D So A PBIT is something the system does alone. PBIT GO i think means that the system is ready for the IBIT , that is shown as "IN TEST". CBIT is never shown, I think, correct ? Ok, I'm reading the manual, Page 237, and he things are absolutely not clear ... aaaargh! As of now, I have read that the full test should take like 2.5 minutes ... with the AUTO button ... let's try that and we'll see.

Thanks, I'm studying the manual ... pretty complex as of now, but let's try and see what comes out of it ... :pilotfly: :joystick: :smartass:

I had the same issue ... and I'm still working on it. I *THINK* it might be because the target on the TPOD is not enough for the Maverick ... Maybe if you lock the tpod on a contrast line, mav can lock on it ... I'm yet not sure. I've discovered that if you move it around a but it *MIGHT* work ... But I'm curious too for the correct explanation.

Oooh, ok, so PBIT GO is good, ok! :joystick: So, now I'm down to: Flir and LTDR "NOT RDY" , and that's correct, since they aren't onboard ( well, Flir can be, but I guess that the LTDR is the Nite hawk. or maybe the passive side , right one, that is only a lser spot tracker ( but that's an educated guess, not supported by facts ). CLC is still NOT RDY, but I don't even know what it is ... It's in "stores" but I can't even start that test. On the ohter hand tough, From "stores" I was able to test weapons, by click on "ALL", and so triggering test for everything except CLC ... But they seems to be in "in test" for a while, and then get back to DRGD ... I don't know. ALE-47 Seems to be on only without WOW, I guess, so that test must be delayed. EDIT: Yes, it works when there's no WOW, ok :D RWR Is always in RESTR ... but I've done the test ... Am I missing something there ? Then I have: -IFF => NOT RDY If I've understood correctly, it's not yet there, ok. -D/L => NOT RDY ??? I have no clue ... -MIDS => NOT RDY It's like the Link 16, if I've understood correctly ... But I don't know how to use it yet. -Beacon => OFF And this too should not have been implemented yet. -DMS => It's in the Display page, but no clue ... -AUG => DEGD ??? I have no clue ... But, on the other hand, I was able to check all the nav page ( ecept for the Beacon of course ). Weird, you need to turn on ILS and TACAN, but you also need to enter in the ils system a channel , even if it's not real ... Or maybe it was just terribly slow ... I'm not totally sure there ... Ok, that's concludes my BIT page adventure for tonight ... See you all tomorrow :D In the meantime I'll try to find a real Hornet Manual and sees what I can find there. Does someone have one ? :P EDIT: There might be a bug: Radar is PBIT GO even if the radar knob is set to OFF. Is it correct ? Shouldn't there be an OFF there ?

Ok, so I was totally wrong on acronyms ... GREAT :cry::doh::lol: Yes, I tought that some things might not be completed, just I didn't know what they were, and so If I were missing something in the test procedure. Ok, so a PBIT as in Periodic BIT means that the system is go ? Or that I need sto still do something ? Indeed :book::helpsmilie: When you say: "fcs bit switch", is it the one on the right hand side panel, that is controlled with the Y key, correct ? Yes, I have found that procedure by trying, but I think that I was missing the final flap part ... that should clear the "restart" message, correct ? I've heard the beeping tone tough. Also, If I press the FCS reset button and the fcs bit switch , the system will perform another test ( 10 repetitions of flap and slat up and down ). How and when do you perform that ? And on a carrier, when the wings are spread only at the end, on the cat, how's the procedure ? I guess it will be as you were describing and then controls wipeout on the catapult, correct? And also, I've read that the final chekers are the guys behind the plane, crouched down and angled to resiste the engine blast after the launch ( my bad english does not allow me to better explain this , sorry ) , that will check for any hydraulic fluid leak because the wings are spread only on the catapult ... HMD: So you , the pilot, are the tester ... I tought that it was taking too long ... :doh: RWR: yes, but still, I've got a pbit like indication ... not a go ... So Pbit in that case is a go ? Also, I see test messages on the rwr scope down right, correct ? Guys, THANKS , and sorry for another load of questions, but really really thanks :D :pilotfly: EDIT: I've just quickly tested, and now it's working better. Just, If i have a PBIT GO, it measn that I'm good to go, correct ? But, for example, I still have Weapons and somethign I don't remember as "DEGD" , that should means "Degraded", correct ? Also, I've noted that the warning is also for things that aren't there, like the TPOD if it's not installed or the Beacon, that isn't implemented, and in that case is "OFF", correct ?

Hi all :D I'm slowly learning the Hornet ( Amazing machine ), and step by step I'm starting to understand it. As of now tough, I can't figure it out how to clear all the errors in the DDI BIT page ... Even the FCS, in the end I'm able to clear out the various errors, but I'm never sure on the correct procedure or the correct sequence to follow. Also, what does PBIT and RESTRICTED means ? I guess that Restricted means something like " degraded performances " , but in practice, what does happens ? PBIT I guess that is something like Power-up Built-In Test, but then ? Do I need to perform anohter test ? Do I need to just wait ? I tought that it might be because it's still in Early Access , but I'm not sure ... I've searched online, but no luck. I've searched this forum, and still no luck ... Also, startup procedures does not contemplate the BIT page in full ... So, does anyone knows something ? Thanks for the help :D

Tried yesterday ... and it's amazing! It shows that it's an unifinished product ( and also it shows that I don't know yet how to handle it ), but it's amazing and I'm happy to ahve brought it! :D

I agree, and I have done the same.

It's the same for me ... A very small but surely noticeable tendency to roll right, at any speed and any altitude. Yesterday I was trying to destroy the engines with mach overspeed ( just for a test :P ) and I've got this continuous right roll at any speed ... I was unable to stop it with trim ( got a wharthog ) without overcorrecting on the other side. Weird ... nothing critical, but surely it's there.

Hi I'm absolutely no expert, but i've found that smoothening the joystick curve did help a lot, at least for me. Also, I've discovered AFTER some time, that the F-5 have a yaw and pitch damper that have to be activated manually after the engines are up ( just behind the throttle levers ). Trimming, on the other hand, is tricky for me too ...

Just two words: Thank You! :D

Sorry, i tought I've repied to you, but something didn't work correctly. I'm not sure I had correctly understood the answer. You said that , sice the ATC gives you the airfield elevation in a different format, then your altimeter can't be adjusted correctly. But then a simple conversion chart should be enough, no? I mean, the ATc says : 1234 4 scenarios: 1) I'm in Caucasus with a russian airplane => ok, it's QFE 2) I'm in Caucasus with an allied airplane => conversion form QFE to QNH 3) I'm in Nevada with an allied airplane => ok, it's QNH 4) I'm in Nevada with a russian airplane => conversion form QNH to QFE For me, the issue is that on the ground in Nevada the SU-27 altimenter can't be lowered enough to reach zero, while Su-25 altimenter can. So, even if i know the QFE/QNH, I can't use it. I can't even set my altimeter on the ground to zero without looking at the QFE/QNH.

Hmmmm, ok. I'll have to learn about QNH and QFE then. But my problem is that, while on the ground, I can't lower the altimeter enough for it to reach the zero. so, while standing on the runway, my altimeter still indicates about 200 meters. Radar altimeters and HUD altimeters works fine though. Is it a minor bug or the Flanker has a limitation in altimeter setting?

The "clock" altimeter on the SU-27 can't be lowered enough to reach zero when on the ground. It seems that the lower pressure ( QNH? ) that the altimeter can accept isn't low enough ( the lower end is something near 70, while the ground is at 65 , if i remeber correctly ). Is it a bug or am I misisng something ( like a limitation )? In the SU-25 the altimeter can be set that low, but I don't know on other planes.

Don't know... i've made a quick try but i can't figure out if it's working or not ... it seems it tries to make the aircraft more stable, but not like the autopilot on the A-10A. I'll try again later on.