firmek

There is also an FPS drop related to the prop - specifically when looking on the sun through it. By the way the propeller model in Spitfire is just great. Even changing prop pitch is animated. On the other hand the FPS hit caused by looking on the sun through propeller is nowhere close to the drop of FPS related to the mirrors where on 1070 it's from 190 FPS to 70 when turning the mirror off/on.

Question - turning the battery on, was it a part of a startup procedure when the pilot was in cokpit or is it somethng that was done by ground crew as part of the pre-flight preparations - before the pilot even arrived to the plane? I guess this was done in order to avoid prop hitting ground during engine tests. Would be a nice option to have.

Chocks would be a good starting point. Either I've missed it or the options is not there yet.

The mirrors in Spitfire seem to have a much higher image settings than in other modules - thus the noticeable FPS hit. I guess ED will just lower the settings down to bring the performance back.

This is what I thought also - artificial horizon should align itself after a moment of steady flight but I guess it doesn't do a great job atm.

Yea, I was all like - I do a takeoff in Mustang with 0 ruder assist, Spit can't be so bad. Sure, the taxi and takeoff in Spit is more or less a panic mode for me atm. This beast is probably the most difficult module in DCS. What I think makes a big difference and why the taxi and takeoff in Spitfire is so changeling is that apart of free tail wheel that the spacing of front wheels is short.

Big thank you to ED and all people that made the Spitfire becoming a real thing in DCS :thumbup::thumbup::thumbup: For me personally and probably for many other people this is just a dream coming true. Technically the module is top notch, really the internal cockpit modelling as also external model are just great. This comes also with the sound which IMO is just exceptional. Really, the Spitfire shows how big progress was made through many years in DCS. It already looks great and it'll only get better with new graphics engine Another great positive is that even if it's an early access release, the plane is quite complete with manual and training missions (by the way love that English voice!).

IMO the in cockpit sounds in Spit are just on a different level compared to everything we've got so far. The sound was the fist thing that struck me after entering the pit and starting up the engines. Purely fantastic. I don't know how much it reassembles the real think but I'm sure that ED did a great job of recording the real audio. This is no just a belief but looking on how the BS there are much reasons to think that ED didn't do it in a different way. I just hope that we're not running into situation that the sounds will be changed based on some yt videos.

I've got to the same conclusion. During one flight I've got so much focused on chasing the dashed line that I’ve ended up flying a snake pattern straight into the see. At least it was a good lesson :) After that I've started to put priority on all other instruments, using TACAN/HSI, ADI alt and treating the dashed line with the lowest priority. Actually, when I come to think about it maybe it’s a good idea to try out the mission with HUD off.

I can also confirm, turning off the mirrors seems to solve the problem.

Just made the pre-purchase. Can't wait for tomorrow (or actually today). The bad news is that all my other modules will stay in hangars for a while. I really hope that its not going to be postponed as also that there will be some servers to practice on. Any news on the content that is going to be released with Spit - training missions, campaign. It's been rather quiet for some time. Would be great that at least we'll get the manual.

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.