Cloudie

Sorry I deleted my message, it was totally my fault. It was a mod for the HUD color that broke with the update, disabled the mod and the JHMCS is visible now.

Capt Zeen could you update the download on your site with the init.luas you are using, since the original ones broke in the last DCS beta update? I'm curious to try what you are using, since I could not fix the thick lines even after following your steps. Even after removing everything from your package and just using default RIGHT and LEFT_MFCD in monitor config, the lines are very thick, so it could even be a problem with DCS resolution (using 3440x1440+1920x1080 for Helios) that ED have to fix. I have to change the values in MDG_strokesDefs.lua or set "shaderLineParamsUpdatable = false" but the result is not as good as before the patch.

The problem with this, for me at least, is that the HUD and DDIs become a little bit too crispy, and show aliasing. But I will try these settings when I'm home, hoping that the hud does not fade away.

@RightStuff these values would be perfect to play with if they also didn't change the thickness/alpha of the HUD. Do you know if there is a way to tune the HUD itself with similar values somewhere else? I searched some HUD-related luas but found nothing...

I've tried this solution and it works quite perfectly (with different values) for the exports BUT it completely destroyed HUD and to a lesser extent DDIs on the plane: https://i.imgur.com/Dq0v4CN.jpg Note that above I had set the values as 0.2 and 0.1 respectively. With 0.4 and 0.2 like suggested it was still quite bold to me, not as my first screenshots (post #104) but still "worng" and the HUD, while readable, was noticeably thinner. DDIs in the plane were OK. I've tried Cpt's solution after my post but there was no change at all from my starting point unfortunately. For now I'm using the original files from before the patch, changing only shaderLineParamsUpdatable = false because it's the most playable to me, even if some aliasing was introduced in the DDIs both plane and exports. Too bad it was perfect before the patch...

Same here, these are my exports now, which worked flawlessly before the update: If I set the first parameter "shaderLineParamsUpdatable" to false it's playable, but worse than before. Is this even something we can fix ourselves?

Sorry but which is it? Wrong weather conditions or it really is a known bug? Can anyone confirm that they see them in their game (2.5.2 beta) and if so point out an instant action mission or tutorial where they do, so we will have the same conditions? I remember seeing them all the time on the instant action missions on the A-10C, but from the release of the F/A-18C they do not appear anymore in both aircrafts, for me. Contrails and the LEX vaport on the Hornet works, tho.

Thanks, that was it. I couldn't fix it with the instructions in the FAQ, until I figured out it was the .layout file and not the .hpf that had to be modified. :music_whistling: Weird bug considering I used the same monitor configuration with other profiles, but glad it's alright now... thanks again for your kind support

Looks that way to me, too, but I really can't figure out what is wrong. For the first issue, i copied the profile in the Helios/Profiles folder: https://i.imgur.com/xfRHHn8.png And the images in the Helios/Images folder: https://i.imgur.com/V9W22va.png I've run Profile Editor, opened the profile and run Reset Monitors successfully: https://i.imgur.com/DtDHGPo.jpg Then I simply load the profile, as usual (used Helios with the A-10C for years and years): https://i.imgur.com/68B25zx.jpg As you can see, I tried AUX, LFT2, BRKS, but nothing pops up. Regarding the second issue, copied the .lua in the Scripts: https://i.imgur.com/ECSeaYO.png If I load Loz's A-10C profile in Helios, it works normally with that same .lua. That's what's really strange here. Can't really figure out what I'm doing wrong, I do this kind modifications pretty often (Helios for A-10C, DCS-BIOS, sim shaker, etc)... I must be missing something for sure. I've downloaded the rar again and cleaned a bit the folders, but it's the same as before :cry: Thanks for any input, really appreciate it!

