Bacab

Hi everyone, I have built a "pocket" instrument panel using x27.168 steppers, an oled screen and two arduinos (UnoR3 & Pro mini 5V) linked through I2C. Since I only want some basic data, I chose to use the common data plugin. I tested it in the P-47 (no luck) and in the F-5 (it kinda work). It seems like most of the time the instruments are showing the correct value however they regularly displays completely incorrect values. I can't see anything weird when I check the values in DCS bios web interface so it could be my programming on the arduino's end. However I find it odd that as soon as I press the pause button all the instruments that were showing abnormal values go back to displaying correct data. Do you have any idea of what may cause with this kind of behaviour ? Thanks for the help. EDIT : It's working now ! The issue was a dynamic allocation in my code that was not freed and only occurred when the altitude was changing, hence why It worked when the game was paused.

Hi, As said in the title, in the "Rhubarb radar raid - Wels site" mission, the AI wingman systematically crash into my plane or into an other AI while taxiing. Moreover your wingmen try to take off as soon as possible, not waiting for you and then announce they are RTB as soon as they are in flight. Currently I have been able to complete the mission once by modifying it so the player's group is immortal while on the ground and by preventing the AI from taxiing before me by racing them so I can take off first. I'm playing the OB v 2.7.2.8165 I can't post a track file since, while only a few minutes long (due to the unskippable briefing), it already weights more than the 5 MB limit. Instead I have attached three tacview tracks Here are several screenshot of the issue in action: Tacview-20210626-140710-DCS-P47D-RRR-CHANNEL.zip.acmi Tacview-20210626-140131-DCS-P47D-RRR-CHANNEL.zip.acmi Tacview-20210626-100024-DCS-P47D-RRR-CHANNEL.zip.acmi

Hi, I tried to do the Yarwork mission for the P-47 on the Channel map twice and each time I had a CTD while approaching the coast south of Boulogne. I have been looking at the log and the error seems to be : 2021-04-18 07:40:16.949 ERROR GRAPHICSVISTA: Can't open model wheat_green. 2021-04-18 07:40:16.949 ERROR EDTERRAINGRAPHICS41: model "wheat_green" not found Here is the zip file containing the dxdiag data and the crash log : dcs.log-20210418-074048.zip Thank you in advance for your answer

Hi, I am having issues with the ME that seems to be specific to my installation. However I'm unable to find their origin and I would like some help. When I open a mission and select certain flights, I can't see all the flight's controls, there is a grey box instead : If I had an other flight previously selected it shows the controls but the load out page and the preview is the one of the previously selected unit: I tried running a DCS cleanup and repair but it didn't solve the issue. The issue appears both in Opend Beta and in the stable release. I do not use mods but I do use third party softwares : Tacview and SRS. Here is the dcs.log file. It seems to run into an issue with the GUI but I don't know what to do with that info. dcs.log Thank you in advance for your help.

Hi everyone, I have noticed while trying to set up a supersonic interception of a group of Tu-22M3 in the ME that the group does not respect the speed it was assigned in the ME. The instantaneous speed is not the one set in the ME (and in the trk attached even the average speed is incorrect). Sometime one airplane is going faster and sometime it slows down (in the trk attached the 3rd plane is the one whose speed is constantly changing). I've seen this with the GS being locked but also if I try to lock the ETA (with GS unlock). Is this the intended behaviour ? I thank you in advance for your answers. Trk : Tu-22M3_fix_GS_bug.trk Miz : CA-Formation_test.miz ACMI : Tacview-20210108-215356-DCS-CA-Formation_test.zip.acmi I just had the idea of testing this exact same mission with exactly the same parameters but with only one airplane in the group and everything work has intended. Trk : single_Tu-22M3_speed_test.trk Miz : CA-Tu-22M3_speed_test.miz ACMI : Tacview-20210108-220515-DCS-CA-Tu-22M3_speed_test.zip.acmi

Hi, I encountered some weird behaviour while flying the Hornet : I'm in RWS with LTWS boxed. I put the TDC over a "brick" and designate it. Then, with the TDC still over the trackfile, I command an AACQ: As you can see the TDC is over the target but the B-sweep line "jumps" to a far away target during the acquisition process. Then I find myself with the wrong target locked : The track corresponding to those screenshot is attached. I have been able to reproduce the bug several times. The mission I used is "Ode to Mongo". The track was made with DCS World Open Beta v2.5.6.52437. Thank you in advance for your answer. AACQ_bug_F18.trk

