JLX

I know this is an old thread, but I'm having the same issue now and cannot use snap views in the Viggen. User Snap View saving is ON in my settings. Disable TrackIR Rotate/Translate/Zoom to get desired view. LWin+Num# to select snap view I'm going to replace. Finally, RAlt+Num0 to save. The saved views do work for the duration of the current mission. However, when starting a new mission, they are not preserved and revert to the defaults. After checking the user SnapViews.lua file, I see that the views ARE being saved. So, I suspect that the error might be just that when starting new missions, this file is not being referenced/loaded with the previously saved user views. Would be grateful if there was a quick fix to this as I use snap views extensively. Thanks!

I understand the problem with not seeing the basket. If you don't look at it, how are you supposed to know how to correct your approach? What I did was bind a joystick button to "rear arcade view" (Shift-F4 IIRC) and another to jump back to cockpit (F1) view. Then, keep looking at the plane, once again NOT at the basket. However, when you miss, quickly switch to the outside rear view to see HOW you missed. Too low? Too far? Then quickly flip back to your cockpit view to see what that position looks like from the seat. This way you have an idea of what to correct for your next run. It sounds to me like you are trying to set the throttle at a single "correct" position to hold speed with the tanker. This doesn't work in my experience. You must CONSTANTLY adjust. If you've flown helos it's like maintaining a hover - the stick never stops moving. In this case neither does the throttle. You DO "chase the speed rabbit"! Just try to to anticipate a bit as you're making very small corrections and don't stop. 10 times is nothing. Perhaps adjust your expectations? It definitely requires patience and persistence. On the upside it makes it even more satisfying once you do nail it. Once again, good luck! Sent from my MediaPad using Tapatalk

It's hard but doable. Just takes a lot of practice/patience! I use AFC to set my initial trim as I get into formation. Once that's done I ignore it and everything is manual from that point forward. I don't use curves in my profile but you may find that helps. For my default view, I line the center of the HUD with the left edge of the propeller, and the top of the HUD glass with the bottom of the propeller. Creep up very slow and keep fumbling around like a teenage boy until you stick the landing. Look at the propeller (or whatever you choose as a reference), NOT the basket. I never turn my head to look at the probe as the change in perspective totally throws me off. Once you do it a few times, just get used to how the probe position looks as it passes out of your peropheral view on a good connect. I started to be able to judge a good approach from this even before connecting. As to maintaining speed, I have an old CH throttle and have to constantly rock it slightly fwd/back to hold constant speed/ formation. I consider this normal. If I'm coming in too fast, a very quick shot of air brakes does the trick. There is no magic here. It just takes a lot of trial and error. But it's very satisfying once you can pull it off! Good luck! Sent from my MediaPad using Tapatalk

