exnihilodub

I really wouldn't reccomend it since any automatic change in one of those components will break functionality, and when you press that key you are going to have for example "brakes on, flaps up" or vice versa. I don't know if DCS reads thru raw hardware or through software, and I also don't know at which level this software creates these combinations but it's worth a try: https://autohotkey.com/ I'm glad if i could be of any help.

Hi. I think it would be a nice addition if killing the power boxes or the lines between boxes actually had an effect (blacking out an entire town or block).

:doh: thanks man. Should've done my reading more. :doh:

yeah it states that in the manual but correct me if i'm wrong: It uses barometric altitude to check for the launch permission right? and as far as I know, barometric altitudes report ASL, not AGL.

I think you missed my question. What if the target is on top of a hill which is let's say 2000m. above sea level? As far as I know, BK90 can't be launched above 500m. above ground level. (which means 500m. above sea level since launch inhibition checks barometric altimeter) So to put it easily, let's have a hypothetical scenario like this. We have a flat hill, which is 2000m above sea level. Both me and the target is on that hill. I'm flying 50 m. above target, which the altimeter shows as "2050m above sea level" and inhibits bk90 launch. I hope this makes it clear :(

Hi. I was wondering what should I do to be able to hit ground targets on elevated positions (hills etc.) especially if you're over the release altitude limit of bk90's - e.g you're engaging a group of tanks on top of a hill which is 2000m above AGL-. Is there a way to input the altitude of waypoints? Or should I somehow fool the system by changing my barometric altimeter(if so, is there a conversation table of converting altitude to QFE)? thank you for your answers and I wish you a great evening

Hi.I've read in the manual that you can add RUTA type waypoints and have like a recon box on your radar. I've tried doing it but I've failed and I don't know where I did wrong since it's a long procedure.( I was able to set up R waypoints though, by entering them into CK) my problem was i couldn't get them on my CI. So I'm hereby humbly requesting a quick run-down on how that system works and what are the steps required :) I would really appreciate the help and wish you all a great night

Hi. I was wondering how do you switch between a2a missiles if you have both 24j and 74 loaded? If it's the IR fast select button on the left side, how do you know which missile you have selected right then? If I'm not supposed to carry two types of missiles, why does the viggen have CAP (6 AAM) as a preset loadout? thanks for your time answering my questions and I wish you all a great night

Hi. I can't seem to set ToT for "B" type waypoints. I have 3 waypoints total, first 2 is for visual fixing and the 3rd one for target area. Whenever I try to set the first waypoint's ToT to 12:08:00 ( or anything else ) it saves it as 12:10:00. Here's a list of what I've been doing: *Create a mission with 3 waypoints, only speed set, no ToT preset before mission start. 12:00:00 as beginning time. *Start the aircraft, insert data cartridge and load it by inputting 9099 on TAKT & press LSSKU. *Switch to TID, Output mode, see B1 has 051000 as time of arrival(which means no ToA set i assume?). *switch to TID, Input Mode, enter 120800 and press the waypoint button to the right (B1 in this case) *switch to TID output and see the set time on arrival for B1 is 12:10:00 now. EDIT: just realized i can only input time in intervals of 10 minutes. like 120000 / 121000 / 122000 .. any clues? EDIT: Even though I set a ToT like this, the ToT output mode will display 700000 as if i hadn't set anything at all. Any help is greatly appreciated, I wish you all a great afternoon

thanks ragnar. should I expect it in my current playable version or should I wait for the next update for the fix to take effect?

even though I move the crosshair dead-on top of the target, the circle moves to a position where it's a bit off target.

Hi. Copying this from a comment I've made in youtube. Be advised that I've been trying those with air starts: I have a question for you. even though I set my fixes correctly (2 visual overflight fixes before target radar fix), the bk90's hit ahead of target. anything i might be overlooking? Also, does one have to input the target elevation above sea level to the CK or the radar takes care of it? Also another addition is: The bk90's are accurate when I do an airstart and use the waypoint without radarfixing it. If I try to do a radar fix on the target, they fall ahead of targets. So another question that stems is: Do I reference the circle's center when I TV Fix on a target? or do I reference the center of the crosshair? TLDR so far; -placed waypoints are accurate but manual radar fix on targets aren't. -how does one input target elevation above sea level? I'd greatly appreciate if you could answer my questions and I thank you for your time.

oh that's a bummer :/ but thanks for the answer and clarification! Any place i can read about this mixed loadout incompatibility of AJS37? also another question is, why did the engineers felt the need to include a weapon selector that extensive if the Viggen can only carry 1 type of A/G missile?

Hi. When I load myself with only RB-75's, I can use them as I'm supposed to. But if I have RB-04's and RB-75's loaded, I can't select the RB-75. Here's what I've been doing: mastermode: NAV MODE wpnselector: RB-75 triggersafety: non-safe I've also tried pressing IR-RB FRAMSTEGN button on the left vertical console, but that doesn't seem to help either. Any help is greatly appreciated and I wish you all a great evening

hey renhanxue, thanks for the detailed post. I've solved my problem. I was using the "three-button switch" option on my joystick, so it was held when i pressed it. Fixed it by remapping my controls. you're awesome!

Hi. In manual page 132, it is stated as such: "The system will automatically select the next waypoint when the active waypoint is overflown or passed within a distance of 3 km.). During modes ANF (attack) and SPA (Reconnaissance) or NAV with the trigger safety off (mode unsafe), this automatic switch is locked. Automatic switching does not apply for BX or landing waypoints." I've tried flying over a waypoint on NAV mode with trigger safety on, off (in NAV mode) but the DI shows the waypoint as E1, and it doesn't switch to the second waypoint after overpass. Any help is greatly appreciated and I apologize if this is a noobish question or I missed a very obvious thing. Have a nice day

Hi guys, thank you and congratulations for this awesome aircraft! I've been reading through the manual to learn how the systems work in this beauty. In page 196 it says: The waypoint is checked by pressing a waypoint button. If the data indicator indicates 900000, the waypoint is defined as a target waypoint. setting the waypoint type by using TAKT IN works but TAKT OUT fails to report waypoint types (only returns 000000) I know this is a bit of a nitpicking but just wanted to help by a small amount by pointing out something i've found:) thank you again for this module and I appreciate your hard work & time on this project. Have a nice day!

