tietze

Updated package available here: http://dl.dropbox.com/u/2910357/fsim/JSGME/Ricardos%20Blue%20HD%20cockpit.zip *********************** * RICARDO HD Blue pit * *********************** These texture files is the work of Ricardo and further adjustments by Devrim packed into a JSGME-friendly zipfile for easy installation. I have done nothing but packaged and zipped the files together and corrected a spelling mistake on the left rear panel. Have fun! Jørgen Tietze <tietze@mail.dk> Link to more information about JSGME [url]http://forums.eagle.ru/showthread.php?t=98607[/url] JSGM installation ----------------- Extract the contents of the JSGME zip file into your JSGME mods directory. Manual installation ------------------- 1) Move or remove the following files: DCS World\Mods\aircrafts\Ka-50\Liveries\Cockpit_Ka-50\english\*.dds 2) Copy description.lua into: DCS World\Mods\aircrafts\Ka-50\Liveries\Cockpit_Ka-50\english\ 3) Copy the texture package "Cockpit-Ka-50 Textures.zip" into: DCS World\Mods\aircrafts\Ka-50\Cockpit\Resources\Model\Textures Further information ------------------- The readme's and Links to original files is collected in the directory "links and readme files". For more information check out the following thread on the Eagle Dynamics forums: [url]http://forums.eagle.ru/showthread.php?t=99751[/url] Ricardos KA-50Textures.zip [url]http://www.lockonfiles.com/files/file/2447-ricardo-hd-ka-50-english-blue-pit[/url] compass fix by Devrim [url]http://forums.eagle.ru/showpost.php?p=1676795[/url] description.lua by Devrim [url]http://forums.eagle.ru/showpost.php?p=1681638[/url] fix_adfknob by Devrim [url]http://forums.eagle.ru/showpost.php?p=1802234&postcount=148[/url]

Just discovered one error in the blue pit - on the left back panel (File: Ka-50 Panel L.dds) the hydraulic pressure for the wheel brake is spelled "WHELL BRK", pretty easy to fix (could just copy the "E" and place it above the extra "L"), but using gimp, what format and what compression would you save the texture in? Edit: just to answer that myself - Compression set to "BC1/ DXT1" and set Mipmaps to "Generate mipmaps".

It looks good, but I'm getting flickering shadows in the water with this mod (ATI gfx).

Thanks for the update on the gas struts - tried out with two 100nm found on ebay and it feels good, but I guess 50nm will be sufficient. I just hope that they wont rip the pedals apart before the weaker door hinges arrive ;-)

No, you would need to replace the zip archive. Another way would be to place the files you would like to add into a directory with the same name (without file extensions) as the archive and place your files there.

Yeah it is the dark red one just below the HSI on the left foward panel. It is called "laser designator reset button" and activated with LAlt+LCtrl+O:

Apparently it has not been mentioned, but you can shorten laser usage by resetting it with the laser reset switch. For example the laser keeps firing on even when target has been destroyed.

It is only relevant for the KA-50 and only concerns files for the KA-50. The two others already have this functionality :-)

Certainly not! It's great :-)

The HUD (and doppler) not repaired bug is acknowledged, but has never been fixed. Checkout those threads: BS2 1.2.x bugs and glitches thread (not CTD/BSOD) HUD has not been repaired in BS2 1.2.0 KA-50: HUD not repaired

It worked with open beta. Will test more tonight :-)

Would probably (or hopefully) not work in multiplayer.

While having your coffee enjoy the sound and following music (6minutes and 27 seconds in) - it's great and I wish for an in-cockpit walkman with a select collection of tapes :pilotfly: http://www.youtube.com/watch?v=HCnBIf9Gt44&t=6m27s

It is already confirmed by Nate from ED Testers team. That said it would be nice to see it fixed together with some if not all of the other bugs related to the KA-50. It is probably not hard, but still requires someone to but their mind, work and resources into coding of the KA-50 which is probably not very present for anyone. I understand multiplayer (1.2.7 open beta) and EDGE being of highest priority at the moment.

