All Activity

I don't doubt there is a problem. I'm just saying that a screenshot is not enough. Let's say the bug goes like this - this is a hypothetical scenario: I have the following snapviews (file attached to the post). I load the following mission (attached in the post). NOTES: The mission is a minimal mission for practical reproduction - that is, a single Player-skill plane, if that is enough to replicate the issue. If it's not plane-specific, use a free Su-25T or TF-51D. Of course, if it's only with some plane or some map, use those. I do this and this in a mission. (Trackfile is included in the post.) I leave the mission and check my snapviews and see that the modification date was updated. I can also see the differences (tools like diff or WinMerge). And again, the modified file is attached to the post. Now somebody can try it and say "yeah, I see it now" - or, sometimes frustratingly, but happens as well - "sorry, it works on my end". And the process can follow one way or the other. Screenshots and videos are welcome additions, but not enough. Does the process make sense?

I just ran a test and I had no issues launching the ATACMS. Make sure you're inside the allowed launch sector, the most common issue is trying to fire when pointed straight towards the target.

looks great good job man

Hi, Inside each %USERPROFILE%/Saved Games/DCS.serverN/Config/options.lua file find the following option: ["Tacview"] = { ... ["tacviewExportPath"] = "", ... }, Does that work for you? For your other questions could you please email us at support@tacview.net ?

No you can't* and that's not what this thread was initially about. All the talk anout the wind derailed it, albeit one can assume two SEPARATE issues discussed here might be somehow connected in the code. The issues are: 1) Inability of the tail wheel to caster freely while unlocked, which makes making tight turns with diff brakes (ie. taxiing out of parking spot to perpendicular taxiway) impossible unless you use full rudder + stupid amounts of power to literally scrape the tailwheel sideways across the ground. Simply put - tailwheel always remains locked either fully or partially (ie. it kinda unlocks but to about 30'ish degrees only). Watch the video of the real thing posted by Super Wabbit on the previous page. Wind or no wind, It's impossible to do the same sort of turn in DCS Corsair right now. * Makind mild turns with rudder only as in DCS Mustang is perfectly doable indeed, but that's not what we're talking about here. 2) Some excessive weathervaning caused by adding wind component to the mission. What wind speed threshold maxes turning impossible is still to be determined. I would also add a third issue of tailwheel getting stuck hard in the mud if one incidentally rolls off the runway/taxiway on some maps, which makes the plane very difficult to get moving again, but It's a different issue and I don't want to derail the thread myself.

Good morning! I had Windows 10 on my computer and was updating DCS without any problems, but I recently upgraded to Windows 11 and when I tried to update DCS, the following error message appeared: “Curl error (35): SSL connect error.” What does this mean and what is the solution? Thank you! Paul

Use one or the other. Not both. It doesn‘t break anything, I guess, but it might add up onto one another which might not be the desired effect.

ED let us set the render distance from bushes an grass again so it can be stopped completely if wished, no matter what performance cost! This is so f.....ing annoying with an RTX 5090 which has enough headroom to do this but there is no way to change it anymore. This absolutely unnatural comic-style bushes-popping is really destroying everything of this nice flightsim in lowlevel flight! It can´t be that hard to change...

I don't know if you'll find a perfectly clean cockpit. I don't remember ever seeing one like this.

That solved the issue!

@BIGNEWYHi, I've re-tested this 'bug' today and it seems to no longer be an issue. Test Map: Kola, AGM65 mavs, Litening pod, Auto start, latest patch. I had the old TGP equipped, however, this bug was not specific to either TGP. I made sure that I pressed TMS down after bore sighting. It now seems to be corrected. Would you like me mark as solution? Thanks

Also one can not assign "center view" and "reset zoom" to the mouse....

Evidence is in the screenshots above, and in the fact that The Bigger Bass also has this issue, and with the F-16, most probably not in the Marianas map. Moreover, why would he and me invent something? To annoy you? These are not anecdotes but hard FACTS. Proof is since I have marked the file SnapViews.lua as "read only" I don't have this issue any more, As this bug tries to change the SnapViews.lua does not succeed because now is "read only"..... And BTW, the corsair and the huey missions I provided do not have baked in views.

