Devrim

:flowers: :cheer3nc: :worthy: :thumbup: <3 <3 <3 <3

Source? Official?

I'm a little confused. What I understand from "I.C. succeeds" is that I.C. successfully catches the abnormal modifications but, here you mean I.C. doesn't warning about anything at first, right? If so, I think this issue is there a long time. Sometimes I test a mod that I know it could not pass the I.C. At multiplayer lobby, I.C. shield icon seems green (no warning) but when I entered a server that I.C. enabled, the server kicks me out. And then I see the I.C. shield icon is red and reports which files are guilty. :) *** In your case, did you install a land texture mod?

You see in the picture, isn't it a rope motor that mounted over the door? Maybe it's in the To-Do List.

I do have Viggen module long time but I don't know why and how, I didn't pay attention to it as it deserves. Silly me. Recently I fly it and ... man, what have I been thinking for all this time? Thank you bizillion tons Heatblur!!!

And I'm here again... Plllliiieeeeeaaaassseeeee? :D

This has been already found long time ago but, I feel disappoint that this issue is still there. This is joystick default.lua and Cargo View command is mistakenly placed wrong section. We can see the line in Controls page but can't bind any button of our HOTAS. . . . keyCommands = { . . . }, axisCommands = { . . . }, --Cargo view {down = device_commands.Button_1, cockpit_device_id = devices.EXTERNAL_CARGO_VIEW, value_down = 1, name = _('Cargo View'), category = _('View')}, }, } eof Please, move it into keyCommands section and we can use it. Thanks a lot.

I have no idea what Zimmer told (he edited his post) but I see some improvement on autopilot (AI Copilot I mean). At least, when engage it, AI won't mess with the controls. Do you confirm too?

:D No actually.

What's your HOTAS? https://forums.eagle.ru/showthread.php?t=222108

Missing track.

Hey. I've just re-checked my mod. I'll update it without ED's updated textures, but I will fix those bugs. You're right about HUD. Let me check it. If I can fix it, I'll add it into the mod. See you.

Thanks Holton. I looked for this mod or something, otherwise I'd make one. Thanks. You saved my time. :D

Thank you Marduk. The conversation between Rudel and me was just about this, my friend. :) I'll update it but I feel weird about the textures. People didn't like updated textures. So, I'm hesitating if I should update the mod with new textures or not. If I should, I'm afraid ED would re-update the textures. That's why maybe I should wait a bit. I'm not sure about that tho. :)

Guys. You remember ED's poll; What is your primary DCS flight controller?. I think that according to this poll's results, ED has added new HOTAS profiles into modules' input folders. If you check your aircraft's input folder, you'll see new lua files with today's date. The given bindings in them may be interfering with your own bindings. I don't know a real solution but you can choose to delete the lua file in input folder but I'm sure it will come back with next DCS update. Some friends report that re-starting DCS will solve the problem but, for some say problem still exists. You may have to re-bind all keys from scratch. For example, I'm lucky at this point; I use X-55. No new lua file for Saitek, even the poll's result shows that Saitek is the one of most used HOTASes. *** I'm sure there're many users (like me) who suffer from binding troubles for years and years. As I said in another thread, ED didn't find a really proper technique to binding controllers. It's OK for settled modules but it's a huge pain for developing modules. Thank you.

Hi Rudel. Yea, I've noticed that right after today's update. In fact, ED has touched the textures - in other words - ED has made a serious graphically update on MIG cockpit textures! (I love it and I'm happy for that because probably they will make a similar touch on KA-50's cockpit! - Yeeey!) So. This mod needs a whole re-work but, I guess I'll do it in quick way. Thank you so much for feedback. See you soon. Dev.

I hate these binding issues! ED never found a proper technique to handle binding thing! Until last year I was directly editing stock lua files to fix my own bindings but I couldn't stand against updates, updates and updates. That's was exhausting modding for me. I quit. ... but I luckily have zero problem with bindings on today's update. :D :D :D

Second child? :D

Map updates cause the large size I think.

No Macro_Seq. means no auto-start for that module maybe?

You're welcome my dear friend. If Willy give a clue on aircraft? I can give a try...

Yes, you're right. If there's no any announcement about ending mission, you "assume" you finished the mission. Mission builder should add a closing (congratulations) text or speech at the end of the mission.

Oh! My bad. Thanks a lot, mate. :)

Come ED! KA-50 is older and older than P-51. Why? Why?... :\ :\ :\

You need to do some work, if you want to. For which aircraft? Example: A-10C Browse: "...\Mods\aircraft\A-10C\Cockpit\Scripts" folder. Find: Macro_sequencies.lua Take a backup of it. Edit it via Notepadd++ or another good text editor. Erase message part of the line like below; ,message = _("BATTERY - ON"),message_timeout = std_message_timeout You must do that for each command line. Or, there may be an option in OPTIONS page. Turn off Subtitles or something? Cheers.