For you:

Ok, figured it out: you need a damaged aircraft to get a repair!

Sorry, but when you say that everything works fine, have you tried the above attached mission (now 2 versions for either latest non-beta and latest beta)? On FARP: Rearming, refueling, ground power, turbo gear, NVG installation, and HMD/HMS installation works fine. Ground crew copies the request to repair but the repair countdown timer is not started and repair is not commenced. Repair is commenced without problems when requested on a non-civilian airfield. Here is a screenshot of the FARP with labels on, to show what vehicles is parked there: Just for good measure here is the relevant part of FARP.lua: local objects_by_type = { [RUSSIAN_FARP] = { groundCrew = { [RESOURCE_AMMO] = { "URAL_4320_B", "SetkaKP" }, [RESOURCE_FUEL] = { "URAL_ATZ-10", "ATZ-10", "ATZ-60", "GSM Rus" }, [RESOURCE_ELEC_POWER] = {"Zil_APA-80", "URAL-APA" }, [RESOURCE_GROUND_SERVICE] = { "UAZ-469", "Ural_4320-31", "Ural_4320_T", "Zil_KUNG", "KAMAZ-TENT", "PalatkaB", --self "URAL_4320_B", "SetkaKP", -- ammo "URAL_ATZ-10", "ATZ-10", "ATZ-60", "GSM Rus", --fuel "Zil_APA-80", "URAL-APA", --elec power "Zil_SKP-11", "KP_UG" -- control point }, }, ATC = { [RESOURCE_ATC] = { "Zil_SKP-11", "KP_UG" } }, FARP = { [RESOURCE_NIGHT_ILLUMINATION] = { "Zil_SKP-11" } } }, [WESTERN_FARP] = { groundCrew = { [RESOURCE_AMMO] = { "M-818" }, [RESOURCE_FUEL] = { "HEMTT", "GSM Rus" }, [RESOURCE_ELEC_POWER] = { "M-818" }, [RESOURCE_GROUND_SERVICE] = { "M-818", "PalatkaB", --self "M-818", --ammo "HEMTT", "GSM Rus", --fuel "M-818", -- elec power "HMMWV_M1025", "KP_UG" --control point } }, ATC = { [RESOURCE_ATC] = { "HMMWV_M1025", "KP_UG" } }, FARP = { [RESOURCE_NIGHT_ILLUMINATION] = { "HMMWV_M1025" } } } }

Trying to repair a western KA-50 with appropriate vehicles (APC 1025 HMMWV, Transport M818, HEMTT TFFT) in place at FARP results in a "copy" from ground crew, but no repair is initiated (count down is not starting and no repair is commenced after 3 minutes). Example mission attached (vehicles both added as static and vehicles as well as all FARP support buildings added - still no cigar): farp-test.miz & farp-test-openbeta.miz. DCS World 1.2.6.20768 & DCS World 1.2.7.22412. farp-test.miz farp-test-openbeta.miz

DCS SU-25 Flaming Cliffs Happy holidays! :-)

Looks great! :-)

Thanks for the update!

A public bug tracking system will not silence the discussion and remove every problem interfacing users, forums, testers and developers. It will be another tool to interact with users, govern bug fixing and perform strategical communication. In that regard when mentioning a bug tracking system requires work and maintenance I was just pointing out that it would require resources and prioritization from ED, not just increase work load for moderators. ... and yes, OT again... :pilotfly:

Same as they do now, but the difference is that the bug is acknowledged. That assumes the bugtracker is moderated and maintained. Which requires work and making public priorities and possibly technicalities that needs explanation. It is a service that could benefit both or no-one depending on how it is implemented and used. I do not think ED wins anything in the long run by keeping silent or do what might look like obfuscating what is going on behind the curtain. But that is a question of strategy. Where do you want your users, testers, developers and what role do/should they play for your software? What kind of commitment? But if the bug is not going to be fixed anyway there is of course no reason to have a public bugtracker!

Serial: 1206 Location: Aarhus, Denmark