captain_dalan

@BIGNEWY Late arrival here, so sorry if i act like necroing the thread. Just a personal opinion, but IIRC, we almost never take into account camera footage, be it a video or a photo, to be indicative of real life visual conditions. For a number of reasons as well, not the leas of which would be eye adaptivity. So if we decide on how to treat the laser lineup, i would be all against using those as reference. Could we stick to first hand accounts and SME's?

Hey mate, thanks for the heads up! I managed to miss this one

Hey guys, after the latest 2 November patches, i find the SC deck alignment light barely seeable on a sunny day, even when the sun isn't shining directly at it. This makes it almost useless when flying the pattern, until you get really close, by which point is too late, or when flying at night or in late afternoon. Is this a bug or a feature? That is, is this how it's supposed to be? I remember a few patches ago, we could see it clearly, especially when it was blinking from a couple of miles away. Here's some screenshots from the current state (notice the light is actually in the shadow): null

Good to know! Thanks mate, could be something on my side then. Also, i just noticed a new patch came out, i'll run the updater first, and try again. Cheers!

Yep, the scripts don't launch, ST and MT checked

@all Really? No one is flying the F-14 anymore?

Thanks!

I thought it was just me. At the same time, glad and sad to see i'm not the only one

Yes, despite first hand accounts of the AIM-54A being more resistant to CM then contemporary Sparrows (we are talking pre AIM-54C era here), ED has decided to make them worse. Hooray! Just learn to live with it. We are living with UFO AI's and Unobtanium powered Hornets. Is it so hard to live with a Phoenix that prefers not to hit its targets?

Hey guys and @IronMike, is this just me? Latest OB, MT. When the Phoenix goes active, the flashing numbers are now more like blinking. If so, is this a feature or a bug? Also, the carrier flashing lights no longer work, so may be related? Made a short video as a showcase:

Roger that. Do update on your situation. I'm also curious on this bug, as it's only a recent development for me

Can an admin please merge these threads?

I generally don't use external views that much, but with the latest changes that 2.9 brought, while calibrating LOD and Sharpness sliders in DCS i noticed something odd. Namely, the texture around the rear of the left engine nacelle flickers from damaged to non damaged. I attached some snapshots bellow. This happens by default in instant actions and missions as soon as you load one. Usually the plane will spawn with damaged texture on. Wait a bit or rotate the camera around, and the texture will switch to non damaged. And then back again and so on. Has anyone else noticed this as well, or is it only on my side? Also, @IronMike, could this be related to the elusive bug of the F-14 sometimes respawning with a dead engine requiring another mission reload to fix it?

I've been experimenting with something on the latest build (2.9). If you experience this on any mission or campaign, open up your pilot log page inside DCS and change something trivial about it. Like say..... squadron. I had another issue after the update to 2.9. I had to uninstall Sinai map to update, as i ran out of SSD space. After the update finished, i installed Sinai again, but some missions on the Persian Gulf, wouldn't work because of hanging load times. And these were build in Instant Action missions. Nothing fancy or custom made. I changed my squadron in my logbook, from VF-1 to VF-143 and tried to run the missions. They loaded without issue. I tried my only active campaign (Zone 5), and that worked as well. I've only tried Through the Inferno MP thus far and that loaded without issues. I can't say for sure, as there a loads of missions i haven't tried yet, especially with multiple aircraft, but if a stumble upon a loading issue, i'll try to record a video about it. Hope this helps!

