Holton181

Osäkring (i presume it's an 'ä' and not an 'a') in this context: O- = Un- säkring = safe Osäkring = unsafe

Compared to real world it kind of is. In reality it's actually quite hard to enter VRS by purpose. It's very exaggerated in DCS in general (all choppers). My belief is that ED try to force helo pilots to be more careful (as they are IRL) and not just slam the chopper down in an unrealistic way.

This is the Viggen subforum, please move to the F-14 one.

Sorry for the necro, but has anyone any insight on this? the new 2020 DCSW manual simply states: But I can't find anything in the NS 430 manual. Previous old DCSW manual states it being for A-10C only.

[emoji106]

I don't have a screen shot to prove it, but it worked for me in 2.5.6 with an air start.

Thanks a lot! Yes, I just found info that this might work (see my edit to my last post, probably done after you quoted me and before I saw your answer...), and you just proved it!

If this is true (source?), for MODs where a part of it went into the Sounds folder, it should work if that part was "removed" and located directly in the Saved Games/Sounds while the rest of it stay as is, no need for any changes other than that? For instance the Skullz Genuine Huey Sound Mod, containing edits/additions to both the Mods and Sounds folder. Putting the content of the MOD Sounds folder in saved Saved Games/Sounds while keeping the rest in the root game folder? EDIT: No need to answer, a guy called ristod76 just tested it with Skullz MOD and it works! Thanks!

@sSkullZnBoneZz Hi, I have the UH-1H Skullz's Genuine Huey Sound Mod 3.0 (and 2.5) and like it a lot! Big thank You! Unfortunately, now with 2.5.6 the entire Sounds folder is gone and I don't know if this MOD will still work. I don't have time to test it right now, but I doubt it will work due to how they seams to have changed the way they handle sounds now. Pretty early to ask I know, I'm sorry, but do you have any thoughts about updating the MOD to the new way? There is some new file 'example.sdef' in 'Doc\Sounds' that implies it would be possible to still develop sound MODs. Thanks again! EDIT: Might be easier than expected, according to THIS

If you like, you can try another small MOD by me, slightly less disorienting... https://forums.eagle.ru/showthread.php?t=207776 And by the way, the MOD mentioned by Chic in post #2 has been updated with a 2.5.6 version if needed.

I took the liberty to update them to 2.5.6 Beta from yesterday. They are also a bit tidied up, your original ones contained some files not affected/related to these MODs. Still OvGME ready. UH-1H Crew Status - Dash.zip UH-1H Crew Status - Pedestal.zip UH-1H Crew Status - Window.zip

So, ones again I take the same liberty to post an updated version of this. Now for the 2.5.6 Beta released yesterday. It has version number 1.5. Last time I posted v1.3. I forgot to post the 1.4, and I don't have it anymore. If you are still on stable (pre .6) v1.3 might need some small fixes by comparing the files to the original ones. But overall, this MOD doesn't add much any more, except some small fixes and 4 extra axis assignments for the joystick. Might still be worth it. AJS-37 _My Buttons Viggen v1.5.zip

UPDATE FOR 2.5.6 BETA PROVIDED!!! The version for 2.5 pre .6 is still provided until DCS stable goes 2.5.6 (sorry, posted a faulty 2.5.6 version, corrected now)

UPDATE FOR 2.5.6 BETA PROVIDED!!! The version for 2.5 pre .6 is still provided until DCS stable goes 2.5.6 (sorry, posted a faulty 2.5.6 version, corrected now)

@Mustang What changes compared to original file did you do to the 'terrain.cfg.lua'?? Changes have been made in the 2.5.6 version, so I try to adopt v1.30_2.5.x_06_05_2019 to it, but I am a bit unsure what exact values you changed. Those I am unsure of are: noise1PerSquare noise2PerSquare grassHeightJitter grassShadowIntensity And/or something else? Thanks!

As night and day! And yes, the MOD I made should not mess with your key assignments. I haven't tried 2.5.6 yet so I don't know if it will introduce issues with it, but I doubt it will. Otherwise I will correct it an publish a new 2.5.6 compatible version as soon as possible. Lycka till med slingträningen!

So typical! Just because I mentioned it, I saw now I DID get a notification for today's Beta update! But not for the Weekend News thread.

Hi, Sorry if this is posted in the wrong place, but it's related to the forum and not DCS and I didn't find a better place to put it. My issue is that I no longer get any notifications in Tapatalk when new posts are added to the DCS 2.5 Beta update/changelog thread nor the Weekend News tread. I have the threads checked for update notifications in Tapatalk. All other threads I follow do generate notifications (at least what I know of, might have issues with threads I don't remember following). I previously got notifications for them, but don't know when it stopped other than sometime during second half of 2019. Is this an issue with the forum or Tapatalk? Is it something that can be corrected by some moderator here? Thanks! /H

I believe they already have. Just look at the Las Vegas and Dubai ma... sorry, Nevada and Persian Gulf maps. Where have they seemingly put most resources during development? On what locations are the marketing of those maps fokused on? When it comes to PG, is it really the area (and timeframe) where most action in the region have taken place? not a bit more to the NW may be? Added to that, both cities are well-known for extraordinary and creative ways of promoting themselves. With that (conspiracy-ish) said, Taiwan map would be very welcome indeed.

Just a thought, try ["Mi-8MT"] = 6 instead (without "V2"). I have no idea if it will work in this case, but when dealing with other lua files concerning the Mi-8 one shall often use "Mi-8MT", like when correcting head movements/location in the server.lua and such. Worth a shot.

Did you see post #93? What are your RPM:s? Surprisingly often people accidentally have their throttle (the one on the collective, not called throttle on the Mi-8) turned to idle speed, making the chopper very difficult to fly properly. And remove all curves! And centering springs! Neither belong to helicopters!

The shortcuts in red are a rest from when they tried to have the checklist read by your co-pilot, i.e. voice-over. It was only avaliable in Russian, and eventually scraped all together. The "missing" APU start you referring to is simply to push the start button I think. The checklists are simply just that, a list to check so you don't forget steps before and after the actual push on the button.

I just tested it. Indeed it works with the option for second joystick disabled. When not in AH, you fly with your cyclic and the second joystick slewing the camera. With AH enabled, both sticks control the camera, but with priority on the cyclic, i.e. if one axis on the cyclic isn't perfectly centered, the camera will slew according to it, ignoring the same axis on the second stick (if the other axis is perfectly centered on the cyclic, the cammera will follow number two on that axis). This is a bit different from how I remembered it. I remembered it being that you could move the cammera with both sticks simultaneously, the sum of the two inputs being the controlling signal. Anyway, if you have a second joystick or analog thumb hat like you, it's better to have the option in the special settings enabled. The cyclic need to be perfectly centered in both axis while in AH for it to work flawlessly otherwise, not always easy even for sticks with centering springs/detent. Deadzones on the cyclic are really not desirable and not an option for helicopter flights.

Did you see my comment above and did you test it?

Have you tried it while in autohover? and have you while in AH tried to move your cyclic and observing what happens on the screen? Can't test it myself for a while, but I believe I did a while back when adding a spare joystick to my setup, not thinking about the dual joystick option in settings. My memory tells me that I could indeed operate the camera with the second joystick at all times, but when in AH I got some strange behavior. Turned out to be that while in AH both sticks had authority over the camera. Finding and enabling that setting in options solved the issue.