vgilsoler

When replay a track, I tested with different tracks, and there is a release ordenance (bombs, missiles or tanks) a windows error is showed. The track replay can continue. It happened with both stable and last beta using MT. I didn't tested with ST. I attach error screenshot, dcs log, mission, and a track replay example. Error produced about 1200s after start. practice_f86_bombing_no_mpc.trk dcs.log CFragps_Marianas_Proving_Grounds.miz

No news about correcting the radio controls in the last update? Controls are the first point of contact with a plane for users, to have them bugged for years doesn't give a fine image about the status of the plane and quality and assurance work.

A benchmark track replay should be included. It could use the SU-25 or the TF-51, Marianas map and different weapons, missiles, bombs and guns. In that way we could compare performance or features between versions or settings, or between systems. Or even could be useful for troubleshooting. Regards,

Maybe you’ll find this interesting, I guess ED already read it https://www.intel.com/content/www/us/en/developer/articles/guide/12th-gen-intel-core-processor-gamedev-guide.html

Yes, the info is there but it relies on users extracting, formatting and updating info from maps, when that info is already known by the module/map creators.

The following documentation in pdf in addition to flight manual should be provided with each module: Planes - A list of default keybindings/commands. It will be faster to configure joystick mappers like TH target, or to check commands without stopping simulation. Maps - A list of each airbase with their NBDs, ATC frequencies, TACAN, etc. To print or to check without needed to go to F10.

Any news for radio key binds? Maybe next for update?

Thank you for reviewing the track and the comments. As I said before, at this moment it's more bad feeling when shooting with the Mig-15bis than thinking there is a bug. I wanted to know if for other users it was the same, or not.

Probably it's me and not the gunsight or a bug, but more I practice with the mig15 more bad feeling I have with the gunsight (fixed or gyro doesn't matter) I used to fly with warbirds (FW190D9, P51D or P47D) and I'm not an ace but I can shutdown a B17, Ju88. C47 or straffing with guns using a reasonable amount of ammo. But with Mig15...I'm starting to think there is something wrong with the gunsight or with the guns. I attach a track of a training mission trying to fire a C47 and a B17. practice_mig15_gunsight.trk

The P-47 is good at high altitude because the engine performance is very good due the supercharger. But she is still a brick, a high speed brick. You need to trim her correctly and do not reduce speed.

After a belly landing in caucasus map it is possible to view grass passing through the wings and the cockpit floor. I attach track and some screenshots. practice_mig15_grass.trk

Good stuff! I will add them to my notes. Thanks.

I tested but still not able to tune the inner ndb, at least I can do it to the outer ndb and get close to the airbase.

Don't forget to add the Mustang to the list of available planes in Korea

Thanks for the info, I’ll take a look and test it.

I'm trying to setup the ARK-5 for Krymsk Outer NBD and Inner NBD. For the outer NDB I don't have any problem, select far switch, set ARK-5 to ANT, change frequency range, fine tuning and set mode to COMP. I can listen the morse code at 408 mhz aprox. But when In try to do the same with the inner NBD and select near switch, the frequency range doesn't change in the dial and inner NDB at 800 mhz can not be tunning. If I try to setup first the Near NDB, it happens the same. What I'm doing wrong with the ARK-5? I attach a track with the followed steps. practice_mig15_ADF.trk

I've added these lines to the Mig-15bis\joystic\default.lua axisCommands = { {cockpit_device_id = devices.CONTROL_INTERFACE, action = control_commands.Mig15_Command_FlapsHandle, name = _('Wing Flaps Handle'), category = {_('Systems'), _('Custom')}}, {cockpit_device_id = devices.CONTROL_INTERFACE, action = control_commands.Mig15_Command_FrictionLever, name = _('Throttle Friction Lever'), category = {_('Custom')}}, {cockpit_device_id = devices.CONTROL_INTERFACE, action = control_commands.Mig15_Command_HydroGainLever, name = _('Hydro Booster Lever'), category = {_('Custom')}}, {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_Volume_EXT, name = _('RSI-6K Audio Volume Knob Custom'), category = {_('RSI-6K Radio'), _('Custom')}}, {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_SetTransmitterFrequency_EXT, name = _('RSI-6K Wave Control Handle Custom'), category = {_('RSI-6K Radio'), _('Custom')}}, {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_SetAntennaFrequency_EXT, name = _('RSI-6K Antenna Control Handle Custom'), category = {_('RSI-6K Radio'), _('Custom')}}, {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_TransmitterFrequencyFix, name = _('RSI-6K Wave Control Handle Lock Custom'), category = {_('RSI-6K Radio'), _('Custom')}}, {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_AntennaFrequencyFix, name = _('RSI-6K Antenna Control Handle Lock Custom'), category = {_('RSI-6K Radio'), _('Custom')}}, {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_SetReceiverFrequency_EXT, name = _('RSI-6K Receiver Tuning Knob Custom'), category = {_('RSI-6K Radio'), _('Custom')}}, {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_ReceiveARC, name = _('RSI-6K Receive/ARC Switch Custom'), category = {_('RSI-6K Radio'), _('Custom')}}, {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_Forced, name = _('RSI-6K Forced Mode Switch Custom'), category = {_('RSI-6K Radio'), _('Custom')}}, } In the DCS.log I can see several lines like 2023-11-10 14:39:20.278 INFO Quaggles.InputCommandInjector (Main): Detected loading of type: "Thrustmaster Virtual Game Controller (root)", filename: "./Mods/aircraft/MiG-15bis/Input/MiG-15bis/joystick/default.lua" 2023-11-10 14:39:20.278 INFO Quaggles.InputCommandInjector (Main): --Translated path: "C:/Users/uvegi/Saved Games/DCS/InputCommands/MiG-15bis/Input/MiG-15bis/joystick/default.lua" 2023-11-10 14:39:20.278 INFO Quaggles.InputCommandInjector (Main): ----Found merge at: "C:/Users/uvegi/Saved Games/DCS/InputCommands/MiG-15bis/Input/MiG-15bis/joystick/default.lua" 2023-11-10 14:39:20.280 INFO Quaggles.InputCommandInjector (Main): ------Merge successful But I only see a new axis to configure in the settings options in DCS and the assigned control to the axis is not moving in cockpit.

