Maulkin

Yeah I have no idea what that means..

So they announce that the Mig-15bis is no longer in beta but the DCS World 1.5.3.51171 still shows that module as beta?

Just to point out that it not just that they don't illuminate but in fact the "lights" cast shadows: http://forums.eagle.ru/showthread.php?t=160273 I think the sprites act as objects.

Was it the left or the right Alt key?

Oh now I get it! I had not even considered that. Ok then yes I agree that would be a good feature. Does any other module support this feature of toggling exports?

I guess this is the part I don't understand...if you don't use a second monitor then what display are you toggling? What are you exporting to?

Rlaxoxo can you attach your mission so I might try it?

Does anyone have a mission file where they have definitively confirmed that this is working? I have downloaded a number of so-called working mission files but so far none have been reliable. I dont need anything fancy here. Just a JTAC, a tank for it to target and a Mirage lined up at the proper altitude and heading so I can see if I can get this working.

Just to add my input into this topic, I would prefer it remained on by default. I have been using the viewport feature for the VTB and the RWR for some time now and now this has all changed it. :( As it stands when you perform this kind of setup it commits that monitor to the display (it blacks it out) so I cannot see why I would have this as a toggle-able output when I have already made the commitment of turning it on by modifying the .lua files in order to turn it on in the first place. The fact that I now must also commit a keybind to this functionality only adds more complication than is really needed. Does this also mean there will be a keybind to enable the RWR export? I sincerly hope not. On a better note I am very thankful for the '+' that has been added to the RWR export. It really helps to evaluate where threats are coming from.

Again this is buddy lasing. I am desperately trying to get the JTAC to work. I have slightly modified the mission tflash has linked above (to save on time) and I am still unable to get it to work. See attached track file. http://forums.eagle.ru/attachment.php?attachmentid=135257&d=1456094066 As far as I can see the JTAC has turned on the laser and everything looks good, long before I even turn on the Master Arm switch. In fact the damn thing almost hits a tank just by the ballistics.

Could you take a quick look at my track and see what I am doing wrong? I just cannot figure it out. :( I am really trying to get this figured out with a JTAC since I dont have someone available for buddy lasing.

Ok maybe it is not just me then. I have been trying to do this for some time now and I cant seem to ever get it to work (see attached DCSalpha track file). If anyone who has ever been successful has time, could they please review the track and let me know if I did anything wrong? Thanks. :) GBU_fail_2.trk

Where do I put them? EDIT: Nm I figured it out :) : C:\DCS World OpenBeta\Mods\aircraft\MIG-21BIS\bin

You used to be able to download the individual DCS modules until recently (which you could have then burnt to a disk of some kind). Now the modules will only install via the internal module manager. This makes a lot of sense for DCS as they have version control and wont have to deal with chasing their own tails when people run into problems with mismatched versions and raise bogus bug reports.

I split the throttle because I don't need the left side for anything. I find with the left side in the shutdown position it is actually easier to access the switch and single button on there. The fact that it was also activating button-30 and shutting down the engine was not intentional so I have moved it to button-29 now. This way if I move the right hand throttle to the shutdown position I will get the desired result, but even with this modification I have seen the above mentioned error condition occur where my traverse would be stuck int the "cutoff" area of the M-2000 throttle and I would be unable to start the engine as a result. But that situation is harder to get into now that I am not accidentally activating it by using button-30 Sorry for the confusion and even as I have been trying to describe this I have felt it is very confusing. I have been tempted to make a video to help explain it and I still might need to if I was to raise this a a bug report.

OK I think I figured it out! Before I had said that buttong 29 and 30 (which represent the engine cutoff on the TM warthog Throttle controller) were not bound to anything but after testing it again I discovered that in fact button 30 (engine cutoff for left engine) was in fact bound to engine shutdown on the M-2000. So what does this mean? My initial condition was that my left and right throttle were unlocked (mechanically) from eachother and I had put the left throttle into the shutdown position just to keep it out of the way while I used the right throttle to control the M-2000 throttel. This means that the engine shutdown command was being sent to the M-2000 *all the time*. This is interpreted by the M-2000 to mean that the full traversal of the M-2000 is opened up. So if I throttled back to far it would traverse into the engine-shutdown region of the M-2000 throttle and cut the engines. I have since rebound engine shutdown from button 30 (left engine shutdown) to button 29 (right engine shutdown) and it is now working more predictably since I use the right throttle to control the M-2000 throttle, but there is one more thing: When you engage engine shutdown, as I said before, it will open up the full traversal of the M-2000 throttle, but only while the engine is in shutdown mode. Once the shutdown is complete it *should* close off the engine shutdown part of the M-2000 throttle traversal and you can restart the engine. But every once in a while I would get stuck in the small margin of throttle traversal on the M-2000 which composed of the engine cutoff. This means I could never start the engines again. I even tried binding the "engine startup" which is by default not bound to anything and sometimes it would boot me out of that engine cutoff region but most times it would do nothing at all. I think it came down to timing. So if this is the case we have a race condition and no one likes those..... My recommendation to Razbam is this: The M-2000 needs to operate similar to the way the A-10C throttles work.

