Talonx1

Was dropping them last night with no issues, must be something to do with the bomb codes then. The bombs and the laser are set to matching codes correct? Tried using default codes to see if it works?

I havent seen it happen against npc's buy will give it a test. If it doesnt happen against them the it'll be a little more trouble to setup a mp matchup on a server with zero mods.

Sometimes it is just a jolt. Its maybe 1 out of 10 times the damage occurs. My personal theory is that the turbulence isnt dissapating and is becoming additive as it crosses over itself. It seems to occur more the longer a fight occurs in a given area. I've lost wings in a 7 g turn and I've lost them in a 2 g turn.

The laser is armed and you (have mapped) and are using the first trigger detent to fire the laser while the bomb track to target correct? The L on the pod (lower center) and on the hud should be flashing.

Do not have this problem. I activate my bar using shortcuts via voice attack. If the command uses shift, alt or ctl keys be sure youre using the one on the correct side of the keyboard. Left shift isnt the same as right shift etc. Only thing I could imagine being your problem short of a corrupted install or keybind file. Or perhaps this...https://forums.eagle.ru/showthread.php?t=278663

The f18 is extremely squirrely on take and landing on airfields. No idea why. Do not have the same problem with any other airframe.

His hanger mod is not making it visible, it just caused the baked in glare to appear unique and identifiable due to the location of the highlights on the vertical stabs. In the default hanger when you look straight ahead in the f10 menu the glare off of the mig 29 weapon pylons create a round glare when you go back to cockpit but since its just a round spot it wasnt so apparent what was causing it. If you look up at the ceiling rafters in the default 3d hanger in the f10 screen when you go back to cockpit you can clearly see a terrible glare that matches the hanger rafter outline. Saying this is something basically no one else is seeing is blatantly inaccurate. His custom hanger aircraft just helped track down the issue that most likely is there for everyone in vr by making the shapes of the glare more identifiable. Your responses and tone are a bit rude and uncalled for.

Can confirm that this is the mission that used to flip my aircraft over. Guessing something with mission or model has changed since the viper first released. It no longer flips the aircraft over but it still causes enough vibration to upset INS alignment. If I recall I think the F15's originally taxied from past the player starting point and crossed in front of your aircraft causing the destruction. Now it has been changed so the Eagles startup and taxi on the other side closer to the on ramp to the runway. The turbulence is still so strong though that as each plane takes off 100 meters or so in front of and perpendicular to you, that a few seconds after they pass by the wave of turbulence hits you and unsettles the aircraft.

I believe the only mod should have been maybe the range targets mod that was being used by the server. Dont believe I had anything else loaded. Wasnt aware that could effect track files. Would a tacview acmi be of any help?

Have only seen one vid of a viper being effected but its impossible to tell if he was behind a mirage or something else when it happened. Any hard evidence of it happening when no mirage was involved?

Trying to find a group that is open to flying all different modules. Semi-milsim at best. Keeping it professional is great but not interested in having to fly quarterly carrier quals or groups that will boot you for not utilizing realistic comms when departing a field with 2 ppl on the server. Occasional squadron missions would be good, would like to get more proficient at close formation/exhibition flight and would be cool to find a group interested in participating in intersquad DCS competition like SATAL. Havent had the opportunity to do so myself but would enjoy it. Most proficient currently with the F-18 but also own and working on improvement with the F-14, F-16, AV8, M2000 and F-5. No issues with flying proper case 1's and AAR. Could probably use more case 3 practice. Have flown with a couple of different squadrons and have never departed on bad terms, just trying to find that goldilocks group. :helpsmilie: Edit: Almost forgot. Timezone is Central US. Usually on between 2100 and 0000 just about any day of the week.

https://forums.eagle.ru/showthread.php?t=278514 Mirage is causing other aircraft to lose their wings as well.

Anyone know what that f16 was chasing down in the video on page 1? Atm I'm betting it was a Mirage. See thread...https://forums.eagle.ru/showthread.php?t=278514

Were you in a mirage chasing the mig? Was the F16 chasing a mirage? I agree in that I think turb. is overpowered, but I havent yet seen a wing rip that didnt involve a mirage on one end of the exchange or another. And I've seen and documented quite a few now.

Sharing this info from a thread in the 2.5 forum. Since all accounts I've found involve the mirage in one way or another I thought it should be shared here for Razbam to see. Track files is 28mb so I can't attach it here directly so I will link to an upload below. Is video of one of 2 wing rips that happen in that track file. https://drive.google.com/file/d/1VNyd09d8JbLIz9xOJZOZprpsmpx1KrjY/view?usp=sharing Is a link to the track file. The first rip is just after 13:33 and the second is after 13:37. When I tried to make a video though the second event doesnt show the visual effect. The aircraft just starts to lose control. When it happened live however I didnt know the wing was gone and couldnt figure out what was wrong till the others told me my wing was gone and I verified it visually when I looked over my shoulder. I was floundering around at the end w one wing until the mirage fired a missile and finished me off. The first event happens to callsign "Loot", and the second happens to callsign "Talon". Realizing now that every event in which I've seen a wing rip off in turb involves the mirage. It both loses its wings and rips off other aircrafts wings. I will also post this info in the Razbam subforum and also intend to make a track of the mission where the F16 is blown over in the parking area at mission start and post it later.