This is exactly why I asked the question: just to learn more about the plane, indeed you don't need it to fly but it's always good to know how things are done. I thank everyone for their replies even if the question has not been answered.

Hi, While flying the Harrier I was intrigued by the fact that, though I kept my aircraft aligned with the "commanded heading marker" on the HUD (which is called the bug I think), I was still drifting away from the waypoint. Here I made a mission with 60 kts wind and you can see the "bug" is directing me to the geographic heading of the waypoint and I have to compensate the drift so my ground-track stays in line with the waypoint heading to actually fly toward it. I am pretty sure the "bug" should be drift corrected so I think this is an issue, am I correct ? Thank you in advance for your answer.

Hi, I'm currently learning how to fly the F-5E and I would like to know (out of curiosity) what is the link between the AOA units displayed by the AOA indicator and the real AOA in degrees. Thank you very much for you help.

Just did it. I have missed the "bonus target" since I did not try to refuel but otherwise destroyed the enemy HQ and got home safely. The SEAD component of the flight was useless but the blame is on the AI which jettisoned its AGM-122 when engaged and was subsequently killed. I went for a very low (200 ft) and fast (450 kts GS) level pass. After viewing the briefing it seems I did not load the snakeyes I wanted for this mission and therefore I was lucky DCS do not take into account fuze arming delays otherwise it would have all been for nothing. The Igla shot and missed but the Tunguska shot down my (remaining) wingman (AI is terrible, it didn't use chaffs or even tried an evasive manoeuvrer). I wonder if the EW escort was useful. I agree with those that said the default loadout behave weirdly. I had a very hard time taking off with it because of the yaw it induced.

Depending on the missile seeker it may need a specific waveform to guide (for instance the seeker may rely on CW illumination of its target). Upon detection of this waveform the RWR will issue a launch warning. I was explained that's how the launch warning work in the F-16 for instance. If the missile home without requiring a specific waveform then you should'nt have a launch warning, you'll only know that you are locked. However if the RWR detects a missile emiter then it will display this emitter (likely as the most urgent threat to deal with). More elaborate logic might be used than this simple one but that's a good start to begin to understand RWR. An other way to detect a missile launch is through a dedicated device that monitor the IR signature of rocket engine. (the mirage in dcs has this feature). However I read somewhere that those where prone to high false alarm rate and therefor not as useful as they might be. Envoyé de mon G8441 en utilisant Tapatalk

I don't want to diminish his work but I'm quite sure he is wrong on this one. If you read the discussion on the subject on acig you'll see there is no definitive proof of that anywhere. Envoyé de mon G8441 en utilisant Tapatalk

Ah... I thought it was complete, hence my incomprehension. Thanks for the clarification.

Wait a minute : what is supposed to happen that makes the campaign end here ? I'm quite frustrated I can not go beyond the landing at Batumi.

I had the same issue. Envoyé de mon G8441 en utilisant Tapatalk

+1

Nice ! Thank you for your answer

Is there an update scheduled for the English manual ? There are several "to do" in the document as well as missing translation.

If you want to check, my source is the documentation from SAMSim. Maybe the control of SA-2 systems was handed over to ground forces when it became obsolete as an area defense system ? I have my doubts though. The thing is SA-2 is not intended as a movable asset and I have yet to read an instance where an SA-2 battery was moved to a frontline. Usually they were set up on fortified position to defend strategic areas and could not really move from those positions. So it make little sense to hand their control to ground forces.

The SA-2 is also a PVO asset so I'm not sure about that.

Very good find though I'm wondering why other systems are not mentioned. Thank you for sharing this information.

DBS, SAR,... work fine on the ground where you only have to account for your movement. In order to do that on a moving target it's something completely different.

It's not only a problem of computing power, it's also a problem of resolution. In order to recognize a target by its shape the radar would need a resolution in the order of a few meters, something no airborne radar can do (yet) on an aerial, moving target.

Ausairpower is not always a trustworthy source.

I would like too but so far my search has been in vain.