pdmarsh

@emc -- In order to see if the displays are working on the Multi Panel, you have to configure them with DCS-BIOS commands. Please refer to the video tutorials listed in the first post on this thread. The second tutorial explains how to use DCS-BIOS commands. Paul

Hi Devrim, I have seen similar behavior as well. When I open DCSFlightpanels I always flip a few switches just to make sure it's working. Then, when I open DCS, I go into "controls" and do the same for the module I'll be flying. The DCS-BIOS configurations won't be seen there, but it somehow initializes everything. If I forget to do this before I get in the cockpit, I get into the controls in-game and do the same there. For some reason the panels need this little kick to sync up with the game. Hope this helps. Paul

My pleasure and good news! Yes, there is a bit of wind in the mission. I actually wondered about how wind would affect this. The original mission is attached. To save time, you might want to move the Viggen flight to an air start near waypoint 1 or later. I will test again myself without wind. To anyone else who might download the mission, it's not quite ready for prime time. When it is, I'll post it to User Files along with a mission brief. Thanks again, RagnarDa, for looking into this. Paul Floodgates DCS 2.5.miz

@RagnarDa -- I made a video this afternoon that shows fairly well the problems I am having with precision dive bombing. In a controlled environment with level approaches I was getting it to work, but the scenario in the video has been all but impossible for me to work out. While the video might run a bit long, I do request that you watch it in its entirety to see HUD aiming cue behavior under different approaches. Thank you, Paul

Hi RagnarDa, I'll be happy to provide whatever additional input I can, but it might have to wait until the weekend. I'll try to capture some video as well as a replay file. While I think precision bombing is in a usable state now, with practice, I hesitate to say it's all good. I don't know yet how difficult it will be outside of a controlled test scenario. If I didn't follow the precise profiles noted above, high or low, it wasn't possible to keep the aim cue on the HUD. One thing I have noticed that I just don't remember if it was present before was that when approaching the target area straight and level, and when in ANF/DYK modes, the aim cue stays toward the top of the HUD. As you nose over, at some point the aim cue jumps to the bottom of the HUD. Thanks, Paul

First, I stand corrected. There is altitude information in the manual, but I missed it. The delivery profile graphic does not show range or altitude. However, the series of HUD indicator images below the profile graphic does show altitudes on the left. My bad for missing that. Second, I flew the low altitude delivery profile (start dive at 750 meters) and had some success with it. Still, like the high altitude delivery profile I was attempting, it's not very forgiving. Maybe that's normal. I had my best deliveries with a level approach to the target and nosing down after the target passes below the aircraft. Even then it takes a bit of effort to keep the aim cue on the HUD. The few attempts I made with a lower altitude approach and pop-up to 750 meters were not as successful. Maybe practice will take care of that. Since this is so different from my experience with first release of the Viggen module, I would appreciate hearing from Heatblur if what we have now is considered final with regard to precision dive bombing. Thanks, Paul

The version of the manual that I have been using doesn't give altitudes for the procedure. I have been learning by trial and error. I don't recall seeing the kneedboard pages before this, but maybe I just missed them somehow. I'll try those altitudes and see what happens. The numbers I posted came from my latest attempt to get this working. Thanks, Paul

After testing precision dive bombing in beta release 2.5.2.20601, I am not entirely convinced it is yet working as it should. I have found only one delivery profile that works, and maybe that's just the way it is at this point. I can say that, without question, precision dive bombing was much more forgiving in the early days of the Viggen release. Here is what works for me: 1. Put HUD glass in lower position. 2. Start dive from at least 5,000 meters, higher is probably better until you get better at it. 3. Dive angle must be at least 42° to keep aiming cue from drifting off bottom of HUD. 4. You might have to shallow-out the dive for a bit to get the target further under your nose and to keep the aim cue on the HUD. Again, practice will probably make this easier. 5. The release cue will come at around 2,500 meters. After this it goes away. I believe the release cue was coming much lower than this when precision bombing was working better. 6. So far, my bombs seem to go long a bit. Could be pilot error, but at last I was getting one bomb on target. If this is expected and/or intended behavior, so be it. If so, was the early DCS Viggen just unrealistic with regard to ease of dive bombing? Anyway, I hope this helps. Thanks, Paul

