doveman

I think I've got a Deadzone but let me check. As mentioned, I think I managed to minimise the problem in Central Trimmer mode by making the Recentre zone very small in mods/aircrafts/KA-50/FM/FMOptions.lua like so (the values were 4x this before): ----------- for new helicopter trimmer method ----------------------------------------------- ----------- (joystick will be disable after trim until it come to neutral zone) ------------- HelicopterTrimmerZonePitch = 0.05 HelicopterTrimmerZoneRoll = 0.05 HelicopterTrimmerZoneRudder = 0.1 which kinda makes sense as if I'm clicking Trim whilst the stick is already in the Recentre zone, it's going to trim, think it's recentred and therefore "unlock" the stick and register the current position as additional input. However, when I release the stick this additional input should be removed as it's not trimmed in and this doesn't happen so it doesn't really explain it.

Yes, I just used the keyboard T to ensure I wasn't nudging the stick. Thanks. I'm just thinking that in RL the pilot has the ability to do this, i.e. click Trim then make a small adjustment and click it again and with the current methods which require us to recentre between each click we don't. It's obviously pretty much impossible to get the stick back from centre to exactly where it was when you last clicked Trim, so it's likely that the next time you click it, it will be quite a way off from the first click. Sure, when aggressively maneuvering trim isn't really needed (I tend to use the hold-Trim method for that rather than engage FD, mainly because when I need to do so it's because I'm being targeted and I don't have time to fiddle around with my mouse to click on FD. I need to try and remember to toggle it on with my voice control software though). It's more when stopping such maneuvering and wanting to stabilise or just in general flight that the first click of trim might not get it exactly where I want it (particularly with the oversteer problem) and it'd be useful to be able to adjust the Trim without having to recentre the stick in-between. I think so but I'll re-test without that.

Thanks for taking a look Yurgon and confirming that you (probably) observe this as well.

Same to you mate! I posted a video in my thread here http://forums.eagle.ru/showpost.php?p=1661763&postcount=76 showing how the stick jerks when clicking Trim, which in the air causes the helo to oversteer which can be fatal. After manually editing the TrimmerZones I was able to use Trim without it making the helo oversteer but only in Central Trimmer mode, the other mode is still unusable for me. Whether the modelling is perfect in BS2 or not, there's all these config files that can clearly make things not work properly, which obviously doesn't apply to RL, so just because it works for you doesn't mean it isn't broken for others. Please feel free to test and see if your stick jerks the same as mine when clicking Trim on the ground (or in the air). I note no-one who insisted that Trim is working fine could be bothered to watch my tracks I posted http://forums.eagle.ru/showpost.php?p=1652472&postcount=35 or comment on Daniel M or my videos http://forums.eagle.ru/showpost.php?p=1655247&postcount=37 or comment on ZaltysZ's posts http://forums.eagle.ru/showpost.php?p=1660099&postcount=60

OK, sounds like something strange is happening there then. Maybe it will help point to where the problem lies. Just to clarify, I don't have any problems exiting the Briefing screen but if I click on either of the buttons Back or Fly, rather than pressing Esc, my mouse cockpit no longer works (i.e. I can't look around).