Just wanted to add a +1. But, I wouldn't stop at a Bambi bucket (although this would be awesome!). I'd love to see improved sling loads in general. Perhaps add options for: Bambi bucket for fires Medical stretcher for SAR Hanging rope for hover & rappel deployment/extraction Hanging sonar/mic for ASW (I know, this isn't a thing yet but you get the idea) etc. Accompanying object models (even if just statics) for the back would also be a great way to provide status info rather than having to query CTLD/CSAR via F10 for example: Show medic by stretcher(s) so you can see how may wounded are on board (max 4?) Show soldiers seated in back to see how many seats are left available. Have perhaps 3 static cargo loads for "light" "medium" "heavy" so you can roughly tell how much weight is on board. etc... I realize this would take a pile of work. But if you're going to go as far as to make a Bambi bucket, then it's worth making the most of the effort rather than just a single function. Anyway, great suggestion!

Very interesting. Tnx for the post. Sent from my SM-G930W8 using Tapatalk

I can't test now but one thing that may help with the failed startups is to make sure the throttle is at the idle position before starting the engine. I also recall occasions where even this abbreviated early-access startup did not proceed as expected. IIRC, in my case I'd left the throttle open. With it in the closed/idle position the startup worked as expected. Now I just skip the startup altogether and figure I'll wait until it's implemented fully before committing it to memory. Take with necessary grains of salt as this is from an admittedly vague memory and at least a couple updates ago but perhaps something to try.

Training scar? Interesting term. Never heard it before. I don't reverse the collective direction so that particular issue didn't get me. But I did have to remember to not touch the pedals as you come out of transitional lift. On an unrelated note, I haven't noticed much ground effect when hovering the Harrier. Has it been modelled yet? I expected a bump as I slide right on to the deck of the Tarawa if I don't have much clearance. Sent from my MediaPad using Tapatalk

^this. Pay attention to visual landmarks. It may sound obvious but it's easy to get your head wrapped up in the cockpit and forget to simply pay attention as you look around. Look for big prominent landmarks that area easy to find and then remember relative positions from them. For example, the target may not be easy to see but if you notice it's near the tip of a large "pointy shaped" forest or roughly between two large lakes that are easy to spot, you can reorient yourself from there. Also, if you are comfortable with the instruments, don't forget about markpoints. They're quick/easy to create spatial bookmarks and useful for much more than marking targets. Drop a few of those like breadcrumbs to help you find your way. Hope that helps.

I use the light springs but also like some center definition. Found the 10cam too vague at center. Am using 30s but wish there were 20 as that's the feel I'd really like. Was going to order some but learned they don't make 20 cams which is a shame. Sent from my SM-G930W8 using Tapatalk

I like fairly short ferry times. Below 5-10 minutes before some sort of navigation or tasking starts. In general I prefer utility over combat as the Huey is just do damn fragile. So, SAR, transport, recon & sling loading (when fixed) are all good. I definitely want a challenge - something interesting to do as I'm flying. Could be dealing with bad weather, trying to locate a nav point, setup/use radio homing, night missions with NVG and/or searchlights... that sort of thing. A bit of sight-seeing as you go is fine, but in general I want to be busy and stay engaged. Also, missions that you can fly with a buddy are always appreciated. I tend to gear mine for 2-4 players.

I don't even own the Viggen but this is some of the best organized and presented kneeboard information I've ever seen. Well done!

I'd like to see a new USER-SELECTED type of plane option added to the mission editor. The differences from the existing plane unit would be: SKILL is always set to CLIENT (no AI) PAYLOAD is always EMPTY (as the plane type is unknown at design time) PAYLOAD tab is replaced with a PLANE TYPE tab which has a checkbox for each flyable module. The mission designer can then choose which planes are appropriate for that slot. WAYPOINTS would have to allow any speed as a top speed would not be known at design time. Any other plane specific options would have to assume default values at run time. At mission start the player would select his/her plane from those made available by the mission designer, then rearm manually once they spawn in. Generally it's not a specific plane that is required but rather a role that needs to be filled. It doesn't really matter if it's a Hornet, Harrier or Hog as long as it has the capability to get the job done. Having to include all possible planes for all possible players gets unwieldy very quickly requiring dozens of slots! (e.g. 10 plane types x 6 players = 60 required slots) Being able to design a mission for 4 people and actually use only 4 player slots makes infinitely more sense and would ease scripting as well. It would make it so much easier for mission designers to support as many modules as possible and thus easier for players to find missions which they can use. Finding a mission suitable for me (AV-8B) and my friends (F-5, A-10C & AJS-37) is next to impossible. I'd have to find another mission that is hopefully close, then edit it (potentially spoiling it for myself in the process) for our particular cocktail of planes and hope it doesn't break. Variable slots would solve issues like this and make more missions accessible to more players while also making things easier for mission designers. I realize this is not a quick-fix kinda request. But, it doesn't seem too far off the beaten path and I'd argue benefits are worth the effort. As always, tnx for the ear :-)

I never noticed that! A-10C habits carrying over perhaps. I just assumed you needed to be on the STS page to change weapons via MPCD. Never thought to check for guns on other pages. For consistency, I'd still have thought you should also be able to do it via center pylon on the ACP. But you're right, at least on the MPCD pages you'd expect to be active during combat (other than the TGP) the gun option is there. That makes things much easier. Thanks for pointing that out.

From my testing, whatever the last selected weapon was in A2G mode gets reselected whenever you return to A2G mode. So, no. It's not 2 HOTAS actions if you want to switch to guns from another A2G weapon. Point being, that you still cannot make a bombing for example, spot an additional a target on approach and quickly switch to guns to get snapshot off with the aid of the aiming reticle before climbing out. This I would imagine is not an uncommon thing to want to do. You could quickly switch to rockets for example and get a quick shot of that way. But not the gun? As I mentioned before it just seems like a very odd design decision as the gun would seem to be the weapon of choice for that sort of thing. If anyone knows a pilot with Harrier experience they can ask - please do! I'd love to understand more about this.

Tnx for the reply, Zeus. Out of curiosity is this something you could ask one of the Harrier pilots and/or other subject matter experts? It just seems such a bizzare operation choice I'd like to understand the rational behind it better. Regardless, tnx for the info. Sent from my SM-G930W8 using Tapatalk

