falconzx

As stated in the title. Seems something changed in Link16 compatibility between F-16 and F-18. I red some posts on f18's bug section about some issues they have between them. Nobody posted anything here about what happened on F-16C Link16 in relation of their issue. Seems we see F-18s for just one second on HSD when they spool up the plane, then NOTHING. Other clients F-18s are invisible and we do not receive anymore informations from them. Hoping it helps, Thanks.

You are right, so the problem is that i'm used to doubleclick the central button of mouse, to make appear/disappear the cursor. In fact with FC3 planes i don't have the issue. Before was possible to unassign "mouse 3" from "camera transpose mode", and now even if you disassign it everywhere, clicking mouse 3 activate that behaviour instead of zoom. So the Fix would be Eagle Dynamics to remove that mouse 3 hidden assignation, like it was before this patch.

I'm providing another little track showing the bug happening 4 times! I'm just moving left and right the scanning area. Sorry for the size of the first track, even if short it came up from the Free Flight of instant action mission, i realized now that mission is a little dense. f-16_scan_pattern_stuck2.trk

Noticed that in the last OB "Camera transpose mode" is by default in the opposite function by before: BEFORE 23rd sept. patch: You enter the cockpit, scrolling mouse affect zoom. AFTER 23rd sept. patch: You enter the cockpit and scrolling mouse affect pilot head Z-Position. For me and for all the users that are used to zoom with the scroll (like Saitek throttle scrolls), it's a very annoying change. Just to say, i used to de-assign camera transpose mode to do not press it accidentally when making cursor appear. Expecially because i use trackir to move my Z-position!

I'm encountering this bug even in the previous OB release, so it's here since the middle of august. In this track i'm trying to reproduce doing fast, little random antenna azimuth movements, with the smallest azimuth it's more frequent, probably there's something odd when the scanned area is moved in certain moments of the bar pattern. As you can see, when it got stuck the azimuth is completely blocked, the bars instead continue to loop between two, despite every bar setting. I ensure you, i accidentally have the scan blocked 3-4 times during an A/A CAP mission. It's very annoying. Thanks for the help. f-16_scan_pattern_problem.part1.rar f-16_scan_pattern_problem.part2.rar f-16_scan_pattern_problem.part3.rar

What you miss here is a simple reality: The code of DCS is an old mess, to improve something, you have to break something. You and more complaining guys have just to understand this simple thing.

What you asking for is exactly what the Open Beta is. And, it's called Open Beta for a reason. People are used to play everyday on OpenBeta asking for quality but they confuse what they are actually doing: TESTING, and help ED to find bugs. I don't think ED should do different like this, they have a large community playing OpenBeta and they help them to find issues through their forums. Who is bored of this job can just install Stable and play. Who plays OpenBeta should be warned and should behave constructively. :smilewink:

We're encountering another BIG issue with new 120s in MP, in terms of De-sync and inconsistency of events observed between CLIENTS. If you use those new missiles in a private server and you observe from 5-6 different clients what that 120 does, you will face 5-6 different trajectories, and endings. (in ext views, but it's easier comparing Tacviews) Even some of them observe the missile exploding on target, the target doesn't die. In other different cases, the target tacview shows the missile as defeated doing loops and he suddenly explode without reasons (for him) because the server and the launching client tacview shows a direct hit. Against Chaffs same story, on TACVIEWS of some clients you see that missile turning on chaffs, on some other client's TACVIEWS you see the same missile keep tracking target correctly! This is completely ruining our MP experience, the fake explosion with F-16C's GBU12 was the first symptom of this netcode problems, and we urgently need a fix about it... Another bad story about this NETCODE is the fact you cannot do fast manouvers like High-G barrel rolls, because it generates LAG and because of that you do a missile successful evasion. That's a big problem in terms of realism and MP balance and fairplay.

