Jump to content

-Dagger-

Members
  • Posts

    36
  • Joined

  • Last visited

About -Dagger-

  • Birthday 08/12/1987

Personal Information

  • Flight Simulators
    DCS & IL2
  • Location
    Spain
  • Interests
    c#
  • Occupation
    C# Dev

Recent Profile Visitors

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

  1. I Broke 2 cables already and fortunately they were covered by the warranty. I'm uncovered now but I've been using this configuration that I found on internet for several months and I still didn't had any issue. If you use the "normal" way the cable suffers every time you put the glasses on or you pull them up to see the keyboard. With this configuration there's no strain around the connector. Will it work forever? I don't know, but I can confirm you that using how the manual specifies I broke 2 cables.
  2. I got this one: https://a.aliexpress.com/_mMQzXmk You also need some grease as the damper was not properly lubricated, 2020 aluminum profiles, m5 round head bolts and profile connectors. Then the clamp to the collective and the bolt to joint it with the damper
  3. Here is my attempt. The collective is mounted to the chair using aluminium profiles and a 5mm thick metal sheet. next week I'll get a longer bolt to make the movement more vertical but it still works fine now. I'm also using a 3d printed clip to limit the movement using the damper tube. This way the collective doesn't go totally down and it stays at a 45º angle in the lowest position
  4. They used to have a website and a contact email at the bottom. Now it can only be reached through internet archive and probably they only speak russian: https://web.archive.org/web/20190316060753/http://ugra-media.ru/2018/proekt-blizhnij-vostok
  5. This is amazing!! Thanks a lot!! From what I see you support thrustmaster. For virpil it works very similarly but they encode the axis in the shift registers. Related code: https://github.com/gavazquez/ArduJoy/blob/master/CoolJoy.ino#L234 If you need more info let me know
  6. You still have the forks. Ex: https://github.com/dmtrkun/bldc-ffb-joystick-base
  7. Just open the C47 in the encyclopedia while in VR The left eye will render the C47 with the number markings and the right eye without them:
  8. You're totally right, the positions doesn't make any sense with the voltage displayed. Let's hope they fix it soon
  9. This also can be solved by editing the file \Mods\aircraft\Mi-24P\Cockpit\Scripts\clickabledata.lua Change the line: elements["VOLT-AC-KNOB-PTR"] = multiposition_switch(_("AC Voltmeter knob"), devices.ELEC_INTERFACE, elec_commands.ACGangSwitcher, 91, 11, 0.0947, false, 0, nil, false) to elements["VOLT-AC-KNOB-PTR"] = multiposition_switch(_("AC Voltmeter knob"), devices.ELEC_INTERFACE, elec_commands.ACGangSwitcher, 91, 11, 0.081, false, 0, nil, false) It might be happening in other knobs, but playing with that number might help. I guess it's related to the angle it moves on each click. I tried with 1/11 (the 11 is the number of positions) as I did on the other bug but the positions are still weird. By trial and error I think that this number is the best we can get Both bugs are very easy to solve but I don't know it ED will fix them as they are not very game-breaking
  10. Finally fixed! I didn't managed to reproduce it with the last patch. Great work ED!
  11. Could it be done using lua? I guess that from lua you can call powershell with a command to play some internet radio? Powershell script: Add-Type -AssemblyName presentationCore $MediaPlayer = New-Object system.windows.media.mediaplayer $MediaPlayer.Open([uri]"http://streams.br-online.de/bayern3_2.m3u") $MediaPlayer.play() $wshell = New-Object -ComObject Wscript.Shell $wshell.Popup("Operation Completed",0,"Done",0x1) $MediaPlayer.stop() And then from lua something like: local script = [[ Add-Type -AssemblyName presentationCore $MediaPlayer = New-Object system.windows.media.mediaplayer $MediaPlayer.Open([uri]"http://streams.br-online.de/bayern3_2.m3u") $MediaPlayer.play() $wshell = New-Object -ComObject Wscript.Shell $wshell.Popup("Operation Completed",0,"Done",0x1) ]] -- Now create powershell process and feed script to its stdin local pipe = io.popen("powershell -command -", "w") pipe:write(script) pipe:close() Its just an idea. I'm not sure if DCS allows that, but running that lua code from the command prompt works....
  12. Sounds good. I think that somehow the error is related with the display of the lines of the waypoints as when you press over a unit you can also see their waypoints and that might be acumulating. Also, since now you can "trigger" the bug I saw that there's nothing written in the log so it's useless to attach it.
  13. I'm also affected by this bug as I have a 6900 but I've discovered that as long as you don't press the button "show all routes" in the map screen, the bug won't happen (or at least it didn't happen in my computer) so at least this is a workaround... @Flappie Perhaps this can make it easier for the devs to debug it as it seems to be linked with the display of the waypoints. Steps to reproduce: 1: Have an ATI card 2: Start the mission linked here: https://forums.eagle.ru/topic/268351-game-breaks-in-f10-while-gci/?do=findComment&comment=4762762 Select blue side, game master slot. It probably works with any other mission but that's how I did it at least... 3: Go to map view and make sure that the button "show all routes" is deactivated 4: Play with the map view by selecting different units, zoom in and out, press F8 over units to view them and go back to map view, etc... 5: Press the button "show all routes" and see how all the UI breaks down. If it doesn't, just deactivate it and go to step 4 to try again... It doesn't happen 100% of the times but it's quite easy to reproduce it consistently if you play with the map for 1 or 2 minutes Relevant GIF where the bug is shown:
  14. As you can see in the video: https://youtu.be/xDn1ugHtZi0?t=104 The signal flares are positioned in the tail part of the helicopter That would be the equivalent to this part of the helicopter in DCS (the colors of the flares should be painted in the texture also) But when you shoot a signal flare you can see how it comes from a weird position and angle compared to the KA-50 or Mi-8
  15. I posted this a month ago but in the wrong forum (https://forums.eagle.ru/topic/274687-invalid-selector-arrow-in-the-temperature-selector-solution-inside/?tab=comments#comment-4698057 so I will post it here so it gets properly tracked -- This selector should accept 10 positions but currently you only have 9, so they are not properly displayed and the arrow ends up in middle positions Trying to select 18 degrees (3 clicks) This can be solved by changing: elements["AC-TEMP-KNOB-PTR"] = multiposition_switch(_("Temperature Selector, 5/10/15/18/20/22/24/30/35/40/50"), devices.ECS_INTERFACE, ecs_commands.Temperature, 146, 11, 1/9, false, 0.0, anim_speed_default, false) to elements["AC-TEMP-KNOB-PTR"] = multiposition_switch(_("Temperature Selector, 5/10/15/18/20/22/24/30/35/40/50"), devices.ECS_INTERFACE, ecs_commands.Temperature, 146, 11, 1/10, false, 0.0, anim_speed_default, false) In the file ....\Mods\aircraft\Mi-24P\Cockpit\Scripts\clickabledata.lua (line 150) After the fix:
×
×
  • Create New...