gofrm76

Is there a dedicated section for discussions on documentation issues? I came across a couple of issues I would like to suggest fixing but I think it's better to have them separated from the topics about actual issues in the sim itself.

Hi, the error regarding the localization of decimal numbers I posted back in August seems to still exist. After going to the preset editor tab and leaving it right away without changing anything I get a popup asking me if I want to save the changes. After continuing, the changes in the options file looks something like this:

First of all, I want to thank SkateZilla for this outstanding tool. I have been using it now for years and I recently started to use the new version with the integrated config editor. Unfortunately, this feature isn't working for me because the config file that is written out by the tool is corrupt. For example, the following lines are changed by the tool without me making any changes in the UI other than loading a config and saving it again: ["custom_IPD"] = 63.5, is changed to ["custom_IPD"] = 635 ["aspect"] = 1.3333333333333, is changed to ["aspect"] = 1,3333333333333, ["msaaMaskSize"] = 0.42, is changed to ["msaaMaskSize"] = 42, Some values will be replaced by an empty line: ["autoTrimmer"] = false, ["avionicsLanguage"] = "native", ["birds"] = 0, to ["autoTrimmer"] = false, ["birds"] = 0, Starting DCS with this config file will result in the values getting reverted to default. While I am not sure that the removed lines are actually caused by a bug rather than being a default value that will not be written out explicitly, for the first described problem I bet it has something to do with the default system locale the application is using which in my case is German. I assume SkateZillas default local is US. In these two locales, US and DE the usage of '.' and ',' in numbers is the exact opposite, and in parsing numbers from strings in the wrong locale, a decimal separator will be ignored by the parser because it is misinterpreted as a thousands separator. https://en.wikipedia.org/wiki/Decimal_separator For the aspect-value it seems that the value is simply written out as a string with no parsing at all after it is generated with a comma as a decimal separator because of the german locale. I tried to overwrite the system locale in the user.config file with no success. I hope my description is of some use to solve the problem. thanks again for this great tool...

For all the campaigns where it's stated that I need version 1.5 of DCS World, does that really mean I have do have an installation of that exact version in order to run the campaign or is it the minimum, so in other words: do these campaigns also run with 2.5 beta?

Thanks. I was looking for cargo related topics before, but I was only searching in the multiplayer section.

Are we really talking about the same problem? We have no problem with the load swinging around like crazy. It's only when we put it on the ground and unhook that the cargo is moved to 30 feet above the ground for everyone else. That problem is not mentioned at all in the post you liked.

When cargo is placed on the ground by one player after unhooking the cargo it suddenly shifts to about 30 feet above the ground for everyone else except the one who dropped it. These hovering cargos still have a hitbox and stay there the entire session and it makes it impossible for other clients to drop additional cargo nearby. This happens consistently every time. The drop locations seem to be of no relevance. We tried flat ground, hills, building roofs, and one of the oil rigs. Setup: DCS 2.5.6.55743 Open Beta Dedicated Server and 4 Clients, Caucasus, Huey 4 Ship Is this a known issue? If not, I try to produce a track file and some screenshots next time I fly with my buddies. As this is only occurring in multiplayer, do you need the track from multiple clients?

Ah, thanks, I didn't know that. I found it way too slow but this is maybe because I have recently modded my TDC and didn't fly A10 since. And the new stick may behave differently from the old one. I find 100% saturation with a 25% curve ideal.

I had a similar problem with my A-10C II controller profile, the preset saturation for my ministick was at 30% for whatever reason. Don't know why, never touched that profile before. I had to change it back to 100% manually, to get 100% travel on these axis. Maybe you have the same problem with your throttle axis.

but for 10th gen you had to change the board as well because of the 1200 socket, right? so also different chipset, different ram... does higher ram speed make any noticabled difference in dcs?

#4584 I just received mine and installed it within 10 minutes. Top-quality, works like a charm. One question: Is it common that the update rate of the slew axis is significantly lower than the throttle axis? I guess that this is the default behavior of the throttle firmware. But it wasn't noticeable before because of the low fidelity of the standard stick so I'm just wondering...

thanks for your help, I will try that...

Avoid any additional light sources or windows behind your back or better in the cameras field of view. From my experiences with my TIR4, the camera gets very easily distracted from additional light sources and does not recognize the lights/reflectors of the clip/hat anymore...

