flavnet

Hi! I bought the F-14 Heatblur on 08-10-2018 (directly from Heatblur). I just updated 2.5.6.57949 Open Beta. Wanting to try the F-14 A, with the mission editor I create a simple mission (only the F-14A aircraft already in flight). I notice that in the box showing a preview of the plane, F-14A it's exactly like the first F-14A (the non-Heatblur one!!). In fact, when I try to start the mission, the game crashes. The F-14B works perfectly, even if - after the update - I had to re-binding controls. Help would be appreciated. Thanks.

A huge thank you Chuck!!!!

Excellent explanation Fri13! Thank you. Now I understand why it is correct for the GBU-54 to turn on the laser in the last 15 seconds before impact.

I've done some practice missions with the GBU-54. Indeed, it is essential to activate the laser about 15 seconds after impact. If you do that, the bomb works perfectly as an LGB.

Indeed, I had some problems with the GBU-54 being used as an LGB. It happens to me that the first release is inevitably lost, even if the laser is activated in a time between 20 and 15 seconds from impact. However, the releases following the first work perfectly. Very strange. However, I prefer to use the GBU-12 which is very reliable.

Hello! I will try to summarize the procedure for using an LGB with the A-10C II. This is a much simpler procedure to perform than to illustrate!!! For this, I will limit myself to the basic steps, those necessary to get to the KABOOM! First, if the mission starts from the ground, it's necessary to verify that the laser code of the LGB (by default "1688") is identical to the one stored on the TGP. Generally, this alignment is by default, but if you want to set different codes, I recommend reading Chuck's wonderful guide on the A-10C (the "I", the change of codes happens the same way). We turn on the TPOD so it can have plenty of time to boot. When we are in flight (altitude at least 20,000 feet and speed at most 200 knots) and we approach the target area (which we have been careful to make a waypoint), we see the TAD screen (left) and make it SOI (coolie left long). We use DMS AFT / FWD to cycle the range and set the range to display the waypoint on the TAD. We use the HOTAS SLEW directional controls to move the TAD cursor over the waypoint, which is the target area. Let's make this point SPI (TMS FWD LONG). The wedding cake symbol appears on the TAD screen at the target waypoint and on the HUD you can see a small square with dashed lines pointing to the direction of the waypoint. Let's set the TAD range to 20. This phase is important to search for the target in the waypoint area. If we haven't already done so: Master Arm ON, Laser ON, TGP ON and GUN PAC ON (if we want to do some healthy BRRRRRTTT). On the TAD screen, as soon as we see the target waypoint appear at the top, on the right screen we select the TPOD and push the AG button. The video appears in CCD mode (default). We push the CNTL button and select LATCH ON and then RTN. With LATCH ON we make the laser modal (push the laser button to activate it and push it again to deactivate it). Let's make the TGP SOI (coolie right long) and start the research and tracking phase. Now the TAD at range 20 is useful. On the TAD the TGP sensor is represented by a small diamond. Then, using the HOTAS SLEW directional commands, I see this symbol move across the TAD. I just have to get this symbol right on the wedding cake and I'll see the target area on the TGP screen. So I start the search for the target using HOTAS SLEW, china hat fwd short (cycle FOV), DMS FWD / AFT (zoom in / out). To locate the target, it may be useful to cycle through the various video modes: Boat Switch FWD (FLIR BHOT), Boat Switch AFT (FLIR WHOT), Boat Switch Center (CCD). When I find the target, I have to track it. With the TGP sensor on target, I push TMS FWD SHORT and cycle between Target Area (AT) for fixed targets and Point Target (PT) for targets that can move. We assume that the target is a tank, so it must be tracked with PT (on the TPOD a small square appears on the tank and follows it). Now let's go to the screen on the left and select DSMS. Among the various stations, there will be some with LGB. We assume there are 2 GBU-12s, one at station 4 and one at station 8. Push the corresponding buttons on the sides of the left MFD to select stations 4 and 8 (the station symbols on the DSMS turn green). I omit to illustrate all the features of the weapon profiles (this post would become an encyclopedia). With the MASTER MODE CONTROL button, I cycle the various release modes and select CCRP. At the center of the HUD appears "CCRP" and its symbology: the double circle (CCRP PIPPER) and the two lines. One line (the one starting from the top of the CCRP PIPPER) is the Projected Bomb Release Line (PBRL), the other perpendicular to the designated target is the Azimuth Steering Line (ASL). At this point the situation is as follows: left screen DSMS, right screen TGP rendered SOI with the target tracked PT. Now it’s FUNDAMENTAL to make the TGP as SPI, that is TMS FWD LONG!!! The SPI is indicated on the HUD at the bottom left and "TGP" should appear. You fly level and maneuver the jet to align the PBRL with the ASL. At about 6-8 seconds from the release time (you see this release countdown on the center left of the HUD, near the "L" which indicates laser activation), a small circle (with the same countdown in the middle) is visible and he falls from top to bottom along the ASL. As soon as you see this small circle fall, press and hold the release button until the bomb automatically detaches (release can be verified by viewing the DSMS screen). In the central part to the extreme left of the HUD, next to the "L", you see the impact countdown. At a time between 20 and 15 seconds from impact, you must activate the laser (push the NWS button). The "L" on the HUD flashes and after 15-20 seconds ... KABOOM!!! IMPORTANT: after impact, turn off the laser immediately (push NWS again) otherwise the sensor will burn and goodbye. With the TPOD aimed at the target area, other targets (other tanks) can be searched. It will no longer be necessary to make the TGP as an SPI (it remains that way), just trace (as a PT) the next targets, drop the bombs (until the selected stations have bombs), activate the laser until impact and remember to deactivate it. I wish many KABOOMs to everyone.