Thanks mate! It's funny that you mentioned the DLC. Most (ot of the few) viators i've had the chance to interview or ask about it, recommended using it only in few short bursts, usually when starting high, to correct the glide slope lower. However, having the luxury of an axis to assign to it (i use a Virpil TFX stick), i find myself repeatedly using to make very fine adjustments of the slope, often VERY minor. Like.....say, 10% or less of total possible input. And i use it to increase lift as much, if not more then to decrease it. That being said, i almost never resort to full DLC up or down, but only partial inputs and then the spring-loaded axis auto-centers. I have an occasion used a continuous input as well. At times, i just can't seem to find the proper trim or engine power, and while i'm in the groove i may, say push the DLC wheel a wee bit down, to spoil the lift for the amount my trim or power generate extra. Those are very small corrections though. Seldom more then 1/4 or 1/5 total axis input. As for the auto throttle, i've never used it myself. Neither in the B, nor in the A that i usually fly. I don't even have it mapped on the my hotas. Heck, i don't even know where in the cockpit it is! I just don't trust auto-anything in the Tomcat all that much. Be it throttle or pilot! Yeah, you are most likely right on the IFOLS. I think it's a long standing issue to, at least for the A. I'm not sure if they ever fixed it for the B, as i haven't flown a boat operated B in more then a year now

Yeah, probably won't work in the wires on in the groove, but i'll give it a try.

Might go for something like that the next time i try it. No idea, how DCS simulates B-1's RCS, but if anything close to RL, i'll get tracked and locked long before they do. At least in the F-14....

General questions to the community. I'm a few months of DCS hiatus, i'm returning to it, and after re-qualifying myself for carrier ops, i decided to give some of the missions that come with the F-14 and i haven't flown before, a go. In one of those, the Bones escort a flight of.... well, "Bones" to Tbilisi on a strike mission. Most of the mission goes largely uneventful, until a pair of Fulcrums goes hot on you some time after reaching steer point 2. So far, so good. Not much difference then a fighter sweep. But then, after you dispatch the MiGs and you proceed to Tbilisi, the SAMs start paining you. And if you continue on the course to SP3, they will open fire, first the SA2 and then the SA3. My question: What to be the proper doctrinal response to such a scenario? In fighter sweeps or CAP missions, both in SP and MP, i tend to stay away from them, and if they start engaging, i usually go perpendicular or sometimes even cold to them. If hard pressed, i may even dive for terrain cover. But do we generally do when we escort packages? Do we leave them alone and hang behind? Do we leave them alone and go around?

OP, is the carrier moving at the time of launch? And is it moving against the wind if any wind is present? Sometimes MP missions don't have any wind.

My pleasure mate! Wish i could be of more help, it's a real pain to reproduce, as sometimes it won't appear for hours, or even days of flying If i found more clues i'll post them over here.

Hey guys, new personal best! 69! Next step, 70+ !!!

A bit of appreciation and bragging on my part! Just scored 69 (no innuendos here) on Bankler's Case I recovery training in the A! And i feel over the moon! To think what got me was the groove time.... and i thought i had those mastered Enjoy!

This bug is a long standing, and it happens to return with variable frequency from patch to patch. When starting a mission for an N-th time, either by selecting restart or selecting fly from the mission menu, sometimes an F-14A will freeze after clicking ok/fly, with a "thump" sound being followed by the engine loop. It can happen in MP and SP, and it can happen in MT and ST. Sometimes it happens every few restarts, and sometimes it takes dozens of repetitions. I found the easier way of reproducing the bug is to re-fly my modified version of Bankler's CASE I recovery trainer. I will attach the mission bellow for those interested in trying to reproduce the crash. I also took this short video as a demonstration. I was originally recording my landing sessions in order to review them the next day and make proper corrections to my technique, but i was lucky (or unlucky enough, depends on how you see it) to have 2 separate occurrences in relatively short succession, so i decided to publish them here in hope of making it easier to reproduce the bug. Looking forward to your inputs. No tracks are being attached, as naturally, DCS freezing prohibits tracks from being saved. Bankler's Case 1 Recovery Trainer_v07-20_Supercarrier_A-4C F-14A.miz

A bit of a necro here. I recently got this kind of load freezes, after buying few new modules in the recent sale. I got the Mosquito, the Mustang and the Apache. I never had the bug happen to me before. Now it happens from time to time, both in campaigns and standalone missions. Sometimes renaming the pilot log to a backup, generating a new log and then replacing the content with the old one helps. Sometimes it doesn't. I experiment with editing the log right now, to see if it helps. But it sure is annoying to have a mission fail to load, seemingly randomly.

I'm not sure if this has been asked before, but are there plans for a Forrestal version of this mission?