I have only tested this using ver 1.5.2. I have also tested the axis out of the sim as well as within using the axis modifiers in the control panel and didn't see any issues. What I found also odd is that it seems to interact with buttons 29/30 even though they are not bound to anything because when I perform a cold start to advance the throttle after rpm's get to 11% I have to put the TM warthog into the idle position (button 29/30) and then take it out of the idle position. This occurs with with the throttle lock engaged or not. With the A-10C module this all behaves normally which tells me the TM Warthog is performing correctly.

I am using the TM Warthog controller (Z-axis) as my throttle control. Until recently I was using the locking mechanism of the TM Warthog to bind both left and right throttle together. With the throttles locked together if I throttle all the way back the M-2000 throttle would stop at the engine-idle point. Recently I unlocked them so I only would have to manipulate the right one. Now if I throttle back the engine will cross over the engine-idle point and into to the engine cut-off point. The reason for this is that at the zero position (all the way back) now translates to the M-2000 as the engine cut-off. For some reason this was not happening when I had them both locked together but this does not make sense as the left throttle is not bound to anything at all. In trying to work this out I even got myself into a situation where I could only move the Mirage throttle within the confines of the engine cut-off to the engine-idle point, and no farther. I would also like to mention that I do not have buttons 29 or 30 on the throttle bound to anything (which is what is used on the A-10C to shut off the engines). Not that the M-2000C appears to have anything like this but I thought it might be helpful.

I have also noted key binds coming undone after patches. I can only assume it is due to new or modified key binds or controls being introduced. I have taken to saving my joystick and throttle profiles which I then can load after each upgrade.

Thanks Tflash! This is exactly what I was hoping for. I can't wait to try this out!

Can some one give detailed steps how to set this up in a single player mission please? Sent from my SM-G925W8 using Tapatalk

Both the anti-collision lights and the nav lights cast shadows when they are turned on. This is very noticeable when you have the sun low in the sky. I would attach a screenshot but this is pretty easy to reproduce in the quick mission: free flight day.

I finally got this to work. There was a problem with the original mission file in that the JTAC frequency was not set in one of the presets for the R-828 (VHF-1). This can only be done in the mission editor. I set mine to preset #7. I have also added more fuel and some more weapons as the original mission gave me guns only. I have attached the modified mission to this post. To use the JTAC you perform the following actions: 1- set SPU-9 radio selector to VHF-1 2- using the R-828 (VHF-1) channel selector set the channel to preset 7. This has been configured by the ground crew (mission editor) to 40MHz. 3- press the R-828 tuner button. A yellow light will turn on. Keep pressing the button until the light goes out. At this point you can call the JTAC (firefly) and request a mission. A lat/long coordinates are given which might look like this: 42'41.417 and 41'40.065. Write this down 4- On the PVI-800 navigation pannel set the PVI master mode to edit. 5- press the NAV TGT button and then the number '1'. This will be creating a new nav target #1. 6- on the keypad there is a zero with a plus above it (henceforth referred to as '0+'). Press that once to be able to start editing the first line and input the first coordinate given. You will not be able to input the last two numbers so in the above example I entered 42414. 7- press '0+' to go to the next line (there is no indication you have succeeded in doing this) 8- press '0+' again to start the second line with a zero. For some reason the second coordinate must always start with a zero. 9- enter the second set of digits. As before you will only get the first 5 numbers so in my example I entered 41401 10- at this point the ENTER key will light up. Press that button to save the target point. 11- set the PVI master mode selector back to 'Oper' mode. At this point you should fly to the waypoint to the north. Once you get there go into hover mode and perform the following: 12- On the PVI press the NAV TGT button followed by '1'. The PVI display should show the coordinates you entered earlier and the ABRIS will have a box with a 1 in it blinking on the map display. If you cannot see it you might need to zoom out the map a bit. 13- Uncage the SHKVAL (default 'O' key) and the camera should immediately pan down to the target point and you should see the vehicles that the JTAC has you tasked against. It is not exact so you might have to pan around a little bit. KA50JTAC_Training.miz

I believe FC3 activations regenerate over time. Something like one per month. This is the case it all ED licenses I believe. Sent from my SM-G925W8 using Tapatalk

You do this all the time using a Mirage? I would really love to see a video that breaks down how to set up the mission using an AI JTAC and then using a Mirage to deploy the bombs (since this is a post about LGB's in a Mirage forum)