Auto-Rich on the fuel helps with keeping the cylinder heads cool in this situation.

Товарищи, а возможно ли погрузить в грузовой отсек Чинука допустим джип с дшк, а затем выгрузив его на каком либо филде, использовать его, при наличии у игрока модуля CA?

These things use low-intensity LEDs which are unlikely to cause damage. Plus you aren’t looking directly into it. TrackIR is certainly the best option. Unless you’re in a country with exorbitant prices this is the way to go. I haven’t ever used other devices but from what I read they require too much fiddling. TrackIR works right out of the box. The face or eye tracking devices like Tobii aren’t supported in DCS and need workarounds. No harm in trying these out though if there’s a return policy.

The first combat landing I did was in Iraq when I flew from Kuwait to Balad. It was night, and couldn't see out of the porthole of a C-130 and I'm not religious, but I was praying to land, preferably soon. The C-17 is more tame when we did the landing in Bagram, so it depends on what plane you fly in. I'm just reminiscing for those who will do this on how your "passengers" will feel if you RP that kind of stuff in missions.

I can't find any topic on this issue so I'm going to have to create one... basically I have been making simple missions for Su-33 taking off from Kuznetsov (and landing on it also of course) towards evening/night time hours and I have noticed I cannot see the carrier at all because its lights are not visible at all until around 0.8 Km See screenshots which show cockpit view with HUD ILS where at 0.9 Km lights are not visible at all and show only at 0.8 Km distance, but this is not because the carrier lights turns on the lights at that distance, because in external view (while mission is paused) when in F2 view of the aircraft, Kuznetsov's lights are fully visible however when moving the distance back the lights stop being visible again. This makes landings on the Kuznetsov extremely difficult at night... can this please be fixed? EDIT: I forgot to add, this is with new 2017 model of the Kuznetsov

I haven't noticed specific 580.97 thread yet,but you'll get more attention by posting in crash-related section of the forum: https://forum.dcs.world/forum/482-game-crash Keep in mind providing logs is crucial, because it's impossible to investigate anything without these really. In the meantime, you can also try to use DCS log anaylzer to try to narrow down the cause by yourself: https://forum.dcs.world/topic/343412-discord-dcs-log-analyser

The natural home for the MiG-17 would be Vietnam. They didn't see action in Korea, and the German, Sinai, and Iraqi maps we have are all set in the wrong period. I'm not saying I won't be flying the MiG-17 there (because you use what you got.)

Just catching this here as well , so it doesn't get missed. If you transport cargo from a ship to another ship then the cargo doesn't link to the new ship and disappears (as expected really), a little tweak in the code to somehow link that cargo to the new home is needed please

No idea if realistic or not (so no bug report) but I thought it was interesting that Pantsir and Tor M2 shoot down Hellfires. Makes them very strong in defence.

ED will not show signs of life without a reproducible use case. I said previously - there were bugs related to views, some were fixed, but there may still be more. But this thread so far was more confusing than evidence based. It's not like nobody believes there are bugs, but always try to make it easy for the guys to reproduce. Provide tracks, configs, videos, evidence. I can't test any Corsair mission as I don't have the bird, yet I wanted to help originally with other missions you provided, but these were wrong missions (baked-in views) and your replay was "but what about"... It's jsut very difficult to help in such a case. Make the case clear, I know it's sometimes really hard, but it's close to impossible to reproduce anything based on anecdotes. These things can even be different bugs caused by different things, just manifesting in a similar manner. ED will not waste time on a report as vague as this one. They have many more quality reports and then they have their priorities as well, so even totally obvious proven bugs are not fixed for many years. Is it Marians WWII related? Is it F-16C training mission related? Is it Corsair related (is it even ED's problem in that case)? Hunt down a concrete case and document it well.

Thanks, I had a look, there are some modified textures MODs for color, etc. I didn't see a MOD with a new pristine factory cockpit. And also, by default it seems to me that the vanilla textures are not crystal clear compared to other DCS aircrafts. Especially on the instruments and labels but maybe I miss something.

I recommend taking a look here. https://www.digitalcombatsimulator.com/en/files/filter/unit-is-mi-24p/sort-is-downloads/user-is-Sundowner.pl/apply/