All Activity

My apologies for being obscure. I use doString_in all missions (it's a framework I use, DML, and its 'common' bedrock that provides all services uses dostring_in(), it uses at least one context. The number of contexts used is immaterial. A user who does not know the origins of the error, and who did not open their DCS install, will suddenly receive an error. Because by default, invoking doString_in, no matter which context, produces a nil error. Someone who until yesterday could happily play all these missions and who did not set up an autoconfig file will today have the mission stop with an error.

Yes, it puts the burden on those who developed the scripts to tell people how to run them / what to do to run them. I agree that this is not great but it is how it is now. My message was meant to the guy who seemed to be a starter in regards of DCS scripting.

AI behavior seems unadjusted for the newer frag radius as well. AI P-47s are fragging themselves and killing the pilot with low-level 250lb bomb drops during CAS.

The rectangle becomes visible when foveated rendering is enabled, regardless of whether you're using PimaxXR or Pimax's OpenXR runtime. Alternatively, you could try disabling SSAO to see if that helps.

So you mean you're using net.dostring_in in all possible contexts with all possible scopes? I doubt that. Unfortunately, the documentation is a thing. There's not "the" source and what we get from ED is very limited. I am on vacation rn, so I can not write up an essay about it. If you just started scripting it is quite unlikely that you need this specific API. You can use it for instance to call a function from your Hooks environment inside of the running mission. Or you can now read values from your mission from the Hooks. That can be useful for persistency frameworks, statistics etc.

Really how are you so sure ED has said in the past certain new features/tech for new maps can’t be done to olde maps like the NTTR and Caucuses.

We are not able to reproduce the gear down issue, so please check your bindings and attach a track replay example. thanks

Exactly! Upgrading every 5 years with a very expensive card (whatever relative level this means at the time) that lasts(!) is reasonable imho. Uprgrading every (other) year for a latest luxury card is bonkers for most regular people. (Still their choice though, I'm not hitting on anybody who does/did is. Just for me personally, it is bonkers)

This video isn't a good example; I've already written about this. It's stretched and compressed, though it's still clearer. Regarding IR, the DCS topic is still in development and not finished. Some vehicles are still black even though they're moving. Unfortunately, new textures haven't been implemented in DCS everywhere, and there's still a long way to go.

bonjour. désolé. je n'ai pas vu le message. je n'ai pas été tagué. je vais consulter votre journal pour voir si je peux vous aider. j'utilise Google Translate.

threads merged

Many thanks... And Raven is spot on, that was supposed to be Silver Dragon, I guess I have an answer now so I'll just apologize to Baltic for the wtf moment

Well, now i am feeling like an idiot... I apologize. I guess i got used to the kneeboards in the Arctic Thunder F16 campaign, as i just finished this, and my eyes were expecting things to be in the same place.

hello. a new version of visual c++ was installed in support of the sim. you can uninstall the update and the sim will likely not work. "Visual C++ 14.44.35211 refers to a specific version of the Microsoft Visual C++ Redistributable package, which is required to run applications built with certain versions of Visual Studio. This package includes runtime components of Visual C++ libraries, such as the C Runtime (CRT), Standard C++, MFC, C++ AMP, and OpenMP libraries. The "14" in the version number indicates it's related to Visual Studio 2015-2022."

this has been reported, thank you

I agree. I think that before the release of the MiG-29, nothing will be released for sale either - therefore the minimum possible release date for the La-7 is a couple of months after the release of the MiG-29.

this has been reported to the team thank you

The big picture is Fw tested GM1 several times, and with the A-8/R4 had aircraft production blocks reserved at AGO for 200 airframes with GM1 equipment installed. This never materialized. If the airframes were built with the GM1 equipment in place isn't clear (it's likely, though). There's no evidence for GM1 use in the field by Fw 190A squadrons. At the time of the Bengelmann visit, GM1 had already been projected and cancelled for the A-6 and the experimental (and ultimately cancelled) 190B was in testing. Just because Rechlin or the FAA aprove a modification, this doesn't mean the kit or serial installation is commercially available for procurement and implementation. A gap of several months is more than reasonable, even today. Certainly, but not only does the report not mention what exactly it means by "provisions" and "tank". It also fails to identify the components of that provision and it's difference to normal vanilla A-8 equipment. Further down, there's no differentiation between the 115l tank and the tank found in the crashed aircraft. That's precisely the reason why it wasn't popular at front line units. Especially during summertime. It's not a reasonable solution for operational use and it seems Galland himself didn't think much of it. The report is signed 1 October 44. 1 May 44 is the date of the design to be replaced. By that time, the "Erhöhte Notleistung" rating discussed is most probably 1.8 ata.

It did not bounce. Your stick is too short, with short lenght or with short throw. Check this video explaining your issue. I used 0 curves with previous FM and in my opinion is the previous FM was better. Now it flies like vanilla Cessna from Flight Simulator X. https://youtu.be/Gs2m-xlyK7o

The level of detail is in fact higher in the TV portion. The TV modes of these pods have always been my goto for actually identifying details beyond just hotspots. Vehicle type and even the specific vehicle. So this seems very useful in centering yourself on the surrounding hotspots and then have the center object be examined in the higher detail TV mode. Or you can look at it as focusing on the center while having more obvious spots on things moving into the outside frame or even moving within it that you are not necessarily focusing on.

Moved to weapons bugs section

I can't manage to enter coordinates via the Jester menu when flying the Phantom in VR: even when the cursor blinks in the LatLong, the keys on the keyboard have their usual keybinds and don't allow me to enter anything like N3459E2213 . Is this a bug, or am I doing something wrong? Cheers, Tobse

Hi, the wing fold is correct at the moment, it is a work around for a carrier start issue, once that issue has been resolved runway starts will have wings extended. Im not sure about the gear down issue but will try to find out. please include a track replay example for the landing gear. And please in the future only one issue per report, otherwise things get complicated fast. thanks

Hi, we have a report open for additional weapons for the S-3B but currently it is lower priority. thank you