RoGaR

Ah,OK, distance in km...Now it makes sense. I tried to figure out what kind of altitude restriction or obstacle warning is it Thank you for clarification.

I do not want to open a new topic. May I ask what the 68/9.57 stands for? Thanks.

Is it possible to create CSEL via OAP? I create an OAP from existing WP. Box the OAP -> The CSEL is created via the original WP. I create an OAP from existing WP. Box the OAP and designate the OAP (diamond instead of cross) -> The CSEL is created via the original WP. Am I doing something wrong or this feature is just not present?

Have you found out why the AI is not fighting? Thanks

This is still a issue. Can someone report it please?

Hello guys, I'm curious if any of you have idea how the virtual trainer works in this Kursant campaign. I like it very much and I would like to create something similar for myself for the Hornet. I bought that campaign and flew it and even try check what's inside the missions but no success. E.g. The aircraft at the mission editor had no WP, there are no trigger zones or triggers in the mission editor it's obviously out of my skill set. But I'm curious anyway

Hey I started a campaign too, and it looks amazing. The documentation is also excellent. However I cannot score 100 points. It's always 80. I managed to get just one warning for the the formation on the route back. It's the formation what gives you the score point? And I have one more strange issue. Saint do not fight with me. After separation I fly to west (as it was fragged), Tapes on, Turning hot, his aircraft disappears and the is another one which is not fighting at all. I fire my both of my sidewinders (space bar) and SIM guns too. I get "knock it off" and fly to south heading (as it was briefed). Am I doing something wrong? Thank you for any advice BTW I managed _OK_#3, so where I lost so many points? Small remark: The mission QNH is 2988 but there is 2990 in kneeboard. Tacview-20210529-150104-DCS-R1 M01.zip.acmi

So I managed the last mission as well the A/G radar is able to track in GMTmode and follow this infomation to the TGP. You just have to be aware, when you lost track (radar limitations). I worst case you have to maunualy lasing for the last few seconds. Thank you @Badger633 That was a great campaign

I play latest OB. As you can see in the second video, the litening pod works more like an ATFLIR. It came with latest OB. Here I attached my Tacview file I will give it to another try today. I would like to know how the TGP and the A/G radar track cooperates Tacview-20210520-215610-DCS-Mission 10 Camp 2 SC.zip.acmi

Hello guys, could you please check my attempts to track a moving target? There are two attempts. One is before and one after the last update. I just cannot lock it. I playing with the contrast / brightness. I think the target is pretty visible. I was able to lock them for a very short period, but then the TGP lost the lock (I was not tweak the TDC depress). BTW I have no issue during the day operations. Here is the video. There are bookmarks in the timeline. Cheers.

Yes I flew full afterburner...As I wrote I managed it behind Kutaisi (8+nm). Next time I try to drop the ordnance as well. BTW I checked the Tacview, and the Hawk shooted just one rocket. Whish me more luck for the next time BTW Here is my attempts to track the target. Am I doing it in the right way or it's really just a bug? There are bookmark at the timeline.

Today I flew that last mission 5th time. The Litening pod still do not track but I managed to kill the snake by manual slew and manual lasing....but on the way home I was shoot down by the Migs 8,7 miles behind Kutaisi... This campaign want me to keep playing it so ... let's see how it will work in two weeks for the 6th time

My First campaign for the Hornet and I love it. I flew the version with the SC. I'm almost done, just cannot lock the moving target at the last mission (current Hornet bug I guess). Anyway, I would like to ask about the wind conditions. Are those intended - @2000m 17m/s and @8000m 17m/s?? eg. In mission 6 “A BLOODY NIGHTCAP” at the CASE III holding I had 308GS when I flew from the mom and 248 when I flew towards to the mom. It caused me a bit troubles to calculate when to turn back to be in time. Maybe less experience players fight with this a bit. Yeah and BTW I almost crashed during Kutaisi landing But in overall very enjoyable campaign. Thank you.

This topic is still marked at "Investigating". Any updates?

Hi, I would like to report a possible bug about TGP and the HMD miscommunication when I try to designate target. What I try to do: I would like to pick roughly the area of interest via HMD. Then I try to find my target and designate it via TGP. The basic setup: GBU—12 (auto mode, instant fuse), TGP Pod – On and displayed in the MFD, A/G-on, Master Arm – on, HMD on. Normal work: 1) SCS (Sensor control switch) – FWR 2) Pick a close target via the HMD (less than 5 miles) – TDC Depress. The diamond appears in the HMD. The targeting pod should also look to this point and the diamond should be visible in the TGP’s MFD. Coordinates in the MFD are still !!! 3) Press the SCS (Sensor control switch) towards to the TGP’s MFD (SCS to Right in my case) 4) Slew the TDC in some direction. The diamond should change to the cross and you can pick up your new target via the TGP by TDC depress. 5) Press the TDC Depress in the new coordinates (The cross change to a diamond). The new position of the diamond should be visible in the TGP’s MFD. Coordinates in the MFD are still !!! This was how I expect it should work (and it works so far) but here comes the buggy part (at least for me)….repeat the previous procedure like this: 1) SCS (Sensor control switch) – FWR 2) Pick a far target via the HMD (10-15 miles) – TDC Depress. The diamond appears in the HMD. The targeting pod should also look to this point and the diamond should be visible in the TGP’s MFD. Coordinates in the MFD are still !!! 3) Press SCS (Sensor control switch) towards to the TGP’s MFD (SCS to Right in my case) 4) Slew the TDC in some direction. The diamond should change to the cross and you can pick up your new target via the TGP by TDC depress. 5) Press the TDC Depress in the new coordinates (The cross change to a diamond).. The new position of diamond should be visible in the TGP’s MFD and it is visible ….. BUT THE COORDINATES ARE CHANGING AND THE DIAMOND TRAVELS!!! I tried to undesignate, re-designate via markpoints or waypoints, offset the designation etc. No matter what I do, the diamond travels. If you try to fix it…the entire procedure degrades even more and in one point after (10-15) designation you will not even be able to switch between the diamond and the cross (Step 4 is not working) TGP_HMD_BUG_SHORT.trk