my only concerns with waiting is that prices will rise for christmas or maybe the market will be bought empty because of corona and/or this other new FlightSim like with the controllers/joysticks and then they rise the price because of this.

Since Raven One Campain has much of its comms in the "F10 Other" menu I was wondering if it could be integrated somehow with Viacom. At least by default, it seems not to work. I have the Pro version with every addon and have the auto-import activated. Do I miss anything or is it simply not possible?

Yes, you're right! I know this chart from the F-18 survey. But for the F-16 that was the info that came closest. By knowing the priorities one could infer the results of the F-16 survey at least to some extent. So I was thinking "better than nothing"...

Thanks i will do that.

Hi, I'm thinking about getting into mission scripting for DCS to some extent. I am looking for information about the DCS scripting engine for a couple of days now but other than a short description about some key Objects/Classes/Singletons on Hoggit I didn't find what I was looking for. Sure there are many tutorials on Youtube including the very nice ones from MOOSE/FlightControl. But coming from a developer background with experiences in a couple of object-oriented programming languages I am not really looking for tutorials describing how to spawn a unit or how to write a trigger in Lua. What I am interested in first is the big picture - how the scripting engine works in general and how it is integrated into DCS. Starting with things like: - How does the "main event loop" look like? - Is it all single-threaded or does it run in a separate thread? - How do events work? Who can emit, who can process events? - What is the lifecycle and scope of objects and variables? (i know, this one is discussed in a coupe of videos on YT to some extent) - What is the lifecycle of the execution context/runtime? - Where can I hook into it? (other than creating a trigger and implementing an action, obviously) - Is there any reasonably current API documentation? Maybe in code like Javadoc? - What are the files and directories in DCS that are interesting when it comes to scripting? A couple of these questions maybe relate not only to mission scripting but to scripting/modding in general. Like for example: How are Tools like SRS or Tacview integrated into DCS with additions to the options UI? What API are these tools using to interact with DCS. For these kinds of questions, I didn't find any good answer yet. Is there maybe a technical reference manual hidden anywhere for these kinds of topics? Thank's in advance for any advice, very appreciated.

https://www.digitalcombatsimulator.com/en/news/2020-08-14/

Yes, I know, I didn't do it here because the changelog mentioned already known issues in this regard. But I was about to create exactly that after I noticed the changed topic. At the same time, a link to a thread has been posted that shows the issue in a much more detailed way than I would have done it. But thanks anyway for updating the thread, next time I will provide the trackfile right away.

Thanks for the clarification and the link to the thread that handles this topic in a much greater detail. Even if it doesn't matter for me personally anymore, because I have received the information I was looking for. I think it would make sense to delete the "cannot reproduce" tag from the post since it's acknowledged in the thread that it is indeed a bug. Maybe it is of help for others that, like me, didn't use the right words when searching for an answer to find the other thread mentioned above.

I was trying to zoom in on some ground units with the A/G radar in standard zoom and EXP1, 2, and 3 but I was not able to see anything. I also tried all the gain levels but no joy. I placed the units for testing purposes on the plain desert ground of the PG map with no landmarks in the vicinity in order to make spotting of the units easy but on the radar scope, there was not the slightest change visible. I read in the changelogs that there were fixes to the radar signature of various ground units and static objects. Does that mean, that they are not visible anymore or that they should be visible now? It was also stated in the release notes that there are still some a/g radar issues in the latest OB. Does that have anything to do with it?

If you turn off D/L you should still have the "auto" IFF active with LTWS, rigth? So there would still be a reason to switch LTWS on/off explicitly. Regarding declutter, I was of the impression that turning LTWS off deactivates data acquisition and processing entirely rather than just removing the symbology from the display. Otherwise, it would surely be called something like DCLT or the like. So still, there must be some disadvantages to having this turned on, otherwise, it could be "hardcoded" into RWS as said before and there would be not option to turn this off...

I assigned the above-mentioned callback to one of the switches of my warthog. Using the warthog switch does nothing while in the 3D-Pit the switch is working (so it's not because I'm not in A/G mode or FLIR is off). Is the callback broken or do I miss anything else?

Here is what I found only recently in another post. I hope it will make TDC easier to use: https://deltasimelectronics.com/products/thumbstick-slew-sensor-adapter Also, isn't there and option under special-settings to turn off realistic TDC so you do not have to hold down TDC while slewing?