firmek

There is a thread with some informatino related to that: https://forums.eagle.ru/showthread.php?t=177993

I wasn't initially interested at all as I have the warthog. Then again, I have a good group of family/friends which we're playing some other online titles from many years on regular basis. My idea was to give it to one of them that I know is into sims but is held back by the need to invest in hardware. This might be a way for me to trigger a chance for organizing a small sim squadron.

I actually find it that TACAN helps a lot. Set the HSI into TACAN mode, follow the course as instructed by ATC, watch altitude and turn towards the runway when the HSI arrow is aligned with the runway heading. To some extend I was relying more on the instruments than on the HUD. Maybe it's just me but the vertical ILS indicator - dashed line on HUD is confusing me more than actually helping. Might be it’s too sensitive, don’t know but I find its movement too erratic.

It's not ready since it's not ready yet. Drawing conclusions based on a few screenshots and a youtube video is a bit too much. Don't you think? The only thing we can achieve is speculations.

M-2000C is out for quite a while and had undergo a lot of changes during last time. With the training missions released I thought it's probably good time to consolidate knowledge about the plane. At start I have to say that I like the training missions quite a lot. Also the French accent voice is a nice touch. I've run into few issues though. Startup The startup sequence doesn't seem like the standard one included in the manual. It might be interesting for someone knowing the module from some time as it gives an opportunity to try out something different but I guess for someone new as it's different from manual it can be confusing. I wouldn't be surprised if some new folks ask on forums if connecting a ground power is mandatory or not. Takeoff Probably just a formality but it would be good to have a takeoff training mission before actually going into navigation - just to follow the convention of training missions for other modules. INS and navigation 1.) Either I'm doing something wrong or the HSI thin needle doesn't seem to work in Cv NAV and Cm NAV modes. It supposed to be pointing towards the VOR/ILS station - which I guess (as it's not clearly stated in the manual) is set according to the ILS frequency. It changes it's position after setting the ILS frequency but after that it just stays fixed all the time. 2.) INS drift and update Drift seems to be always more or less to the same direction west/south. I'm not sure how it should be in reality but I could imagine that it's more random. This isn't probably a big issue though. The bigger one is that actually the update doesn't seem to work as an INS update but like an implementation of drift reset. During the update the position should be updated to the one that is being overflown or pointed by the radar. It looks however that this position it is actually ignored. Intentionally I've tried to fly an update the INS in some other place. It was more or less 1nm mile away from correct landmark position which should suffice the <15nm requirement. Anyway the position was not set to the one that the plane overflew, just the drift was reset. 3.) RD/TD There is separate thread related to it according to which RD seems to work, though I didn't manage to get it working during the training mission. Probably I need to try once more. TD is not working. Apart of that manual pretty much doesn't describe those functions. 4.) Entering the landing point values in PCN Basically CP/PD, ALT and L/G. I've used Kobuleti. L/G is easy, same for ALT (just used the values from APT data on F10 map). CP - I've used 70deg, PD 3deg. I'm not so sure about the glide slope value. Anyway with correct ILS freq dialed in, APP mode selected and settings as above the synthetic runway didn't show up. Those aren't issues with the training missions itself. On the other hand I'm thinking if they haven't been released too soon. Maybe it's better to hold on flying them till the modules is more feature complete as also the manual is updated.

Probably as the MiG-15 is a fighter I wouldn't expect that removing the sight gets high priority on the todo list - if such lists actually still exists. I could understand though where the request is comming from - the sight in 15 is obscuring the vision quite a lot. As for the MiG-21 - there is no way to remove the sight assembly from it in DCS. What Shab249 is talking about is something different. Without the sight the cokpit of 21 would look more or less like that http://www.gawronsky.com/panorama-3-MiG-21MF.html (more or less isnce it's MF not bis).

... 2 pages back of this thread there is a good info on the status

Standard view preset - RCtr+RShift + Num1 (or Num4) should work.

After a year of using it. Stick: no bigger issues with it. It's really sturdy. The minor problem is that after a while the movement becomes sticky. I guess something that can be easily addressed with disassembling it and properly greasing. But then again, why is it needed? Especially that doing it will void the warranty. Throttle: great out of the box but really soon - within one month of use, the throttle handles started to develop some looseness. What makes it even worse is that I've treated it in a really delicate way as also the torque was set to minimum. With time the looseness becomes so big that it makes difficult to be precise with controlling the throttle. Might be not a total disaster for a fixed wing plane but for helicopter it's pretty much a no go. Overall I'm rather disappointed with the build quality. Second issue: The "pinky" 3-way switch has noticeable worse quality then the others. After some time it started to stop connecting from time to time. Third issue: 2 way switches have actually a single position seen by the software (3 way have 2 positions). Not a big problem though but makes mapping the keys a bit more difficult - special commands have to be created in DCS. Overall: it's probably difficult to get something better for the same price but at the same time for the price I would expect better quality. The first impression is extremely positive but with time I'm rather disappointed.

The only one significant issue that I've run into with this application is that using Dynamic Caucasus Beacons generates some empty kneeboard pages.

Thanks for the into Bignewy. Is there maybe a temporary fix - like using some files from previous 1.5 build or 2.0.x?

