kobeshow

Just so there is no misunderstanding, the VTB screen is suosed to be black, if you have a TAS indication in the top right corner everything is fine (like in your screenshot, TAS is showing). If the TAS indication is blinking your radar is not emitting, but you already get ranging info so I suppose it is working.

Once you have picked a side on the server by typting red/blue in "all chat", only the admins can change your coalition, and you would need to request that either here or in the existing thread on buddyspike.net

I thought they had fixed that in the last 2.0 patch, apparently not, it is the same as 1.5 and is known to be an error, so we need to continue waiting for a fix.

There are several issues with synchronisation of animations, but that is a DCS problem, slats/flaps/brakes/lights can all show for you but not for others and vice versa

Yes you may have missed that they fixed the need to display the messages, and the messages were removed at one point in round 9, but came back for some reason.

I don't think kill messages for air kills would be better, remove them all! Remove everything from the chat window that gives any form of intel, I can't be the only one that feels that way.

It has been a while, I'll check and see if it works with engine running, but as I recall it did not. EDIT:Well, I tested it with ground crew and enignes running give enough power to the radio.

the thing I have noticed is: radio does NOT work if the battery is not on, even if you are on groundpower.

From your description it sounds like your radar is not emitting.

Having an offset waypoint to the IP is also good for tactical reasons, if the bombers always fly from the IP to the target and then back to the IP and back to the target it is easier for CAP to cover them as they know exactly which corridor they will use for the bombing runs, staying in that corridor can also serve as protection from known SAM sites.

I can't tell you anything about 2.0 really, as I have decided that 2 installations on which different things are implemented/broken at different times are not worth the headache. I have also asked some questions regarding 2.0 on the ECM thread but no responses from the people who have tested the latest patch.

The latest 2.0 patch included further improvements to the TAS and the gun pipper, sadly ED did not release a patch for 1.5 so we will have to wait for that, maybe friday?

I don't really know what the registration process is good for, just join the server, type red/blue in "all" chat and you are good to go.

hmmm, you have an approximated range for that ? we might be able to use it as a nuke afterall :D

I have "created" this kneeboard page from the finalised charts that Zeus has posted, simply copy it into this folder C:Users\(name)\Saved Games\DCS\Kneeboard\M-2000C Since there was no answer about my previous question, and the changes have made it to 2.0 already, can someone tell me if the countermeasure programs are editable in some .lua file and if that will pass the integrity check, would be much appreciated.

Yes I agree, it's an absolute shame.

Hey Noisy_lightning, sadly the mouse thumb is not really an axis ): your only option to use it as TDC is to select bands, and then bind the corresponding keyboard commands to those bands, leave the 34%-65% range of the band empty, and bind 0%-33% and 66-100% to up/down/left/right. I did a quick test with it and it does not go very smoothly, that mouse thumb stick is just awful since it is really just a 4 way switch.

I think the problem here is not that the light is "popping" (turning on off), but rather that the light cone is too short, the same thing happens with the police light.

hah my bad, I thought when you first said "those are navigation lights" you were refering to the post above which said "no electroluminescent formation strips" nvm. pretend I didn't posts that^^

Yeah unfortunately you have to do it with keyboard macros. At first I thought it would be hard for me to do it for the Mirage because of the lack of default bindings, but I now realised that it gives me much more freedom and makes the process quicker than expected, so that was one of the surprises for my first full fidelity module (great work by the way!). The configuration of the macros is straight forward and more or less self explanatory. One thing I would advise though is to set an advanced command even for single button presses, and always remember to "quantize time" so it happens instantly. I don't want to give obsolete tips here, so instead of typing more words I'll just attach my M2000-C profile for you and anyone else to have a look and get some pointers. It is in no way set to correspond roughly to the real Mirage controls like yours, it might be a bit weird even, and is very much wip just as the module itsself. DCS M2000C.zip

Hi Zeus, nice settings (; I also have a X55 which is broken already (some loose contacts, your "2" button on the throttle doesn't work for me anymore), but I use the software for programing my keybindings and am very happy with it, I used it as a replacement for countermeasure programs for example, if you really want some:helpsmilie:with it I would be glad to help you. I am not sure if DCS recognises the stick's different modes, makes a lot of buttons go to waste that way (;

*formation lights

Is it possible to set your own release programs in a .lua somewhere, and if so: will it pass the integrity check? I know we could get this function in-game but I would already like to change some things since I am used to using my own release programs (via Joystick makro)

Hey Greg, you have an error on the web based map, the COMM Array in PAK 2 has wrong coordinates in the tooltip, the short version is GK40 but the detailed one is KQ 686 071, so something is wrong there (; cheers

Ok a little bit of feedback here, I personally don't care what "feel" the naming of a button conveys, but I think it would be helpful to find some consistency, in the first image, it is called the EMERG button, but then you call it a PANIC release, make the button description match the hotkey description in the control options and all should be good. Users currently have to collect their information on the plane's functionality on the forums mostly, which is fine for a beta module I guess, but having little bits of info laying around in different threads just causes confusion, not to mention that there are functionalities posted that don't work as described due to bugs, and one has to do a good amount of searching to get a good picture of what state the plane currently is in. Consistency with labeling and naming is very helpful in this case and am sure would be greatly appreciated by people who just got the module and now are browsing the forums for info. Anyway, great module I enjoy it very much, keep it up RAZBAM you are doing a fine job !:thumbsup: