vgilsoler

Before the hybrid cpus the devs just need to send the treads to windows cpu scheduler and let the OS do their magic, but after gen12 this method is no it’s no longer working well. So the devs needs to check if the next available core is performant or efficient, and if the thread can run in both types of core or only in one of them. Obviously this increases the complexity of the code and the workload of developers to produce an optimized software.

Well, for me it doesn’t matter if ED can improve performance and offload CPU workloads using nvidia’s implementation, or their own. But I wanted to know if ED already is aware of, and they evaluated the use in DCS as a way to solve some of the pending issues in 2.9.

Is there any plan by ED of using Nvidia RTX IO or Gdeflate to improve IO perfomance and texture handling in DCS? In my opinion, (and as user with old CPU) anything that can offload CPU workloads is an improvement. Furthermore RTX IO (as per Nvidia docs) is compatible both with DirectX and Vulkan. https://www.nvidia.com/en-us/geforce/news/rtx-io-for-geforce-gpus-available-now/

Energía in spanish

For those could be interested in how the hybrid CPU architecture has changed for gaming and an explanation why intel 12th gen CPU and later can be less performant than older CPUs. https://www.intel.com/content/www/us/en/developer/articles/guide/12th-gen-intel-core-processor-gamedev-guide.html It can be moved to other forum by the moderators if they consider it.

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...