flavnet

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!!

Please iranian navy must be implemented!! Thanks in advance.

It seems that it is a mysterious new feature of the Tpod, so the TRIG function becomes useless since the laser activates itself 10 seconds after the impact (of course, LTD on is required). But all this is part of the general problem for which the reference documentation is not released in the face of an important update.

Every moment we discover something new about the Litening after the last update. Don't you think it's appropriate that for every update of this kind it's right to release even the reference documentation? It's not a game, it's a simulation.

In short, I will have to go crazy looking for a joystick setting that the F-18 likes to keep it (as he wants) straight ahead to activate the autopilot. A marvel of technique this plane. If I don't position him the way he wants, he doesn't activate the autopilot. And I believed (as it is for all the other simulated planes, among which the venerable F-14) that by activating the autopilot the plane adjusted to the settings I chose for him. F-18: a real step forward in aeronautics!!!!:lol:

Hello everyone! I'm trying to understand for myself (in the absence of any explanation about the new TPOD) how to launch GBU38 on some tanks using the TOO function associated with the designation via TPOD. Before the last update, the operation was intuitive and fun (!). Because first of all the TPOD kept the view on the last tracked target, facilitating the designation of further targets of opportunity near. Now the TPOD after each launch, self-aligns (I don't know in which direction, maybe right ahead) causing the loss of sight of the group of targets and the waste of time (precious) in trying to find and track them. In short, a useful update the last. But it is possible that now something needs to be done to get what was previously the default. Unfortunately, in the absence of explanatory documentation, I dont known. Now I will try to do some tests with GBU12. If the TPOD does not keep memory of the last target point, then we are faced with a major flaw whose solution should be indicated by the developers.

Hello everyone! For me the autopilot of the F-18 has something wrong!!! Many times I happened to activate HSEL and BALT above 300 knots and at 25000 feet in level flight, it almost always does not activate! My "technical" solution (like a real simulation!!): move the stick slightly at random, here it activates again (!?!?). But after a while, it turns off and the plane goes where it wants! Then I try to reactivate it, but nothing, it doesn't reactivate anymore and I have to drive directly right ahead (very funny!). Since everyone, but I mean everyone, DCS World planes that have an autopilot, this works well, so why does ED not deal with this peculiar problem (which has always existed with F-18)?!?! Hoping for a definitive solution, I greet you.