Track files is 28mb so I can't attach it here directly so I will link to an upload below. Is video of one of 2 wing rips that happen in that track file. https://drive.google.com/file/d/1VNyd09d8JbLIz9xOJZOZprpsmpx1KrjY/view?usp=sharing Is a link to the track file. The first rip is just after 13:33 and the second is after 13:37. When I tried to make a video though the second event doesnt show the visual effect. The aircraft just starts to lose control. When it happened live however I didnt know the wing was gone and couldnt figure out what was wrong till the others told me my wing was gone and I verified it visually when I looked over my shoulder. I was floundering around at the end w one wing until the mirage fired a missile and finished me off. The first event happens to callsign "Loot", and the second happens to callsign "Talon". Realizing now that every event in which I've seen a wing rip off in turb involves the mirage. It both loses its wings and rips off other aircrafts wings. I will also post this info in the Razbam subforum and also intend to make a track of the mission where the F16 is blown over in the parking area at mission start and post it later.

Only time I've seen the improper comms procedure is when the airboss scripting is active on a server mission. Procedures for landing w airboss are a bit different and have to be done through its dedicated menus. Make sure you are actually within 10nm though when u call see u at 10. I think i did get improper procedure once for that. Otherwise make sure you are on the proper comm channel. Could also be the problem.

If I'm not mistaken the icls isnt meant to be flown all the way to the deck. Procedure should be to follow needles till you can pick up the ball then follow the ball in the rest of the way. Someone much more knowledgable than me once said mentioned that icls isnt lined up for the trap point on the deck the way the iflos is. Its just there to get you in range so that being the case, the icls will not match ball indications by design. I'm certainly in agreement about the overlay amd find it too large and distracting. They already said they plan on an option to disable it but also hoping they provide a scale option. https://forums.eagle.ru/showthread.php?t=277591 Also, see this thread. Whether or not something is off w the iflols or not there def seems to be enough ppl having issues with their traps when relying on it that it warrants investigation. Curious if the ppl having trouble are using the overlay or physical ball.

Set up a mission today to start comparing the 2 carriers to see if the difference is real or just perception. Have only got to do one run so far. Straight and level approach from the stern @400ft. On both carriers, observing the physical ball on the deck, the low red ball appears at 1.1 nm. So can confirm the lower edge of the visibility cone matches for both. Plan to test the center ball and upper limit of the physical iflos still and then compare the overlays and confirm that they match what is seen on the physical system. Not even going to comment any further on what it feels like is happening. Just going to share the test results. Have to also consider that its at least in part due to the size difference of the carrier causing sight picture issues. Particularly if youve spent a lot of hours on the old carrier beating the sight picture into your brain. Happy to admit I was wrong initially if my own tests dont end up supporting a real issue.

It did devolve into sounding that way, wasnt the initial response intention however. As for replays I wouldnt trust track files. They are notorious for completIy corrupting what actually happened. I would make a live recording and take care to show instrument readings during the pattern.

As I mentioned before I havent done any detailed analysis but my own experience is that the SC puts you higher than normal on glideslope as you cross the stern and into the groove then drops at too steep a rate as you get "in close." Entering the groove should be happening at <400 ft but that alt on the SC will immediately put you low on the ball and have the lso calling you low. (And thats with an appropriate groove time) A dropping ball in close wasnt uncommon on the stennis but it seems to happen more dramatically and further out. It ends up causing me to have to adjust and add power to prevent hitting a 1 wire or worse which is probably what causes the occassional float over the wires. Then the way the game hangs for up to 2 seconds when getting over the deck (which is documented in other threads) compounds the situation.

Not making it personal, responding to the condescending "get good" response. Issue is seen by many ppl who have no such complaints about the stennis. Responding by trying to brag how good you are and that everyone else is just at fault cause they arent good enough without any knowledge who youre talking to or what their skill level is is uncalled for. But yes, personally I havent had time to put together a full study into the matter with tracks/video cause summer time and family only leaves so much time for dcs and I'd rather spend it blowing stuff up than doing ED's QA work for them. When I get the chance I'll do so but atm I'm just sharing my own experience and that others I fly with have made the same complaints. When I look on the forums and see others talking about the same issue its pretty apparent its not a matter of "getting good." And if youre low and youre aoa is too low as well then yes, youll overshoot. Which is why I specifically pointed out that its happening on the ball, trimmed for on speed aoa and at an appropriate descent rate.

If the lso and ball are calling low, youre trimmed on aoa with proper descent rate and you fly over all 4 wires theres a problem. Because surprise ego, that means technique is there and the problems is with the new SC which btw is wip btw. I trained and qual'd w a prominent squadron and have flown natops case 1's since the hornet released. My traps are probably somewhere in the 1000+ range. There is an issue and the fact they have even stated the tomcats slope was incorrect should be all the backup needed to support that its a wip. If your traps are sloppy enough that you cant tell a difference perhaps the problem isnt that youre so good it doesnt effect you but instead that your so sloppy you its masking the problem.

Theres always someone w an overinflated ego with no knowledge of the skill level of other pilots who are speaking who had the nerve to step in with a "get good" comment. SC ball has issues and is not accurate. Can trap perfect case 1's w a center ball and a 3 wire all day on the stennis. On the SC its a crap shoot anywhere from a 2-4 wire. The SC lso and ball are not reporting proper glideslope OR the stennis ball was setup in such a way as to make it easier or more accurate than it should be. Either way theres a disparity.

Can attach MP trackfile from last night possibly. Which logfile?