I also have the Hornet (which is amazing) but would echo this sentiment. It's currently my favourite too. In particular, learning VTOL is extremely fun and of course unique to this airframe. I'm a big rotor-head too and mastering vertical landings offers a similar satisfaction to the UH-1 and Mi-8. There are definitely bugs and incomplete systems as well as some needed tweaks to the flight model. However, it is quite usable now. The big concern is how long it will be until completion which was recently stated as the end of this year. Sent from my MediaPad using Tapatalk

After setting A2G mode, it seems at present the only way to select the gun (in air-to-gnd mode) is to: Select MENU on MPCD Select STORES on MPCD Select GUNS on the MPCD Not only is this cumbersome, but if you're already using that display for another purpose you must manually re-select the previous page AGAIN once you've armed guns! Very tedious... It seems it should be possible to do this with a single press of the center select station 4 button on the ACP. I'm aware that guns are always available when in A2G mode. But I'm talking about using them as the primary/selected weapon and having the associated HUD mode to assist aiming. If the Harrier IRL cannot do this, then of course it should not be in the sim. However, it just seems a little too odd there is Armament Control Panel for the express purpose of quick access to weapons, yet the gun pod (as important as it is) cannot be selected using it! Not only that, but it also makes the center weapon select button (4) completely useless as guns are the only weapon pod available for that station. Why else would you ever press that button? Maybe the Harrier II+ can carry bombs/etc. there? Dunno. Still, seems like quite an oversight to me. So, I'm asking if this is a yet to be implemented function or if it's already working as intended. Thanks!

MiG-23 & F-15E & Falklands Map & Harrier Variants & (IIRC) Mirage III??? Crikey! You guys are on fire! Congrats! Very happy to see RAZBAM investing so much effort into DCS! I was wondering about a CH-53 or CH-47 but even if a big 'copter isn't in the works, we clearly have a lot of great stuff coming down the pipe! :D

I am curious about this too. Sent from my MediaPad using Tapatalk

I didn't know about the indication in the unit list. Will have to check that. A simple prefix for all objects in a given mod in the unit name pull-down is would be extremely helpful. Sent from my SM-G930W8 using Tapatalk

Ah. I see where the confusion is... You cannot set different modifiers for each key in MenuNav. The modifiers that you select apply to all keys. So, if you have set BtnMod1=Joy4(Pinky) then you'll need to hold Pinky with ALL (Up/Dn/Toggle/Select) functions. The idea is that the modifier let's you select the "layer" that you want all the functions to operate on. I can see this being a common point of confusion and I'll try and remember to clarify it in the docs when I get around to updating next. *Edit: I see what you're trying to do and will add more flexible modifiers (different ones per function) to the wishlist for future consideration.

You specify different devices by prefixing the button with the device number. So, for example, if your joystick was device1 (default) and your throttle is device2, it might look something like this: [buttons] BtnToggle = 2Joy4 // This is button 4 on the second device (throttle) BtnItemUp = Joy3 // This is button 3 on the default (first) device. In this case we can omit the prefix ... Admittedly, it's sometime difficult to tell which device number Windows has assigned to which controller. You can tell Windows to use a particular controller as default (#1). As for which controller is #2, #3, etc. it takes a bit of trial and error. I have device detection on my list for a future version but just haven't gotten around to it yet ;-) The order of the modifiers isn't important. In your case, you'd just need one entry and leave the rest blank: BtnMod1 = Joy4 // or of course whatever your Pinkie button is There are multiple modifier entries because I (and perhaps others) use several modifier buttons in unison (called chording) to get more shift states. But if you don't need them, just leave them blank. Hope that helps guys!

Being able to save data/flags and read in following missions has been a wishlist item of mine for ages. If/when you get this working, is it something you'd be willing/able to share with the community? Sent from my SM-G930W8 using Tapatalk

This sounds fantastic! I'm going to d/l and check it out later today. Thanks for the effort and sharing! Sent from my SM-G930W8 using Tapatalk

My curiosity is definitely piqued and look forward to hearing what's coming down the pipe. But... I can't help but agree with this sentiment. I'm so eager for a finished/polished Harrier! DCS is a smorgasbord of tasty delights and I definitely want to indulge in as much as possible. However that doesn't remove the importance of chewing and swallowing before putting more food in my mouth. ;-) Sent from my MediaPad using Tapatalk