Yes, I meant this behaviour. Thank you very much for explanation. I apology for unnecessary topic. Next time I will double check the manual.

Ok...So... 1) SOI is switched to TGP MFD and the VVSLV option is picked. I push the TDC depress... the diamond in the HUD show up where the velocity vector is pointing (Expected Behaviour) 2) SOI is switched to the HUD ... HMD is on ...Turning my head to the side....I have the piper...I push the TDC depress... the diamond in the HMD show up where I pointed the piper (Expected Behaviour) 3) SOI is switched to the HUD....I dive my nose to -10°...I push the TDC depress... the diamond in the HUD show up where the velocity vector is pointing (Expected Behaviour) 4) SOI is switched to the HUD....I dive my nose to -3°...I push the TDC depress... the diamond in the HUD show up at the approx -7° position, NOT where the velocity vector is pointing (NON - Expected Behaviour)

Hi altogether. I cannot mark properly any target for TGP via HUD. If the velocity vector position is higher than -7° < interval -7° to 0°> the target diamond show up at approx. -7° position. If I put the nose below -7° < eg -10°> the marking is fine. The targeting via HMD works also works fine. TGP_HUD_BUG.trk

I tried some workaround as well. It seems that not only the pressure but also the ambient temperature has impact to this. I assume that F2 (F10) altitude is recalculated altitude to ISA. Try this: 1) Set AI to 27000 [ft] MSL and the weather conditions in ME to 15 [°C] and 29.92 inHg. Fly a formation with the AI. Set BALT autopilot at 27000 (HUD) then jump to F2....you should see difference <100ft. 1) Set AI to 27000 [ft] MSL and the weather conditions in ME to 30 [°C] and 29.92 inHg. Set BALT autopilot at 27000 (HUD) then jump to F2....you should see difference >1000ft. It seems that the AI ignore the weather conditions set in the ME and set its altitude based on ISA (15°C and 29.92).

Yes, you are right. In ME there is 1029 (lb). So is there a way how to correct it in the checklist?

Hello all, I tried to update my ordnance table, based on the weight of the Hornet. My empty Hornet weight based on the checklist page = 36858 (lb) My Hornet weight with GBU-32 (J-83 in the display) based on the checklist page = 37388 (lb) It gives me GBU-32 weight = 530 (lb). I expected that the GBU-32 is based on MK-83, so expected the weight around 1000(lb) Am I doing my measurement wrong or just the GBU-32 is not that heavy? Cheers

Hello altogether, do you know how to bind the radios on/off (I mean turn the knob in the cockpit, not the communication menu) or what is the keyboard shortcut for channel switch? I cannot find it in the list.

Thank you for your answer. But this happens even if I use keyboard. Your solution seems correct but I do not want to touch the root files. Is any chance that this bug will be fixed by next update by developers?

Hello alltogether. I tried to bind my RWR Indicator Control POWER Button to my MFD's but with no succes. I tried to use default shortcuts as well, but without success as well. When I push the key, the RWR panel lights up then turns off. I'm able turn on the RWR via mouse. Another friend of mine have the same issue. Roman

Hi, I have a similar problem. I have TurtleBeach Stealth 600 Headset for XboxOne and I use it with an Xbox Bluetooth adapter on my PC. Works well except a situation when I stop the game (or pause it) and there is no sound output. After a while, my headset turns off and I lost the ingame sound. If I turn my headset “ON” again, the sound is not restored. It seems that after my Headset Turns Off, the sound mixer in Windows lost the DCS sound channel, and it’s not able to restore it after I turn my headset back. The sound is restored after I restart the DCS. I did some workaround. If I jump to the menu I let play quiet menu music the headset is not turn off and everything works. If I forget the game in “pause” state the headphones turn off and I need to restart. I’m new in DCS and reading a lot of additional materials and often pause the game to read manuals or get familiar with the information in the kneeboard and lost my sense about the time and suddenly the headphones beep that they are going offline. It would be great If you give me some advice on how to fix this. Win 10 (64) - 1909 (Build 18363.900) DCS – non-Steam edition (Stable and OpenBeta)