Great work, Capt Zeen! Thank you. Paul

Thank you for the quick response, Nicholas. I appreciate it very much. I didn't think a fix would bypass the beta stage, but I wasn't sure. So, as odd as it might sound, I'm glad to hear it's not in the stable build. Take care, Paul

Was the fix for this issue supposed to have been included in the recent stable release 2.5.2.19682? Precision bombing is behaving a bit differently, but still not correctly as far as I can tell. Thanks, Paul

Thank you, RagnarDa! I appreciate the quick attention to this. Sincerely, Paul

Pop up to the post HERE. It has a link to a DCS-BIOS profile for the F/A-18C. However, it has not been enabled in DCSFlightpanels. ArturDCS would need some support to buy that module. Without it, he can't do the integration. Thanks, Paul

I believe it started after a change that ED made to weather related code, or something along those lines (barometric pressure, or wind, etc.). Heatblur had fix for this in a later beta build and it seemed to be working better. That fix, I believe, was to be in this most resent stable release. I haven't tried precision bombing in the beta recently, which has itself been updated since the fix for this issue. Thanks, Paul

This is exactly what I would see at times as well, late drop cue and bombs going long. I never would see the blinking lines as the symbology was off the HUD by then. It hadn't occurred to me that the drop cue might be late, but it fits with what we're seeing. Thanks, Paul

No problem at all, and I readily admit that I want to keep Heatblur on the hook and not assume that an easy answer has been found. I have put quite a bit of time into testing this and feel strongly that it's just not right. Nevertheless, pilot error is certainly possible. Thanks, Paul

Thanks for taking time to test this--very much appreciated. I will do more testing as well and I'll be anxious to hear what Nicholas comes back with. Regarding the reticle and timing, I am careful to place the dot on the target before arming the trigger, but a good point nonetheless. Paul

Thanks Nicholas. I appreciate the support and look forward to your feedback. Paul

Thanks for taking time to test this, surstromming. I spent more time testing as well and just can't seem to stop the symbology from drifting off the HUD to the bottom. I agree that shallow angles diminish the issue, but it doesn't completely go away for me. Maybe the original flight model was too easy, but this just doesn't seem right. I even raised the virtual seat in the cockpit and lowered the HUD screen angle to try to keep the symbology in view and that didn't work. Thanks again, Paul

Thanks surstromming, I appreciate the response. I have asked a friend to test it as well to help see if it's me or, possibly, the module. Paul

Precision dive bombing still does not seem to working. The aiming cues are still drifting off of the HUD toward the bottom. This never happened when this module was first released. The QFE is set properly and I have tried quite a few aim and release profiles, i.e. steep and shallow dives, fast and slow. It just seems off. If it's pilot error, so be it, but as I said, it used to work perfectly. I am flying in the latest non-beta release, 2.5.2.18736. I would very much like to hear of others see this as well. I realize it could simply be pilot error, or lack of ability. Thank you, Paul Marsh

The video on working with formulas has been posted. You can see it . Thank you.

The video tutorial on working with DCS-BIOS has been posted. You can see it . Thank you.

Hi Kostya, If the original key command you want to map is RALT + L, that is the correct way it should appear in the DCSFlightpanels text file, i.e. what you have above. Paul

Yes, this is a little quirk of DCSFlightpanels. LALT shows up as LMENU and RALT as RMENU, and you can't make a key combination directly. You can fix this manually. After you press LALT or RALT for the switch you want to map, and with LMENU or RMENU showing up in the field, save the profile. Now, click on the note paper icon to open the profile in a text editor. Find the panel and then the command line with "LMENU" or "RMENU." Manually enter the key stroke after that. For example, if you are trying to map LALT + R, you would type exactly the following after LMENU in the profile: " + VK_R" To be clear, that's space, the + symbol, another space, then VK, underscore, R. VK stands for Virtual Key. Save the text profile and then reopen it in DCSFlightpanels. The full mapping will appear as "LMENU + VK_R." Hope this helps. Paul