I confirm those bugs RDR Elev knob STUCK on middle position. :( It was working like a charm before :(

36° Stormo Virtuale Team League: Diamond Squadron Name: 36° Stormo Virtuale Teamspeak/Discord: https://discord.gg/xBJuwVX Contact person: =36=Falcon, =36=Drigo Aircraft Selection: F-16C, F/A-18C, F-14B, M-2000C, JF-17, J-11A Pilot Roster: -ALL PILOTS are from ITALY GMT+2 Falcon Pit Truthkeeper Drigo Evil Dirty Arawindor Witcher® Eircog Majo Rabo Caronte® Wolf® Airwolf® Rafiki® Led® Cisco®

New RWR sounds in 2.5.6 seems very odd, i personally don't like them, preferred the previous, much more efficient, because of a greater variations of sounds. Despite personal opinions, maybe i found a bug, with some slow locking sam stations like SA-8 i found out that the sound of spike is like stopping playing. The launch in the silence could be the thing, or maybe i'm missing some tws or optical tecnology of SA-8 in that case nevermind. If i point straight on, hot on the SAM it doesn't happen, because he's going to launch faster. Here the video of that: https://streamable.com/uihpo

+1 And if you "PCA select" then select a store with AG weapon after selecting an Air to Air mode, you will end with RDO and AA Stuff in PCA page with AG weapon selected, and when you use hotas function to make CCIP appear, so you will have Vertical Scan, Bore and stuff like that with bombs selected. Same happens in CAS (AG-Gun). The workaround is selecting on PCA a button on the first row, like RDO, it will make it turn on the correct page, you have to deselect TAS or RS, then select it again. After this you can have your CCIP/CCRP again. Mirage was i nice module, RAZBAM you are ruining it. I hope it will be a better simulation of it when this hell will end (does it will?). Just a little suggestion: try things before releasing them.

any chance by ED to fix this rotary to absolute rotation knob, like all the others planes (except the f18 )?

I know it doesn't lock, i just saying i tested BFR range on a cold target with my wing. There is no difference in terms of distance of spotting a cold contact, using BFR or not. This is what simply let me think that BFR is not working properly (like it isn't emitting low frequencies) Do tests by yourself and see. Same test can be done on an hot plane, it should appear more far using HFR. I know very well where i'm pointing my radar elevation, i fly mirage everyday i do Air to Air since years. Just use the mirage in real engagements situations, against multiple targets, play with the radar, you will find those random disappearings and those 0.0 on the bottom, as many of radar contacts still impossible to lock using normal TDC.

If RDO shouldn't (and we are lucky it does) , and TDC fails in most of locking (obviously excluding PSIC cases, that are legit failed radar attempts) , i honestly consider this radar unoperable. When i'm sorting targets, and with "sorting" i mean, scanning and locking and unlocking targets to inspect their aspect and stuff, after some lock and unlock i'm unable to see again targets, even if i am sure i'm on the correct radar elevation, and they didn't changed attitude (for example i see the target visually and i have pitch references) instead of them i see that strange false target "0.0" on the bottom. That's so frustrating.

With the last patch, after weeks and weeks of waiting the radar still doesn't have bfr modeled, and still showing in certain condition a "false" contact on the bottom, (lockable with RDO) instead of the real contact visualization. In most of conditions TDC is unable to lock. And a new bug is introduced on PCA, switching between missiles using the PCA-Select from MAG condition now sometimes you lose the RDO page on 530s, and you have to turn off and on again the master arm to visualize the correct PCA page.

Guys, as i reported on a different topic ( https://forums.eagle.ru/showpost.php?p=4040263&postcount=8 ) the radar has huge bugs. To fix this you have to turn STANDBY and ON the Radar to reset the BUG. The ranging on special modes remains broken, no way to obtain a lock on a target in optimal condition at the max specified range. (a big fast su27 hot up in the sky with no cluttering) I wud expect to acquire it at 20nm on SVI and 10nm on Boresight. The theory is: as the radar is able to catch and lock a contact at 25nm on normal scan>lock mode, i assume it see the contact on special modes as well, as you have an hidden scan mode that automatically locks a contact whenever it finds one. So there is no reason to limitate the range like that, special modes are just different radar pattern movements, but its the same radar with the same emission you have when you acquire a PIC lockable target on tws.

BFR is completely broken on this radar rework, it should be an emission wavelenght that give a better ranging on cold contacts and lesser on hot ones, but if you do a fast check you will find it the same ranging performances of HFR (with all the limitations about PIC) Same story for the Horizontal Scan at low frequency.

I noticed the big bugs on the Radar too, i just didn't reported all the bugs i found because i red RAZBAM declaration about the radar that's not what they intended to release ( i wonder about how they don't TRY things before releasing ..) So i'm confident they will fix in the next patch all the problems we have now like: -Negative Antenna Elevation doesn't react to rising axis command, it waits bars to complete before rising. -BFR completely broken, or non-existing anymore. -Loss of contacts, even if the elevation is correct, parameters correct. Temporary fix: turn STANDBY/ON the RADAR to reset and avoid the bug. -Top bar spotting contact indication is barely invisible, i don't think real one is like that...You need a lens to see the little segments on the tails of the contact symbol. -The number of the bars near the antenna elevation indicator on VTB is often un-aligned, expecially when negative. - Special Modes (CCMs) are completely uneffective, if this radar is capable to STT lock an hot target at 30miles, i don't understand why a boresight mode is not capable to find a target more than 4-5 miles. It has a 10miles max range, so il should work from that range in optimal condition. Same story about the SVI mode, 20miles, and you can't find anything over 5 miles in optimal conditions. What's the sense to have 20miles limit then? -Remanence switch and functionality (do we will have it sooner or later?) A radar rework could be a nice occasion to fix it. Probably there's more but i don't remember now.

yes, probably a bug

Dunno if it has been reported yet, i tried a flaps search, i couldn't find anything. Seems this bug came out some months ago, i remember it was working before, maybe when the netcode change something was messed, but the flaps of the other clients are retracted ever. Maybe the extended position data is not passing through the netcode. Thanks.:)

Satal2019 application League: Diamond Squadron Name: 36° Stormo Virtuale Teamspeak/Discord: =36=Falcon#0833 or =36=Drigo#6567 Contact person: =36=Falcon or =36=Drigo Aircraft Selection. J-11A - F-15C - M-2000C - F/A-18C - F-14 Pilot Roster: Falcon (Italy +2 Zulu) Drigo (Italy +2 Zulu) Merlin (Italy +2 Zulu) Evil (Italy +2 Zulu) Rabo (Italy +2 Zulu) Barbarossa (Italy +2 Zulu) Luke® (Italy +2 Zulu) Truthkeeper (Italy +2 Zulu) Eircog (Italy +2 Zulu) Gaanalma (Italy +2 Zulu) Lornix (Italy +2 Zulu) Italicus (Italy +2 Zulu) Edokg (Italy +2 Zulu) Blackeagle (Italy +2 Zulu) League: Gold Squadron Name: 36° Stormo Virtuale Teamspeak/Discord: evilcode#0747 / =36=Falcon#0833 Contact person: evilcode / =36=Falcon Aircraft Selection. J-11A - F-15C - M-2000C - F/A-18C Pilot Roster: Johnny (Italy +2 Zulu) Arawindor (Italy +2 Zulu) Pit (Italy +2 Zulu) Dirty (Italy +2 Zulu) Caronte (Italy +2 Zulu) Cowboy (Italy +2 Zulu) Redshark (Italy +2 Zulu) Scorpion (Italy +2 Zulu)

On multiplayer other clients Su27's slats position, is inverted: when they are open, they are shown closed, and viceversa. Probably Su-33 and J-11 have the same issue

Hello! I started playing DCS more than 4 years ago, i play every day, and since i remember a big(huge) BUG ever brought me during all this time and past hundreds of patches and new versions and modules. Considering the vastness of the DCS simulation, and the depth of its simulation, i can't really understand why nobody cares about a such serious issue. The title explain itself, and who programmed the AI radar locks triggering system knows what i am saying very well. AI Radars (SAM/AA both) modeling is far to be accurate, and keep triggering RWRs of clients even if theres not irradiation. in other words All the time an AI Radar locks something, all the clients that having a positive LoS(Line of Sight) with the locking unit receive the lock warning! I waited years, versions by versions, hoping silently that a so shocking bug being resolved and nothing. I think ED should consider to resolve this very soon to match the same simulation accuracy we achieved on other fronts. Thanks and sorry about my outburst:)

Actually the status now of the landing lights, except for the intensity (that is far more than other modules), is that they never turn off, even when you turn off the switch, the lamp rotates facing the ground and you can still see the light beam on the ground. Hope you guys will fix this