Hey man, that's too many hours working, I'd be too tired for BS2 too after that :( I think the RAMdisk should be OK as when I've monitored DCS it only uses about 3GB and I've got 16GB, so I use a 9GB RAMDisk and that leaves plenty spare for DCS to run in. I've played with FancyCache for Volume as well which is interesting as it caches any data read from the monitored Volume(s) so that if it's re-requested later in can be loaded from RAM instead of disk. It obviously won't speed up the initial loading time but could make things a lot smoother on subsequent flights over the same terrain. It's in beta testing at the moment and can be tried out on a 30-day rolling trial I think http://www.romexsoftware.com/en-us/fancy-cache/index.html

OK. How about just loading it from commandline and starting it by pressing the Start button, as this works if I launch with the shortcut but if I paste the same line into the commandline, pressing Start gives "Error loading profile". The line taken from the shortcut is "C:\Program Files (x86)\SCSimulations\Helios\HeliosControlCenter.exe" -d "Helios" Actually, maybe I can work round this by launching the shortcut from my batch like this instead "E:\DCS\Helios Control Center.lnk"

I'll have to check again but even running from RAMdrive, which is much faster than SSD, I found the loadtimes were more like 60-90s than 20-30s.

I've found if I exit the Briefing screen by pressing Esc, it works but not if I click Back or Fly. So if I remember I can access the Briefing and still play the mission but I'll probably forget sometimes, making me abort the mission so this does need fixing.

I've found that if I exit the Briefing screen by pressing Esc it doesn't break the mouse cockpit, so at least I've got a way to use the Briefing whilst flying now. They should still fix this bug where it stops working after clicking Back or Fly though, as I'm bound to forget and click one of those sometime, ruining my mission.

Well it seems it only worked the once and hasn't since. I haven't re-enabled those two mods either. I've tested using FaceTrackNoIR and the headtracking doesn't stop working after pressing Esc and viewing the briefing, it's just the mouse cockpit that no longer works. Can't really use the sim at the moment as I often feel the need to check the briefing during flight and doing so makes my helo inoperational!

It's quite strange as I have three .lua for my Thrustmaster Hotas X but only one for my Xbox360 controller, which I plug/unplug quite often whilst the Hotas X stays plugged in most of the time, unless I'm re-cabling. The three Hotas X files are dated the 8/01, 10/01 and 20/02. Perhaps it creates a new lua when the same controller is connected to a different port and maybe I did that two or three times recently (I don't recall but it's possible) as there's six or seven ports on the back of the hub, which is where I connect it. The Xbox360 controller always gets plugged into the front hub ports, of which there's only two so perhaps I've been lucky and always plugged it into the same one by chance.

I'm making a batchfile to setup all the apps I need loaded before DCS World but I can't get Helios to work. If I launch it from it's icon it works fine but I'd like to launch it and autostart it with the correct profile. However, launching it from the commandline results in it giving "Error loading profile" when clicking start, irrespective of which profile I select. The commandline I've been using is: "C:\Program Files (x86)\SCSimulations\Helios\HeliosControlCenter.exe" -d "Helios" -t I don't recall where I got this from or what the switches are supposed to do but if I change "Helios" to the full path to my profiles folder E:\Data\Main\My Documents\Helios\Profiles, it creates empty folders in there, which mirror the folders in the parent folder (Images, Panel Templates, etc) and if I try that path, E:\Data\Main\My Documents\Helios it just crashes on launching. Does anyone know how, or if it's even possible, to launch Helios with a particular profile (or even the last one) auto-started?

It's funny because I've just been mapping the keyboard keys to my Thrustmaster Hotas X's single hat and hadn't really noticed how slow using the keys/hat is. I just tried using one of the sticks on my Xbox360 controller mapped to the Shvkal axes instead and used Jorge's suggested settings, simply because I don't really know what I'm doing with the curves or how the Shvkal should "feel" using an analog stick so I had to start somewhere! It's probably too sensitive, with it quite hard to move the stick just a small amount for fine corrections but it's amazing how fast I can move the Shvkal using the stick compared to the keys. So I guess I just need to find a balance that allows both fine and fast control easily. Until then I'll just map the other stick on the controller with the keys so that I can use that for fine control if needed. I'm using Xpadder which complicates matters a bit as that has deadzone and diagonal size settings to worry about as well. Whilst it is possible to remove either or both sticks from Xpadder, so that they're not processed by it at all, a) that's a controller-profile, not a game-profile, setting so I'd have to manually keep enabling/disabling them depending on what game I'm playing and b) then I wouldn't be able to map the keys to the second stick (or the zoom/gate size keys to the d-pad). Thinking about it, I might be able to do the first stick and the buttons mappings directly in DCSW without needing Xpadder but I don't think I'll be able to map the second stick to the Shvkal keys without it as DCSW will just see it as an axis. If I can tune the first stick so that I don't need to use the second stick at all, that would solve that problem though.

Yeah, I did consider getting the X52 Pro but decided I couldn't justify spending over £100 on a HOTAS when I wasn't sure how much time I'd spend with Black Shark, so just got the Thrustmaster Hotas X for £25 instead. I'm using voice commands to do a lot of stuff in the cockpit which makes up for the lack of physical switches and the software (Voice Assisted Commands) only cost me £10 :)

Ah gotcha. I do have a Xbox360 controller that I use on my PC, mostly for games I want to play on the TV from my sofa. I did consider using it as well as my joystick with DCS world for the extra controls but it's a bit fiddly as it tends to slide around the desk so you really need to let go of the stick and pick it up. I'm also a bit cramped for space on my desk at the moment. I'm building a new PC desk soon though, so I think what I'll do is incorporate a recess or something that will hold the controller in place so that I can use it with my left hand and still keep my right hand on the stick.

Awesome. Looking forward to playing with this :)

Ah, thanks for protecting me from my own stupidity :smilewink:

Ah, I see. I created a JSGME folder for it and must have not dragged that .exe from the zip into the folder. :doh: As I said, it seems to work well enough without it though (apart from the error) and the .ini is updated and the fonts are changed, so I'm not sure what it does but I'll put it in place to avoid the error.

No actually. The two .exe and one .ini are all together in the root of DCS World.

Hi Peter I get an error when clicking on the radio menu to set the position, although it does write the position to Clickable_Radio_Menu.ini each time I clicked, so it doesn't really matter. The error is:

I suppose it would be great if I could use my stick axis whilst holding a button to control the Shvkal (currently I use Xpadder so that whilst holding my Trigger, the hat is mapped to the Shkval direction keys) but unfortunately I don't think that's possible, at least not without banking/pitching the helo at the same time. What axis were you thinking of?

Thanks but that didn't make any difference.

Hmm, I thought it might be a recent mod I'd added that was causing it but I've just tested with no mods and it's not working still. I even tested with the mission it was working on earlier (with all my mods) and it's not working on that now either, so it doesn't appear to be mod or mission related (tested with three missions). When it was working earlier, I was using SoftTH/Helios but I've tried disabling that as well now and it still happens. I tried killing RadeonPro and MSI Afterburner just in case but no difference. It doesn't matter whether I exit the briefing screen with Back or Fly, no ability to move the cockpit view with the mouse afterwards, although the numpad still works. EDIT: Tried doing a Repair with all mods disabled but that didn't make any difference either.

Thanks for testing. The problem was that the mouse cockpit no longer worked (i.e. I couldn't look around), not that the mouse cursor came on. However, I just played a mission and it was OK. I disabled a couple of mods yesterday though (ConfigTweaksHIGHGeneric_v2.0 and SmallFX_v1.0), so it may have been something about one of those that was causing it. I'll have to do some more testing with them enabled/disabled and on other missions to see if I can narrow it down.