Hi. What's the purpose of pitch damper cutoff switch on the stick? Is it just an easier way of switching the pitch damper to off position without looking at the left console, or does it have another usage? If it affects flight dynamics in another way, should I keep it pressed down while maneuvering? Thank you all for your replies.

the only thing I know of those aircraft is that they retained their paintjobs after the movie was done. also here's a USN VFC aggressor squadron f-5 photo. I know it's not the same with the ones in the movie, but it's same as the one in your signature: http://themindfulbit.com/blog/mig-28

check this one out watermanpc

the GBU is implemented, the manual part is still WIP so no instrucions & release tables

Hi. This is just a humble opinion and a feature request :) As you know, we can see the cockpit glass shattering under damage, but only in external views. How about adding it to the internal camera too for every aircraft? Also, instead of immediately and abruptly switching to external camera upon pilot death, how about losing the control in internal camera and watching it smash to ground (maybe with a post-processing effect that's signifying death like vignette+b&w)? I'm already content with the current status of these situations, just wanted to present you guys a humble opinion :thumbup:

wow that's great! also noticed though, even if after fire, I release second detent but continue holding on first detent (to have the gas exhaust open and continue recording), the recording will stop after the overrun time. is that intended feature? by the way, thank you cofcorpse for helping me with the recent flood of questions. You've been very helpful. I'm forever in your debt :)

Hi. I see a feature called "sight camera" in the documentation and also in main menu options under F-5. Is it ever going to be implemented?

Hi. Just wanted to point out; after depleting the chaffs and flares, the counter that displays remaining flare/chaff on countermeasures console doesn't stop at 00. goes to 99 and starts descending again.