The quality is amazing but unfortunately I have two issues at the moment :( First of all, the "green" extra buttons (like AUX, LFT, RGT, NAV, ABOUT, etc) are not working at all for me; I tried outside the game, left or right click, but nothing happens, only the green line under it. All the buttons and switches responds correctly at both touch and mouse inputs, so it's working to some extent. Helios is at the latest version 1.3.190.448 The biggest issue I have unfortunately is that the buttons and gauges are not working at all in game, and it is very wierd. With the same Export.lua I copied from the rar, untouched, the CapLoz A-10C profile works as expected, both gauges and inputs, but the F/A-18C profile is completely dead. I've tried all I could and I'm sure I've copied all the files in the right place, now I don't know where I could be wrong... Do anyone have similar issues? Any help is really appreciated And thanks again Capt, this is really an amazing work and can't wait to get it working (the viewports work flawlessly, outstanding)!

Thank you very much for your work, I can't wait to try it tonight as soon as I get home. This will be a game changer, you are truly the best!

Solved by changing USB port, it was on a PCI-E multi-port and now it's on the mainboard working just fine. I suspect that the Windows 10 "device setup" that happened after I switched USB did something too, but can't be sure about that. Anyways it's working normally now, thank you both for your kind help!

Thanks for your advice, I will try to connect it directly to the PC and test it again. I haven't changed the usb connections for a long time, and it worked perfectly before, but I'm aware that maybe something changed in the meantime (window/dcs software update or even the hub malfunctioning) so that's the first thing I will try tonight, thanks!

Honestly I don't remember, but I'm pretty sure that it's via hub. Tonight I will try to move some cables, yesterday I tried to solve it via software but could just be an hardware issue: I stopped using DCS for some months and the issue could have appeared after a windows update or DCS update, I remember it was working flawlessly before. As soon as I get home I will try to troubleshoot more, thanks for your help for now!

Unfortunately it's pretty random but it happens within the first minute (sometimes seconds) after I launch a mission, after some high G turns for example. I don't think a track would help specifically. I also noticed, while trying to fire the gun in the A-10C or F-15, that sometimes the effect on the seat is a bit delayed or that it does not register at all. Never got it "stuck" while firing the gun tho. I fear that it could be an issue with the JetSeat firmware, because the SimShaker debug view seems to work normally when the seat just continues to vibrate. Tonight I will try to reinstall the seat drivers too, or maybe I will try to change the USB port before that... even if I don't have any issues with all the tests in SimShaker and the JetSeat app.

Hello, I have a strange issue with SimShaker (tried both stable and beta) and DCS 2.5.1: everything seems to work normally when I start a new mission, but after about 30 seconds of maneuvering the aircraft, the vibration becomes "stuck" and the only way to make it stop is by turning off the power of the JetSeat. The DCS Debug View in SimShaker continues to work normally even when the vibration is "stuck" At first I though it was a confict with DCS-BIOS but the issue also happens with a completely clean export.lua (with just the two simshaker lines) after a reinstall. Any idea to fix this issue? Thanks a lot for any suggestion!

Thanks for your reply, I double checked everything you mentioned and remembered that when I updated I didn't copy the DCS-BIOS folder into the Script folder in Saved Games (everything else was working because I still had the 0.5.0 folder). Sure enough, now even the four SAS switches are working properly! And with that my first panel is finally complete! Thanks a lot Ian for all the work you put into this project, without DCS-BIOS I doubt I could have reached the same results. Cheers!

I'm back at home too, I downloaded the latest version (5.1), updated my Arduino project with the switch2pos version but... like when I tried manually yesterday, the switch does nothing in the sim :( If I pause and look at the terminal I can see the switch is working: < 2017/02/22 23:06:43.668689 length=17 from=168 to=184 SASP_YAW_SAS_L 0 < 2017/02/22 23:06:44.271015 length=17 from=185 to=201 SASP_YAW_SAS_L 1 But in the sim nothing happens unfortunately. Any ideas? Ian?

Thanks, I tried that yesterday but I didn't get them to work. Anyways, nevermind, I checked the control-reference now and noticed that it's already a switch2pos, eg. DcsBios::Switch2Pos saspPitchSasL("SASP_PITCH_SAS_L", PIN); There's not that "PUSH" argument and it's not an actionbutton anymore. Maybe I had an outdated version. I'll change my code and update my DCS-BIOS folders tonight, cheers

Sorry for the noobish question but since we're talking about the SAS switches, is there a way to let them work like a normal switch2pos instead of an electrically held switch? My panel is quite simple and I could never emulate that kind of switch, and for some reason sometimes one of the 4 SAS switches does not work and I have to switch it off and on again. A simple switch2pos would resolve that but I don't know how to "convert" it, if it is even possible... Thanks for any input!

The package arrived yesterday! I was actually very surprised by the speed of the delivery (Andrey shipped it on the 23rd jan, entered customs on the 1st, released on the 8th and arrived on the 9th at my door). Wow! The product is really plug&play, I had installed SimShaker already and it worked just by plugging the power and the USB! Ran the test, then a round of massage, and it was time to fly: my first try was pretty rushed unfortunately, and I was dressed heavily cause I had to go out soon; using the speakers the noise of the motors is pretty noticeable but I was impressed by all the effects modelled: take off, a gun pass, landing, it all worked! As soon as I was back home I gave it another run, this time with proper flight gear (trackIR, big over ear headphones and a light pajamas...) and I was blown away. Really. The vibe motor noise disappears and the immersion is incredible (tried a night flight in Vegas with the A-10C). Then I loaded a mission on the F-15 with G forces enable and... what a rush!! You get the same feeling you have when you drive a car, except every sharp turn makes it difficult to stay still on the seat, awesome. Really had a hard time turning off DCS yesterday... Also before bed-time I tested the sound mode briefly and worked like a charm, it's just a passthrough where you have to plug the chair audio jack to the PC (or even ipod/phone I guess) and headphones and it just works, the higher the volume of the source the better. Thank you Andrey for your service and thanks to all the team for the SimShaker software, I don't think I will ever fly without it now!! :thumbup:

Hey Chicki, I can answer since we are on the same boat, got my 908 shipped quite recently. The tracking for the russian post is here: https://www.pochta.ru/tracking (you can use google translate to get the gist of it) You could also try this site which is more non-ru friendly http://www.trackitonline.ru/ Also know that for those international shipping you may notice that the tracking seems to stop for a week or more at times, but that's because our package may be stuck at customs (both outbound from Russia and inbound to your country) and that may take a while :)

I had it at 0.067 and didn't notice any problem, but I'll try 0.016 anyways, thanks

Hmm is this in Export.lua? How's the variable called exactly?

As far as I remember from when I did it the first time I installed Helios, it's the Helios setup program that generates the Export.lua and places it there, when you have to point the install folder. I could be wrong tho, I just copied the one that worked in 1.28 SavedGames folder into the DCS.openbeta\Scripts folder (also in SavedGames ofc)