escaner

No.

Yesterday I was on a mission with rockets in the F-5E. Before startup I selected in the kneepad 60 ms interval in both rocket types, as I was not sure which ones I had loaded (I had four Mk.151 7 rocket pods). For the ground attack, I selected the two inner pylons, set "Rocket" in the A/G mode and when I hold the pickle button, only one pair came out. Of course, I expected all seven pairs to fire on the set interval. In the end, I needed one press for each pair.

I made my own Spotify playlist for that and i get to choose the songs.

I had this problem between TARGET and TeamSpeak. Solved it in TS options -> Hotkeys, selecting "Keyboard & Mouse Only" as the input device. See attachment.

1013 images in 172 pages... That is almost 6 per page. It looks like a photo book. Sent from my MI PAD 2 using Tapatalk

I finally found a straightforward workaround to this bug. * Problem I found this a few months ago while programming a TARGET script to support BMS start/stop: there is a bug in the SetSCurve() function in TARGET that provokes this problem. When using the TARGET GUI, it always generates a call to that function with a flat curve (pretty stupid, but it is there). I contacted Thrustmaster and they replied acknowledging the problem but that they would not fix it because it "made no difference". Belsimtek does not seem to be putting any resources in the Huey anymore, so I doubt they will fix that exponential axis either. * Workaround: So, the obvious the solution was to make a TARGET script without that call, but I was lazy. Finally realized that actually you can convert a TARGET GUI mapping onto a TARGET Script. When editing in the TARGET GUI, below section "2. ASSIGN PARAMETERS", there is a button "VIEW SCRIPT". Just click it, try not to vomit at that elegant piece of programming that you see, remove all the lines "SetSCurve(&<whatever>, <whateverelse>, 0, 0, 0, 0, 0);" and save it as .tmc. From now on, just run that script instead. Do not delete the original .fcf GUI mapping in case you want to make changes and redo the process whenever that happens.

Good catch, the problem only arises with imperial units. The conversions are correctly calculated, but still displays metric units.

1. It obviously is a bug. I reported it, but no acknowledge so far: https://forums.eagle.ru/showthread.php?t=181767 2. In the USA inches of Hg are used. I guess that in Russia maybe they use mm of Hg. The origin of this simulator included aircraft of those two countries. Now there are planes with hPa (which is currently used in most of the world), but it is not updated. Also I think that german WW2 planes might use Atmospheres, but not sure. 3. TBH, I think that when a mission starts in flight, it should be already set, because that is what a competent pilot would have done before. When it starts on the ground it could be more realistic to set to a semi-random value, which would be local QNH (or QFE) the last time that aircraft flew. 4. While flying you can go to a place with different QNH (for short range aircraft like these, maybe up to 5 hPa, specially when flying to/from low pressure areas). Besides, in real life, above the "Transition Altitude", QNE is set (1013 hPa) to fly Flight Levels as opposed to Altitudes. Then you go back to the destination airport QNH before landing. These things are done in real life, it should be the same in the sim. If you trim the aircraft (and although the Spit is not very stable), with a bit of practice it is not that hard. Anyway, in the sim it is enough to set the altimeter to the airport elevation before takeoff and leave it there. No need for unit conversion or in flight changes most of the time.

Set the kollsman window in the altimeter to the correct QNH. It is shown in the briefing (left Alt B) in mmHg and inchesHg. You will need to convert to hPa, which is the unit used in the altimeter. Lochini elevation is about 1600 ft, not meters. The Spit altimeter also displays ft.

And it is not properly finished yet...

I can confirm this bug in current 1.5. Last Tuesday was OK, so it was introduced in the latest patch.

It happens to me from time to time with any module. I just cancel the window and it is ok. Sent from my Redmi Note 4 using Tapatalk

ILS will not disengage EGI. Only HARS and TISL do. You cannot have autopilot without EAC.

According to the Pilots Notes, boost pump should be turned on AFTER starting the engine. Before is only used momentarily to pressurize the fuel system. But the Pilots Notes startup procedure will not work on DCS Spitfire, so whatever works seems as realistic as any procedure right now.

The DCS training mission about starting the Spitfire does not even mention the boost pump. It is obviously required in this module, but I don't think the actual aircraft had these problems just because it didn't exist in some of them.

I had the same problem with the engine sputtering and stopping (especially when increasing throttle) at about 17,000 ft. No low pressure light in my case. Engaged the booster pump and problem solved: climbed to +40,000 to make sure that was it. :) The DCS manual does not say to engage that pump. Pilot Notes yes, they tell to do so just after start, before takeoff and before landing. It is weird tho as there were planes without this pump. Maybe it was only really needed for the external tank but was always used just as precautionary procedure.

I have just checked the Spit, P-51 and Huey and their altimeters are OK: set to QNH (you can find it in the briefing) and they read airport elevation. PS: In the Huey there was 40ft of difference, but that should be within limits.

I came just to report this. Nav lights off: left red reflection on ground and white reflection under center of airplane. Nav lights on: right green reflection on ground only for a second and disappears. White reflection under center of airplane stays.

I have seen videos claiming that after startup you shuld lower the DEM button cover and turn off pumps and/or bougies (don't really remember well), but I cannot find any of that in the manual. So, what is the correct configuration of the startup panel once the engine is running? Thank's a lot!

IIRC, if you hit the extend or retract again, it stops moving and stays in the current position. Sent from my Redmi Note 4 using Tapatalk

For the same boost, increasing rpm does increase power delivered by the engine and thus the speed should be higher. There are many inaccuracies throughout​ this thread, best if you read that FAA document that acdelta57 linked.

Yes, I bet the problem is the DHCP lease time, as it only lasts for 1h20m. That means that when that time is elapsed, your computer needs to renegotiate you local IP address with your DHCP server (normally your router), which breaks network connections. To solve it, open a browser and put the DHCP server address preceded by http:// in the navigation bar (normally http://192.168.1.1 if it is your router). Authenticate (user and password should be in a sticker in your router or in the documentation from your ISP), go to "Setup" and look for a section called "LAN". Look for DHCP there and set the field "Leased Time" to e.g. 12h or 24h. Note that this field is normally set in seconds or minutes. Save and the next time that you start your computer the problem should be solved.

IIRC, that message appears when the Maverick does not have a lock. You can tell from the small SA cross in the Maverick MFCD. It flashes when the missile is locked and tracking a target.

It is fine if you don't reach the runway at idle. If you lower flaps or gear you will have more drag, and also if you don't fly perfectly coordinated with the ball in the turn coordinator centered using your pedals (yaw axis). I just wanted you to realize that between reaching the runway at 200 mph and not reaching it at all, it must be possible to reach it at the correct speed. You will need to keep adjusting engine power throughout the approach, there is not a magic setting that will do. As you start lowering flaps and gear the resistance increases and you need to readjust your pitch, trim, throttle and yaw. In a visual approach, you need to look basically two things: airspeed and runway. As I said before: maintain the airspeed with pitch (if you are slow, pitch down; if you are fast, pitch up), trimming it. And keep your glideslope with throttle (if you are low, add power; if you are high, reduce power). You can also look at the ball from time to time to check that it is centered and you fly coordinated. Have you flown more aircraft in DCS? The WW2 fighters are probably the hardest to start with along with some helicopters.

OK, I need you to do this: 1. Open a cmd window (Windows + R, then type: cmd) 2. In the new window, type the following command: ipconfig /all 3. Look in the section for the connection you are using (either Ethernet or Wi-Fi) and look for "DHCP Enabled", "DHCP Server", "Lease obtained" and "Lease expires". Report back with those values.