Is it possible to publish a bug tracking system by ED like github issues or similar? Then the customers (we) could track their opened issues or search for already opened bugs, or reopen issues. In that way it will be easy to request for an update for a specific bug, or see its priority, etc. I think it will reduce the Flappie's and BigNewy's workload on forums and probably make the customers happier. Regards,

Is it possible to add the RSI-6K knobs as axis like the flaps handler? I tried to do it copying and adapting the lines in joystic/default.lua. I am able to see the new command axis and assign them, but nothing is moving later in the cockpit.

And when is it expected to have a fix? Because I see reports from 2 years ago still opened...

The axis labeled in control setup don't correspond to the axis in cockpit - RSI-6K Volume Knob in setup moves RSI-6K Antenna control handle lock knob in cockpit - RSI-6K Wave control handle in setup moves RSI-6K Volume knob in cockpit Why the Antenna tuning or the remote receiver knob are not available as axis but a handle lock knob it is?

Where are the missions of Normandy map that are described in the newsletter? I can’t find them in missions section for P47D, P51D or FW190D9.

At this moment, to override default IA behavior the mission creators need to add scripts at mission so the server could be overloaded by them. What I'm thinking is some type of API running on an external resource that could modify the behavior of the unit assigned to. Something like mission exporting the IA data speed, location, sensors, etc. and receiving new parameters those modify the heading, weapons, throttle, etc. So you could assign different "behavior" to same type of IA units. Benefits: - Offload the CPU resources of server running the mission to one (or more) external resources. - Using a public API service, mission creators could share in a central point their "modified" behaviors. And other mission creators select them from mission editor. - Data could be passed to a Machine Learning service that would "coordinate" or modify the actions of the IA units based on previous missions. This is not for short, medium or long term, just wanted to light the spark of developers (inside or outside ED) to start to think about it.

After read some posts about the configuration at 4k, I decided to try again moving from 1920x1080 to 3840x2160 I did a clean installation of nvidia drivers and left the settings by default, I disabled the windows HDR setting. I reinstalled again the beta and set the attached settings in DCS. And now it's a totally different game, I can see contacts at 20km, no shimmering, no excessive bright at cockpit, and the performance in the mission was very correct. I need to try another mission with more objects and I think I will need to reduce the settings. But now DCS seems the sim I was looking for the last 20 years. It seems 2.9 is far better for 4k than it should be for 1080. I hope they can put both at same level. practice_p47_beta_4k.trk

I tested the same mission i use for practice in the P47D in The Channel map on 2.8 and 2.9. I need to say I prefer not to use beta versions but saying the changelog I liked to taste the new graphical settings. About performance and eye candy 2.9 seems a big step forward, I was able to setup all settings at maximum using TAA, no shimmering on buildings or other planes, more than 100 fps (sometimes drop to 50) but nothing important. If all the mission would have gone in that way I would be a very happy man, but what worried me is the new spoting contacts, or other objects. Just going to the runway, I saw the windsock become transparent for a moment (min 6 aprox), but later it happened the same chasing a FW190 (min 60 aprox) in a dive and losing the contact, or chasing a JU88 (min 70 aprox) Trying to locate and escort a B17 was also more difficult than in 2.8. I hope that is what is referred in the changelog as "some visual issues may be seen in certain hardware/graphical options combination" I attach both tracks, the realease track is only until B-17 is located. i7 3770k @3.9 Ghz - 32GB RAM - RTX 4060 - SSD for OS and DCS practice_p47_beta.trk practice_p47_release.trk