After the recent update the mouse and keyboard sometimes are going crazy: 1. Mouse doesn't stay where it was left. After leaving mouse for a while, when the yellow cross cursor gets hidden the mouse is always re-positioned to a fixed place. More or less close to top left corner of the screen. It seems like a small thing but after a while it becomes extremely frustrating. 2. From time to time the mouse in outside F2 view is not working at all. The problem seems to be connected with switching the comm/radio menu on/off. 3. From time to time the keyboard also gets locked. Pressing any keys do nothing or result in some strange action - for instance F1 makes the whole cockpit disappear. Hitting F1 once again brings it back. I'm not sure if it is related to VR changes. Can there be an clear and easy setting like "no VR" that would disable any VR specific features - for those that want to use the mouse and keyboard in a normal way. It's not fully clear if the options like "use mouse" or "cursor confined to game window" are affecting normal users.

IC is green for me. Also with the dynamic mission briefing and after modifying the "kneeboard settings" (position).

On second thought - I have to admit that the Kneeboard builder is great. I've just got it installed. Most of the things that it does could be done manually but the application really saves time and provides an easy to use, single panel to manage all of the kneebords. I would not run any app as Administrator as it really should not be required. Check if you have MS .Net 4.5 installed as the application requires it.

Just use any of the free online pdf to png conventers. PNG is better as JPEG is less suitable for text. Next copy selected images to the "C:\Users\@YourUserName\Saved Games\DCS.openbeta\Kneeboard\@ModuleName" for 1.5.x or "DCS.openalhpa" for 2.0.

Much appreciated :thumbup:. Just take the necessary time to polish the module and keep everyone updated. It's always better and fair and communicate that some more fine tuning is required than keeping people in the dark which always creates unnecessary noise. Especially that it looks that Viggen managed to turn on a lot of people which may not have been so much into it from the very beggining :) Good luck tomorrow splashing 21s :thumbup:

My bet would be 2.0x being aligned with latest changes from 1.5.x. Then 1.5.x release with Spit next week, maybe also with Viggen. Lets see. Either way DCS is bringing some great stuff for Christmas :thumbup:

C'mon, lets stay pragmatic. Snow +15 deg could happen but it's not exactly the most common situation. As for the flight plan leading through a no fly zone I remember it also struck me when flying the campaign. Those are not a big issues, just a small "oddities". Something probably easy to fix. None is bashing on a campaign because of them but let's not try to twist the things around and say that users are lacking imagination. If my memory serves me right this might be the case. I flew the campaign some long time ago and can't remember any snow there. Actuallym, another reason that I remembered it that way was that some of the story line mentioned winter while the environment was using spring (or autumn) textures all the time.

Just try to learn about development cycle for any bigger software project. As a really quick rule of thumb, ask anyone without any inexperience about the his take on the effort - the real one will be at least 10 times as that. Ask a developer - he'll give you some number - ask PM what he thinks about it - he'll multiply that number by 2 or 3. And just to relax a bit: what's the standard number that every developer will give when being asked how much of his task he has completed - most of the cases the answer will be 90% ;)

There are threads that discuss differences between those two. I've got a Mi-8 first, spent a lot of time flying it, then got the Huey and after few hours with it I came back to Mi-8. Since than Huey sits for some other time in hangar. IMO it depends mostly on personal preferences, nostalgia, ethetics, etc.. Technically both are great modules.

Fully agree, editing the commands files is pretty much a must to be able to map the keys for warthog. In reality I think I had to add those commands for every single module that I fly, including M2000C which probably did the best work out there (obviously when not counting A10-C). The biggest annoyance comes from the fact that from time to time there are updates made in the original file so it's necessary to compare the files and merge own bindings eventually - instead of just copy/paste the file. The other problem is that it's not always possible to make a 2/3-way button command if approporiate actions are not defined (i.e. the off/taxi/landing lights in MiG-21 has only a toggle command). Would love to see the devs adding such bindings by default – it’s not a rocket science after all -> up on else off for 2 way switch and 2 commands for 3 way one.

Thank you for this post! It's really just not fair to complain about someone doing a great job and others enjoying it just because it's not someone’s pair of shoes.

Or maybe the manual needs to be fixed ;) This small action would require not only the other person being able to join the same cockpit but also a proper radio communication via intercom.

It's a point that was always interesting for me. I'm always keeping the pitch/roll channel on, altitude and heading off and then trimming a lot. The question is what the best practice is (if there is any) and how it looks in reality. The reason why I gave up on using the heading autopilot is that the computer pedals always come back to center instead of staying in place as those in the real Mi8. In result the centering action when the pedals are eased and then moving the pedals into a trimmed position makes the helicopter wiggle side to side. Besides of that, not to be totally off topic - Mi-8 is a great module. Totally recommended! I have never though that a transport helicopter can be so much interesting and engaging.

Hate to play the devil’s advocate but the module has just got released. As such probably we shouldn't expect more than bug fixing and not much, if any of new features being added. At some point of time the devs really have to call it a day and move on with new projects. Otherwise they'll just stuck in constant development and maintenance cycle.