Jump to content

Renko

Members
  • Posts

    216
  • Joined

  • Last visited

About Renko

  • Birthday 01/01/1883

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I didnt see anyone mention to check this, go and take a look to see if Force Feedback is disabled. You need to have that box un-checked. It's unfortunately On by default and I've seen it cause issues for users multiple times. So take a look just to discard that item hope it helpsnull
  2. Thanks to this user if you are using JoystickGremlin you can have this for DCS Hope someday this will get the attention of ED , It is definitely worth it.
  3. Great addition Kbu! I hope that ED will realise someday how useful it would be to have this option for users of their DCS helicopters. It's worth it because the immense majority of users would benefit from it. As Polychop and Mods (yes, mods have this) users already do. I'll leave a link to the feature wish list in case any ED developer is reading this. Unfortunately, that wish didn't receive any attention from them. https://forum.dcs.world/topic/372465-new-trim-type-option-for-dcs-helicopters/ Again great stuff Kbu, and thanks for sharing it with the community!
  4. With all due respect, users are concerned, and rightly so. At the moment, if I report a bug, I won't receive a response from any member of the Polychop team. The CEO is nowhere to be found, even through DMs from people who have worked with him. The only developer working now cannot communicate with users in public forums without the previous CEO's approval. Yes the Kiowa was feature completed when it launched, but that doesnt mean there were bugs and there are bugs. It needs maintenance. And since Polychov used discord for reporting bugs, one just need to take a look there to see how those reports are doing in all this time. We are talking about a module released last year, so it is understandable that users are concerned about this zero-comms situation that creates all this uncertainty. The way to stop the uncertainty? A brief announcement from the CEO adressing the situation. (Last public message from him was in January 2025)
  5. Yes, you are right about the LOBL. My mistake, sorry
  6. First of all thanks to that SME for that detailed answer. Included some SOP. If i may, i think there are some good points made. Let me try to explain why. I get that with the explanation about how the Lima works, makes so much sense for the user to operate that way. Stay in NO WPN, and only when you are about to shoot change George to MSL RF. But there are some considerations to this: - 1) If you change to CPG seat, you can still have the Lima selected and use RHG LRFD Trigger First Detent to have a range. Without having the Lima inertial guidance activated for that potential target. So if you get in the CPG seat and can do that, it makes sense to include that in George menu. There are some space even for that. When you are in NO WPN on the right you can ask already George to Lase. And in MSL RF on the right there is nothing, so you could include there the same comand but for a 1st trigger detent only. null - 2) George will lase with 2nd trigger the TGT or Point of interest as soon as you tell him to select the MSL RF. Commiting that missile instantly. That as you can see can create some issues if the pilot is not aware of that AI instantanious action. Since the Missile guidance system is already commited to that place. For example if you tell George to select an object on one side, and after its tracking you change to another object because you need to or because you selected the wrong one. You will get a message from him saying "Negative, out of range" when the issue is that the missile is already tracking other TGT. With Consent to Fire you cannot launch until you deselect & select the MSL. Which is a great thing. Because if you launch anyway the missile will go to the tgt that was tracking in the first place. Maybe it will be nice to add some audio line for that case so the user is aware of that scenario. I attach a track from a quick test where its showcased all this in this order, starting around 70s mark: - How George will stop you from a mistake with the Limas (which is good, but the audio is misleading. Plus the symbology of the WPN page). - Then from the CPG seat how with Trigger First Detent you can range without commit a Lima. - How as CPG you can make the mistake and send the Lima to the TGT you tracked before. - The rest you can skip because is just another test of the symbology bug of the Limas. The bug is with the symbology of the Limas. If you look to the WPN page you will see the Limas state never transition to the T (tracking) status in all the duration of the track. This will mislead the user because they won't know if a Lima is tracking. null Apache_LIMA_and_George.trk
  7. I see you too have the Virpil T-50CM3 Throttle I think there are some unresolved issues with that hardware in DCS. In the Changelog from https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.20.15010/ There is a fix for the same hardware on the F16 : "Fixed: Duplicating Thrust axes on the VPC Throttle MT-50CM3 joystick." And I had reported an issue with it in the Apache forum last May with the T-50CM3 Throttle, but got no answer from ED. Curious that my issue is that the controls are reverting to default when i shutdown and restart DCS, in certain conditions.
  8. First of all, thank you for answer this thread Yes, same USB port for each device of the sim hardware always. It keeps the same ID so that way DCS keeps the keybinds In the input folder (AH-64D_BLK_II_AI_Menu) there is no .diff.lua file asociated to the throttle for George AI, because i have no custom keybindsfor the throttle there The situation does occur each time i start DCS. Meaning samething happens if i start it tomorrow, or if i enter and exit seconds after reaching the control menu to clear those controls. Each single time it resets. But as i said in May: I think when this section its empty DCS forces an uncommanded back to default keybind for my throttle. If i make a custom keybind in that section of George AI even with one button on the Throttle, so a file is created in the input folder, the issue i have doesnt happens. But if then i clear again that category and restart DCS, it will happen again. That Throttle section will be populated again with the default keybinds I think its reverting for some reason to default. Its the only module where that issue happens.
  9. Agreed. Its a beloved module for sure. It shows by how the former devs push that last great big update before the Kiowa launched, and even some community members helped selflessly to push it forward. Both did an outstanding work. Hope we will get an update as soon as posible on this situation
  10. Please can this be checked At September 18 with the DCS version 2.9.20.15010, it still happens. Each single time DCS starts And yesterday patch included a fix particulary to the same hardware that has this issue in other module. The VPC Throttle MT-50CM3 null
  11. BTW I just realised one thing that could make the solution more easy for you guys, but im not 100% sure. I cannot try because i dont have display export in DCS. Seeing the AMPCD from the thread i quoted it seems that the solution could be achieved with only working in the Luma channel. Because the map colours seems to be okay. So if you dont need to transform the colours and only need the luma, that makes things way easier. If thats the case you could achieve a solution by just adjusting with a custom curve or with gamma values. Here is an example with one of the OP screenshots and a quick custom curve i just did in some external software. I tried the same in Photoshop with a similar curve. And both make those two almost identical, the priamry display and the external one.
  12. I would like to offer some advice on this matter, as I have some knowledge in this area. Maybe this will help the team get on track to resolve this issue. First of all i will make one assumption on those colour spaces, because those may deviate from the Rec.709 & Rec.2020 specs. We have some sort of HDR Color Space in the game primary display, lets call it HDR. And the export display is some sort of SDR Color Space, lets call that SDR. So if thats the case you will only need to transform from one Color Space to the other. In this case you will need to transform that SDR to HDR, in the values that DCS uses. This is nothing special. In the industry converting from one Color Space to another is a pretty common thing to use on daily basics. So the only thing ED will need to provide is a Trasnformation Matrix for that SDR to HDR color space. Probably should be pretty straight forward to do a custom LUT (Look-Up Table). Or use an existing one if it complies with Rec.709 and Rec.2020 specifications. And you could provide one. Where? Well just like you have that drop-down menu called "Color Grading" that are just LUTs ( a LUT is a Trasnformation Matrix). There you can have one at least that transforms from SDR to HDR values but it will only affect the export display you choose. So you will solve this issue with that. This user here has done a Colour Space Transform without knowing by using Reshade. And you can see that works well enough, and its is just that. Transform SDR values to a similar HDR ones from the primary display. So if DCS supports having some LUTs for "Color Grading". It should be able to give in the same manner a LUT that transforms SDR to HDR values and only affect export display. If the team wants to find more info on how this technical Colour Space Transforms works they can google "Color Space Transform HDR to SDR". They should be able to find good info. As I mentioned earlier, if DCS already supports LUT, this feature could be applied just to exports from a technical standpoint. Hope it helps
  13. Now we have at least one entire single player campaign that needs you to have those lines in order to play. I wonder if a user who adds this will remember to remove after playing Still unclear to me, sorry i'm a bit clueless with all this, but if i leave that autoexec.cfg after playing a trustworthy mission/campaign it could be an issue for me as user. That I wouldn't have before this update? Sort of like leaving the door open
  14. Can confirm this behaviour Easy to test for them. Just launch Instant Action Caucasus Refueling F16 Mission. Accelerate time and you will see the AI doing that refueling loop. The two-ship AI that are refueling when you arrive are doing what the OP has described. I had to gun down the F16 to practice refueling
  15. As the title says, add an option on the Special tab of a module that will give the user the option to set a custom dtc file to be the new default for that module. You would have to include checkboxes where you can select which parts/sections of that file will be loaded for that new default. Otherwise, if all the data in the file is loaded, it will create conflicts with missions, campaigns and MP server missions. For example if i want only the countermeasures but it will load the default comms too, i will lost all those presets for comms. Or nav data I think this will be great to have and will serve the purpose most users will be using the DTC for. For example, if you are only going to use the DTC for stablising a new custom default CounterMeasuresSystem programs, and want that every time you sit in that module that data will be always the new default you set in the Special Tab.
      • 2
      • Like
×
×
  • Create New...