xxJohnxx

Dies ist ja so eine Sache. Meiner Meinung nach kommt die mommentane Sichtweite recht gut ans orginall an. In echt ist es echt schwierig ein anderes Flugzeug gegen Wolken, das Gelände oder sogar bei gutem Wetter gegen den Dunst zu erkennen. Vom Boden aus sieht es immer einfach aus. Man hört das Flugzeug, schaut in den Himmel, und nach ein paar Sekunden hat man es auch schon in Sicht. Vom Flugzeug aus ist es aber eher die Suche nach der Nadel im Heuhaufen. Ich hatte schon ein paar knappe Situationen wo wir zu zweit im Cockpit einen Flieger direkt vor uns, in entgegenkommender Richtung nur im letzten Momment gesehen haben. Und das obwohl wir beide nach Fliegern ausschau hielten. So wie es Mommentan im Simulator ist, ist es von meiner Erfahrung aus nicht ganz daneben. Im Bild von Nirvi könnte der Flieger in einer Entfernung von 1.1 Meilen etwas größer sein, aber alles andere ist meiner Meinung nach unrealistisch. Kleine Flieger sind einfach sehr schwierig zu entdecken.

Hanging in your seatbelt sure isn't comfortable for long either.

No, so far it is not possible to laser something without the use of either the JTAC, another (AI) airplane or CA. At least the default mission editor tools won't let you do this. You might be able to do it whith scripting though. Not sure about that.

The wingspan is just necessary if you don't have the radar available. It alows you to judge the range by setting the wingspan first, and then adjusting the range until the circle arround the piper matches the wingspan of the target. This is the same system as in the P-51 and is obsolete in normal operation, because the radar will give you the range as well. However, you can set the wingspan to give yourselfe a backup.

Hi, While waiting for release, I thought I would make a small video talking a bit about the MiG-21Bis, the aircraft, some of the systems and stuff like that. As the MiG-21Bis hasn't been released, you obviously see any cockpit footage, and I am using the AI MiG-21Bis to point out some things on the exterior 3D model. Please leave your comments, and tell me if you find such videos intresting! Best regards, John

And this is the last video for now on the F-86. Showing how to employ the GAR-8 Air-to-Air missiles. Once the full manual is released and there is more about the LABS, I will do a video on that as well.

Nope, it is not clear that Fullscreen gives better performance. Look at test #5 and #6. There is no framrate diffrence at all. And this is with SLI enabled. Just in Surround there is such a huge performance diffrence between fullscreen and non-fullscreen. And why should the desktop be drawn anyways? It is clearly neither visible, nor is there much to draw.

Maybe a bit obsolete by now, but just for completeness: Air-to-Air with the cannons:

Yes, fullscreen mode gave me best performance when using Surround + SLI. However, I am not sure how Surround will work with the DVI connectors. When configuring Surround within the NVIDIA Controllpanel it showed this connection guide: The circles indicate the ports for the Surround displays. The suqare indicates the port for an aditional display. From top to bottom the ports on each card are: Display-Port, HDMI, DVI-D and DVI-D. I am not sure if this relates to how you allready have connected your monitors, but I am not sure that you can run surround when using the DVI-D ports. You would have to do some more reasearch on that topic. However, it probably is possible to connect all 3 monitors to the first card (two with DVI-D one with DisplayPort) and then use the non-Surround SLI mode (as I did in Tests #5 & 6). This will work for DCS just as good as Surround, however it might be a bit problematic for other games, as they might not support 3-screens without Surround.

Hi Rajdary, No, I can get SLI to work while Surround is turned off (see second post, test 5 & 6). My DCS doesn't crash when I have surround and SLI off and 5760x1080 selected (test 3 & 4). Daisy-chaning only worked for me with two monitors as well. Make sure that you enable DisplayPort 1.2 within the onscreen menu of the monitor. The Daisy-chained option doesn't allow for Surround though. I had Vsync off for the tests, to see the unfiltered impact on framerates. I generally have it off anyway. Problems with the RGB colour range? I am not sure what you mean, but my monitor connected to HDMI looks identical the other two monitors connected to DisplayPort in display color and brightness.

Yes, I am intrested to see what EDGE will change. I also updated the second post. Did some more tests with running 3 monitors in the 3D Performance mode (SLI without Surround). The results where quit intresting as well. I wonder though why DCS in windowed mode does not run at such bad performance in SLI, as oposed where it will run at good performance in fullscreen mode.

Today I changed my wiring, so all monitors would be connected to one card. This allows me to run SLI without having to use NVIDIA Surround. The results are intresting: Test #5: NVIDIA-Surround: disabled DCS Fullscreen: disabledThis test resulted in slightly lower FPS than Test #1. However, it felt smooth when moving the head and when close to the ground. Alt-tabing out and back in possible without problems. Test #6: NVIDIA-Surround: disabled DCS Fullscreen: disabled This test resulted in slightly lower FPS than Test #1 and Test #2. However, it felt smooth when moving the head and when close to the ground. Alt-tabing is problematic and it takes some time to get back into the program. FPS Comparison: As you can see, running in NVIDIA Surround with DCS in fullscreen mode gives just slightly more FPS than running in non-Surround SLI in fullscreen and especially in windowed mode. This is a huge benefit, especially as the windowed mode doesn't take such a big hit on performance as it did when running in SLI. The 3 diffrent modes in the NVIDIA controllpanel used for the tests: Test #1 & Test #2: Setup: Two monitors are connected to the first GTX780. (One DisplayPort, one HDMI) The third monitor is connected to the second GTX780. (Display Port) Within the NVIDIA Controll Panel "Surround" has been selected. Test #3 & Test #4: Setup: Two monitors are connected to the first GTX780. (One DisplayPort, one HDMI) The third monitor is connected to the second GTX780. (Display Port) Within the NVIDIA Controll Panel "Activate all monitors" has been selected. Test #5 & Test #6: Setup: Two monitors are connected to the first GTX780. (One DisplayPort, one HDMI) The third monitor is connected to the first GTX780 over a DisplayPort daisy-chain. Within the NVIDIA Controll Panel "Enable SLI (maximum 3D performance)" has been selected. Conclusion: All the 6 tests performed showed that SLI has an huge impact on performance. Running without SLI (Test #3 and Test #4) ran on about half the FPS than all tests with SLI (Test #1, Test #2, Test #5 and Test #6). It also became apparent that NVIDIA Surround has not that big of an impact when used for DCS. Connecting all monitors to a single card and enabling SLI gave nearly as good FPS as Surround did. NVIDIA Surround proved to have the best framerates when running DCS in fullscreen mode. It also proved to have worse framrates than a non-Surruond setup in SLI, when running DCS in windowed mode. Therfore, if you want to run DCS World on a 3 monitor setup only in fullscreen, NVIDIA Surruond gives you the best possible performance. However, when you want to run DCS World in windowed mode, it is better to for a conventional SLI configuration with all monitors connected to one card.

Hi, I have lately started to do some testing on a multi monitor setup for DCS. I wanted to share some of the early results with you and would like to hear opinions from people using similar setups. I use three identical 1920x1080 screens, giving me a resolution of 5760x1080. This resolution is set within DCS, together with the 1 Monitor option (the 3 Monitor option makes the side screens look weird). My testing mainly concentrated on the use of NVIDIA surround and the fullscreen vs. non-fullscreen mode of DCS. For testing I used a short track (see attachments) and FRAPS to log the FPS. Test #1: NVIDIA-Surround: enabled DCS Fullscreen: enabled This configuration resulted in maximum FPS. There where no visible stutters. However, alt-tabing out and especially back into DCS proves a bit difficult, as it takes quit some time. Test #2: NVIDIA-Surround: enabled DCS Fullscreen: disabled This configuration resulted in lower FPS. The average FPS where above 40, however visible stutter could be noticed when the view was moving fast or when close to the ground. Alt-tabing out and back in works without problem. Test #3: NVIDIA-Surround: disabled DCS Fullscreen: enabled This configuration resulted in similar FPS to Test #2. The stuttering in fast view changes and close to ground was very similar to Test #2 as well. Alt-tabing is problematic and it takes some time to get back into the program. Test #4: NVIDIA-Surround: disabled DCS Fullscreen: disabled This configuration again resulted in similar FPS to Test #2 and #3. The stuttering was the same as in Test #2 and #3 as well. Alt tabing however, works flawlessly and fast. FPS Comparison: As you can clearly see, runing DCS with NVIDIA Surround and in the fullscreen mode gives me nearly twice as much frames as all the other tested posibilites. Generally the simulation feels running smother. I am wondering what could cause the huge drop between the active and disabled fullscreen mode of DCS. Back when using 1 monitor there wasn't a noticable change at all, wheras here, it is quit diffrent... Just to clearify, all the 4 tests had DCS World displayed over 3 monitors in 5760x1080 resolution. There is also more to test about the enabled vs. disabled surround mode. The problem is: When deactivating surround in order to have all displays running, my setup is forced out of SLI, which might explain the huge diffrence between non-surround fullscreen vs. surround fullscreen. I will do more testing on this once I get myselfe the necessary adapters to overcome this problem. Another point worthwile having a look at would be SoftTH. Understanding that it uses one graphic card to render the whole picutre and then send it to the diffrent ports, it might also have posetiv or negativ impact on performance when running with/without SLI. I plan to do some more testing on this also. I would appriciate your inputs and comments on this matter. I would like to get most out of this setup, and I guess we all could benefit from exchanged experiences! Best regards, John FPS Test Track.trk

I have the feeling that this is just the concrete texture beeing to close to the ground texture. Therfore the ground texture is clipping through at certain angles.

The engines are whineing because when you increase the collective fast the rotor rpm is starting to drop. Therefore the governor is increasing the engines rpm quickly. The spooling up and high load cause that whine. High engine rpm then just adds to this effect.

It doesn't make it static, however an automatic bomb release only occures if you used the caging. As long as you hold down the cage button, the bomb won't automatically drop.

I might point you to this video I made: This also shows the morse-code problem in action. One user commented that he belives that multiple morse-codes play at the same time, making it more difficult to identify the right station. I did not particullarly test this, however I noticed similar stuff while working on the video.

I am still strugling to fight gravity, let alone the MiG-15. Thanks for the tip though!

One thing that you can do in the Sabre is to shake the canopy off. If you are doing some hard rolls the canopy will slide open and be torn away by the wind.

Most of the aircraft don't, as you don't need to do that during flight. Some military aircraft have a takeoff-trim button. The F-86 has a lightbulp. When you trim "nose up" and the light flickers briefly, this means that you are in the takeoff-trim position for the vertical stabalizer. When you trim "left/right wing down" and the light flickers, you are in the takeoff-trim position for the aileron. You don't want to mess with that lightbulp during flight though. Trim out your control forces. Don't expect an aircraft to be completly stable. It always needs small controll imputs.

What do you mean with that? I managed to release between -30° and -70° of pitch without any problem. Just make sure that you release the electrical caging just when your pipper is over the target and start holding the weapon release button down before that.

Okay, thanks for the reference.

It has the following capabilities: 4 Lights show the direction towards the thread. Each light is representiv for a sector (0-90°, 90-180°, 180-270°, 270-360°). When radarwaves are recived (searchmode, not locked) in one sector the respective light will blink and you will hear a beeping sound. One thread might illuminate two lights, if it is right between two sectors. Two threads might only illuminate one light, if they are in the same sector. If you are locked by a thread, all 4 lights will illuminate continusly as well as there will be a continus beep. There is no way to identify from which direction you are locked up. The reception of the RWR has blind spots above and below the aircraft, from where no radarsignals can be detected.

Where was that stated, I wonder?

Dive-bombing with the automatic bomb release: