tietze

I tried to contact support and it was stated that the cut-off levers are toggle-switches. The only way is to create a lua script that does a conditional activation of the cut-off lever. At the moment I have no idea how to access the switch state through lua-code (but I have a plan to learn how to do so in the nearest future), but I would like to do so - now that this is the only possible way :-)

I'm not quite sure I understand you correctly. What Helios does is to install a script in the old export folder, which is ignored by newer versions of DCS.

Lovely! More frankenPeters ;-)

And cut-off levers are not working as expected when sending value 0 and 1 to the Engine Interface, as described below. (posted as ED support ticket, so they are probably aware - will post if I get any news on the subject)

You can add "Doppler NAV System not repairable". I still find the format with all the colors and nomenclature quite confusing.

It is perfectly understandable :)

Try to fly at 250km/h or more below 5m (radar alt) - you'll get a slideshow (DCS 1.2.3.10201)! But please not that not all types of ground create dust when flying over them. Those that does results in slideshows. Just hovering and flying at lower speeds will not produce drop in FPS. (Instant Action/ KA-50 attack insurgents is a fine mission for testing how both dust cloud (after targets are destroyed) and rocket explosion (during mi-24 attack runs) creates big hits for fps) Note that what goes on in the mission (weather, number of units and what they are doing) can also have severe effects on FPS, as well as multiplayer is usually more demanding than single player (probably also due to mission complexities).

[edit: partially sniped by ijozic] But how do you end up with the conclusion that the AMD cards are bad? (reviews, examples, experiences or?) Does the Nvidia cards solve the DCS problems with: Trails of dustclouds causing drop i FPS (flying below 5m or so at higher speeds) Multiple rocket explosions causing drop in FPS (stated above by TZeer to be solved with nvidia card) Cluster bombs causing drop in FPS I agree that an amount of VRAM above 1.5gb is enough for the moment.

Stick with the first part of your sentence, they're mostly the same: http://www.anandtech.com/bench/Product/508?vs=555 The biggest difference will be the price and amount of VRAM.

:lol: (did it really nicely so it (hopefully) will be easy to desolder, but time will tell ;) (though I did even use shrink tubing as well, such a waste ;)))

No joking, google safe search: off ;)

That looks great as well Hans - did you heat the tube to get it into that shape? I must admit I couldn't wait for the PS/2-extension cable to arrive, so I cannibalized a ps2->usb connector and soldered the wires directly onto the pins in the joy handle (sorry, that is really a ghetto solution ;) ).

No I don't have any part numbers - I tried to search on the net beforehand but found out a visit to the local Bauhaus solved all the googling. The main part was the (rather expensive 10) Gardena squarish gardenhose connector. It is cylindrical, which makes it easy to lump together with some plastic tubing. I would recommend putting the joyhandle in a backpack and visit a local hardware store selling all kinds of garden and DIY stuff and just browse until you find the inexpensive and workable parts that can be fitted together. The plastic/ PP sewer tube is quite a common article here in DK, so I don't know how that would apply in the UK.

I really like hardware so I was just looking for some non-blurred (high-res) photos of the hogs internals, private parts, chips and so on. I guess I'm looking for hardware pr0n ;-)

Yes another DIY Warthog stick extension branded Gardena. Went to Bauhaus and bought some sewer tube, screws and Gardena fittings. The extension ended up extending the stick 11cm and is made of 40mm sewer tube that makes a tight fit with the Gardena fittings. Removed the rubber-gaskets and filled them with hot glue instead. Everything fastened with a lot of screws (mostly for fun). Easily disassembled and packed under the table, when not in use :-) Result

I've set zoom on the right toe-brake of the rudder pedals. As this axis is quite jerky, I just use it as zoomed completely in or zoomed completely out. As I don't like to fly around with FOV 120, I have set the max zoomed out level to FOV 70 in view.lua.

Great thread - has anyone taken it apart yet and investigated the ministick?

It is not simple, but still should be possible to be found out :-) In the bindings in the lower part of the profile editor window you have to drag items from Actions (left column) and over to Bindings (right column). For example click on the (1) HSI instrument picture. You will see the possible bindings on the (2) right column "bindings" and on (3) the left column you can find the HSI and drag the available actions to a bindings. Do it for all instruments. Save and it should work. And it is a bit of work to get it all done. I must admit I don't know if there is an easier way. There probably is, but haven't found it yet :-)

Ok, I just checked your files. It seems that the gadroc-profile have no bindings on the keys and indicators (clicking on an indicator like HSI and checking bindings reveals that they are all empty). So on to binding everything, then it will work :-)

I find that setting the WGS-84 ellipsoid results in wrong location of the KA-50 on the ABRIS map in DCS 1.2.3.10201. For example checking runway/ airfield. Can anyone confirm this?

I always start with jettison external stores and expedite remaining vikhrs immediately when I know the engine fail is permanent.

Lol ;-) Luckily not so many crashes anymore though - would love to see some bug-squashing in the KA-50 module though :-)

Thanks, would you care to zip the image, so it does not load inside the browser? :-)

Ok, I've been flying a bit with the proper neck in the KA-50 and for me it was quite a nuisance that the HUD disappeared everytime I just looked a little up. It has worked to change the initial head position, by editing the SnapViewsDefault.lua. Changing variable "y_trans" (it looks like a string in an array or - ok I have to learn lua scripting at some point) on line 973 from value "0.022388909581826" to "-0.02": Snap[9][13]["y_trans"] = -0.02 --0.022388909581826 What values have worked for you guys?

Just got thumbs up for posting Ricardos blue HD pit as JSGME-zip. Updated original post. Link is also here: Ricardos Blue HD cockpit.zip