Great! Many Thanks!!

Syria would be the ideal theater for the Israeli Barak! The idea is not new, but it seems difficult to implement it as a mod of the Viper. As for the Sufa, I think it's impossible to see it in DCS World, considering the characteristics of secrecy surrounding it.

https://forums.eagle.ru/showthread.php?t=288389 It seems that the problem lies with the release altitude. Above 10,000 ft (roughly), there are problems with the laser pointer (apparently it does not drive as it should the bomb falling like dumb). Evidently, when I managed to hit the target, I was about 10,000 ft. altitude, while when I failed I was well above 10,000 ft. (I generally throw LGBs and JDAMs above 20,000ft). I humbly point out that it makes sense to speak of "smart bombs" if they are dropped at a minimum of 20,000 ft. I think it would be worth checking if what happens may be due to: - a bug, - a feature wanted by the developers (and about which I don't think I'm the only one to be against), - my mistake in the procedure for using LGB bombs. But I have followed what is written in the manual! Therefore, it would be right to repeat the correct procedure for using the LBG with the new A-10C.

Hello! The same behavior you described for the GBU-54 happened to me!!! So much so that I thought the bomb only worked as JDAM and not as LGB. In fact, I usually release above 20,000 ft. I tried using the GBU-54 several times ... frustrating!!!! The bomb hit stationary targets perfectly (JDAM - without using the laser). But if I tried to hit moving targets (TPOD in point) with the laser, the bomb would fall like dumb. I posted a thread complaining about the problem, but it has been put aside. I hope that the developers notice that's problem or they tell us how the bomb should be used in the right way.

Hello everybody. The "incipit" may seem strange, but it's much stranger that using the same procedure (the one indicated in the manual) in the same mission but in four different sessions: once everything goes ok and the LGB hit all targets, the second once the bombs hit nothing, the third the LGBs hit the targets and the fourth nothing. I've always followed the procedure. I think it's worth doing a little more testing. Also, the GBU54s seem to work only as JDAM. Thanks for your kind attention.

Bello!!!!!! Bravo!!!!

Benvenuti!!!! Evviva l'MB-339!!!!

Chuck ... the Best!!!!!

Maneuver vertically. Hit and run. The Viper can maneuver more easily in the vertical plane (more power-weight). Avoid fighting on the horizontal plane. The Mig is much more of a maneuverer. However, in dogfight the result is not obvious, it depends on many factors (first of all, who is the pilot).

Thank you! I will investigate and if I can get something, I will let you know, why surely you are very good on liveries!!:thumbup:

