Jump to content

Finlayson

Members
  • Posts

    11
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

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

  1. Hi guys, I have translated / created the missing texture and updated the cockpit livery. Attached find a ZIP with the new texture and updated description.lua. This is how it looks: Installation should be self-explanatory. Unzip and copy both files to your existing livery mod folder (<your DCS folder>\Mods\aircraft\AJS37\Liveries\AJS37cockpit\English). AJS English Cockpit Mod Update.zip @Devrim Feel free to include these files in your mod in case you find them "worthy"
  2. Hi, this has been pointed out before, but it seems it has somehow been forgotten...? Anyways, I did not want to necro an old longwinded thread, so here is a new one on the topic. The problem is that the following joystick bindings... {down = 8014, cockpit_device_id = devices.SYSTEMS, name = _("Throttle Idle Detent - Idle/Stop (toggle button)"), category ={_('Left Console'), _('Throttle lever'), _('Flight Control')}}, {down = device_commands.Button_118, up = device_commands.Button_118, cockpit_device_id = devices.SYSTEMS, value_down = 0.0, value_up = 0.5, name = _("Throttle Idle Detent - Idle/Stop (2 pos switch)"), category ={_('Left Console'), _('Throttle lever'), _('Flight Control')}}, {down = device_commands.Button_118, cockpit_device_id = devices.SYSTEMS, value_down = 0.5, name = _("Throttle Idle Detent - Idle"), category ={_('Left Console'), _('Throttle lever'), _('Flight Control')}}, {down = device_commands.Button_118, cockpit_device_id = devices.SYSTEMS, value_down = 0.0, name = _("Throttle Idle Detent - Stop"), category ={_('Left Console'), _('Throttle lever'), _('Flight Control')}}, ...as well as the following keyboard bindings... {combos = {{key = 'Home', reformers = {'RAlt'}}}, down = 8014, cockpit_device_id = devices.SYSTEMS, name = _("Throttle Idle Detent Toggle"), category ={_('Left Console'), _('Throttle lever'), _('Flight Control')}}, {combos = {{key = 'Home', reformers = {'RShift'}}}, down = device_commands.Button_118, cockpit_device_id = devices.SYSTEMS, value_down = 0.5, name = _("Throttle Idle Detent - Idle"), category ={_('Left Console'), _('Throttle lever'), _('Flight Control')}}, {combos = {{key = 'Home', reformers = {'RCtrl'}}}, down = device_commands.Button_118, cockpit_device_id = devices.SYSTEMS, value_down = 0.0, name = _("Throttle Idle Detent - Stop"), category ={_('Left Console'), _('Throttle lever'), _('Flight Control')}}, ...all do exactly the same thing: they all TOGGLE the state of the throttle detent between stop and idle. So no matter if you press RAlt+Home, RShift+Home or RCtrl+Home, you TOGGLE the throttle detent each time. While for the keyboard this is arguably just a small inconvenience / inconsistency, for the joystick bindings it makes it impossible to properly map a hardware throttle detent switch (like in the Thrustmaster Warthog throttle). Yes, you can of course "sync" the thing to the throttle by mouse click if it happens to be inverted, but that defeats the purpose of having the hardware switch in the first place. Can you please have a look at this and finally fix it? FYI, a long time ago there have been command codes 8015 and 8016 that properly set the throttle to stop/idle, but these stopped working (I would guess sometime during 2.7.x). Cheers, F.
  3. Yeah, that's what I suspected. Just wanted to confirm that is the case in RL. Thanks for the clarification.
  4. It seems the default cold-and-dark positions of the "Boost Pumps" and "AC Gen" switches have been changed from "off" to "on" in 55960. Is that a bug or a feature? When the aircraft is cold and dark, these should be off, right? Same thing is true for the original A-10C Warthog. Cheers, Fin
  5. <p> It seems the default cold-and-dark positions of the "Boost Pumps" and "AC Gen" switches have been changed from "off" to "on" in 55960. Is that a bug or a feature? When the aircraft is cold and dark, these should be off, right? Same thing is true for the A-10C II Tank Killer. Cheers, Fin </p>
  6. Well, it is difficult indeed to see stuff sometimes. However, in this special case, the reason for the difference you are seeing is simple: time of day.:smartass: As it seems, the time of day of this particular mission was changed when it was edited for the A-10C II. The original mission runs in the afternoon, the A-10C II mission runs in early morning. This is why the lighting looks very different, and this is most likely the reason for your target visibility difference. Cheers, Fin
  7. Just want to add that copying Config\Input\Aircrafts\Default\trackir\default.luafrom 1.5.3 to OB 1.5.4 actually also solves the snapview problem. Indeed the problem seems to be related to the same changes introduced for VR headtracker support as reported here.
  8. Yeah, it gives me the snapview. But the snapview is not fixed as it used to be, but it moves when you move your head (using TrackIR).
  9. Hi, I just opened the following ticket, and thought I'd post it here to prevent duplicate reports: I use snapviews regularly to be able to more precisely interact with clickable cockpits without TrackIR getting in the way. For me, the whole point of using snapviews in the context of TiR is that snapviews are *not* influenced by head movements. So I go through the "hassle" of setting up proper snapviews to my liking for each module. With the latest OB 1.54, these snapviews are rendered useless. And having to freeze TiR each time you use a snapview cannot be the solution here. I hope I am not the only person that feels this new behavior is a bug. :( I am pretty sure this problem could be fixed/worked around by messing with some LUA files (like SkateZilla suggested for another problem here), but I think this should really be fixed by ED so we do not have to patch it after each update...
  10. Fix for v1.5.x Yup, thankfully, it has been fixed. And for the impatient who want to also fly Warthog night missions with proper lighting on the Black sea map, here is how you can fix it for v1.5: Copy the following two files from your 2.0 OpenAlpha installation to the v1.5 OpenBeta: Mods\aircraft\A-10C\Cockpit\Shape\A10C-CPT.EDM Mods\aircraft\A-10C\Cockpit\Scripts\LightSystem\LightSystem.lua Copying the LightSystem.lua is not strictly necessary, but I'd recommend it. I'd also recommend to use JSGME (see http://forums.eagle.ru/showthread.php?t=98607) for this. Have fun! :joystick: [EDIT] With the release of OpenBeta 1.5.2.48162, this fix has been incorporated.
  11. Yep, same problem here. However, upon closer inspection, I found the fix. Two of the textures are present in the original ZIP with different name. So to get this to work, starting from Devrim's original v1.2 mod, you have to do the following: First, fix the folder structure as pointed out by Vandal71 above: Second, rename two textures: su25t-cpt-tex-02.tga.dds -> SU25T-CPT-TEX-02.dds su25t-cpt-tex-04.tga.dds -> SU25T-CPT-TEX-04.dds That should do the trick. If you are paranoid, do not rename the files, but make a copy of each and rename the copy. This way, should the old texture name still be used under some conditions, it will be there. Dunno if this is actually a bug in 1.5.0 or due to a change in ED's development tools or naming scheme, but until this gets sorted out, the above works. Have fun, and a big thank you goes to Devrim for his excellent work on these textures :thumbup:
×
×
  • Create New...