Excellent work BarTzi!!! I'd like to ask you a technical question. There are some details (I mean only aesthetic and not functional) that differentiate the Barak from the block 50. Could it be possible to reproduce these details? For example: enlarged tail fin, larger RWR behind the radome, absence of IFF slice antenna, etc. Again, it would only be aesthetic changes on the simulated F-16 model. Thanks in advance for your kind attention and congratulations on your work!

Please update the Mustang pilot model. The current one looks like a "sunday driver".

I agree, if it were a single module for which a certain fidelity is required compared to the original. I meant rather a version of the existing DCS Viper module. The Israeli F-16 C block 40 (Barak) is most similar to the F-16 C block 50 simulated in DCS World. Aesthetically the major work would be the dielectrics and the tail. As for avionics, neglecting systems still covered by secrecy (like the ECMs - moreover, not even simulated on the DCS Viper), it could simply be reduced where necessary and implemented where possible. For example, the Barak does not mount any type of AMRAAM, while it mounts the Python 4 missile which could be a new addition to DCS World. Still, Barak were originally fitted with the Sharpshooter pod, which is a downgraded version of the LANTIRN targeting pod. The Sharpshooter pod were later replaced by the Rafael Litening pod, which is precisely the one simulated for the DCS Viper (with limitations). The Barak is equipped with HMD (called DASH). JHMCS symbology can be used. The Syrian scenario could also be animated by Turkish F-16s. Their shape is similar to that of the Baraks. So, there would be an additional version of the DCS Viper. In short, why not?

Very nice map with landscape rich in details. The only discordant note is the F-16 which is not the Israeli one. It would be very nice if the Israeli F-16 C model was made available along with the map.

Hello everyone! The trim problem, in my opinion, depends on the deadzone setting. In fact, it would be necessary for a goodwill developer to check the correct functioning of this setting. I set the deadzone of all WW2 planes to 10 and I noticed that there is a huge benefit in terms of controlling the trim. The only plane that does not respond to the deadzone setting is the Spitfire! Even if I bring the deadzone to 20 the plane is uncontrollable!! As soon as I touch the stick, the Spit stalls!!! So it's clear that there is something wrong with this plane in the setting of flight controls. I'm talking about the openbeta DCS 2.5.6.50979 (the latest version). I hope for a solution because all the other WW2 planes don't suffer from this problem. The best of all in terms of trim control is the P-47 (perhaps not surprisingly).

Hello everyone! One question: it seems to me that the PP mode for target acquisition with SLAM is not satisfactory. Even if I enter precisely the coordinates of the target, the missile hits the ground nearby and never the target! The coordinates are correct (they are the same as the waypoint identifies). So, I have to assume that the missile has a GPS problem (perhaps simulated to respect the status of the weapon at the time it was in use). On the other hand, terminal driving with the radio pod would not make sense. However, if I designate the target via TPOD, the missile hits the designated spot perfectly. Strange!

The only way I can hit something with SLAM is by using the coordinates (PPmode) or by using the TPOD (which transmits the coordinates of the target). The radio pod is useless. Currently, in the absence of satisfactory instructions on how to use it (even the symbology is mysterious!) I will not use it (and I don't think I will be the only one). Moreover, I also tried to use the radio pod in what should be the smartest way: once the missile was launched (at about 50 nm from the target), the airplane with autopilot should make a large turn in order to not enter the enemy MEZ (near the target). Well, the radio signal is interrupted and the TTS countdown no longer appears. Of course I am wrong, but there is no reference to help. I await Chuck and his precious guide. In the meantime, I use SLAM as a more advanced JSOW.

I have scrupulously followed Matt's video instructions on the use of SLAM with the WPDSG system (waypoint designation system), with all the settings indicated. I launch the missile when in range and wait for the TTS countdown (for the seeker). The seeker is activated and the missile begins a dive but shortly afterwards begins an almost vertical climb and goes beyond the target! It would be enough if the missile continued the descent trajectory to hit the target!!! Why does it go up and leave?!?!

It is the usual problem. Updates to the systems come out and they are NEVER accompanied by reference documentation, but only by Matt's beautiful videos. Unfortunately, I (just me eh) can't study a video while I'm flying the plane and try to understand how the various systems work. Perhaps with a paper reference it would be all easier. For example, I (and not only me) find the work of the great Chuck wonderful, who with his guides literally taught me almost everything about the planes present in DCS. Let's wait Chuck for SLAM!!