fjacobsen

I know this is the Gazelle forum, but still... For some years ago I got the chance to try a UH-1D simulator at the German army's simulator center at Bückeburg - cool experience. I aksed the instructor about VRS in a UH-1D and he told me that it was almost impossible to get into VRS in a normally loaded UH-1D by accident. You can force into it if You really want, but otherwise it would not enter it easily. I think many heli-sims exaggerate VRS making it too easy to enter, thats also what I experience with the Belsim Huey and thats why some want to see the Gazelle go into VRS easier too. Personally I have entered into VRS in the Gazelle quite a few times, so it is modelled.

It´s not meant as a negative input. The video shows exactly how the Razbam M200D INS update works and is very well explained by You. When experimenting with it I also found it odd. Regardless where I pointet the radar on the ground, the INS position for the waypoint I used for the INS update is always shiftet back to where it is supposed to be according to the mission editor. In reality the INS doesn´t know how much and where the position has driftet. So by not updating exactly over the position in "flyby" mode or by putting the radar diamond on the exact spot, will "correct" the INS at a wrong position, which should be indicated by the waypoint indicator move to that wrongly placed update position. FinnJ

Nice video, but as I replied on Youtube, this is how I expect it to work: "I fully agree and the problem is with both the Fly "Over" and Radar update method. I´m sure You need to press the Rec button when You are exactly over the correct position for the waypoint ie. the Hooverdam itself and not some miles away where it is still in the HUD. Also for the radar update the diamond spot must be put on the Hoover Dam to set the exact position. Especially in this mode You should see the waypoint cross move to where the Diamond spot was placed when pressing the Nav update button and not by some magic move to the correct position by itself, despite the diamond spot being off. In both cases there would be no way the INS system could now how to correct by doing as shown in the video." FinnJ

Using OBL with Radar update I found this with DSC 2.0.... I have placed waypoint 2 exactly on small building out in the desert. Flying towards it, the waypoint cross is misaligned a few 100 feet from the builing towards my position and slightly to the left. Using OBL and TAS, I put the radar diamond a few hundred feet behind the building, sen from my position and press the position update button - and then VAL. The waypoint cross does move, but not the point where I pointed the radar. Instead it moves a tad closer to the building, but still infront of it, seen from my position. My expactations are that the waipoint cross should move to whare I pointed the radar diamond when I pressed the update button.

Why pre-order finished modules :P

Thats a clear indication that we will get the Spitfire (P-51 used as placeholder) and Normandymap in just a few hours. The Starfoce update is for the Spitfire and Normandymap for sure :D Did I just re-start the de-railed hypetrain ?

Any news on the video or more detailed explanation ?

It will never be precision bombing when using freefall bombs. INS bombing will only make it possible to do some kind of blind bombing In bad weather, otherwise using CCIP or CCRP will be as accurate. For ude wit Laser guided bombs it´s a different matter, since that way You can drop the bombs at the right point with no visual cues on the ground.

Hmm - no update yet ?

I remember a similar situation with the Belsim Huey. Right after release we where also told how accurate the FM was compared to the real thing. Afterwards the FM changed alot over the various updates. The same is what we are going through now with the Gazelle. I have no problem with this, since Polychop shows steady progress and I´m sure we will end up with a FM much more refined than the one we got now. Regardless these inaccuracities, I still love to fly the Polychop Gazelle. FinnJ

I think the devs has mentioned that this might change, so that in SP Yaw also might be controlled in auto-hover.

:thumbup: Super duper that it seems the culprit has been found and a possible fix is in the pipeline. I wonder if this Ground ranging mode also is what affects the F-5E. FinnJ

It depends on whether the settings in the Nvidia control panel are set to "Application controlled or "Override". FinnJ

We are not talking lower fps, but stutter, whuch was introduced by the update released for appr. Two weeks ago. Try to set cockpit displays to "1024 every frame" and uncheck Vsync. On my system makes it run smooth again, but I still have occasional stutter that seem to stem from some texture loading. Finnj

Alt+Ent to go into full screen does lessen the stutters, but does not remove them. FinnJ

Most aircraft has both mechanical and electrical fuelpumps. The electrical ones are mainly meant as backup, but are on some aircraft also required above certain altitudes and when flying inverted.

Have You checked Your controler calibration ? I don´t see this with my CH-Products Throttle Quadrant. FinnJ

+1 M2000C & F-5E are not usable for the time being in DCSW 2.0 :(

According to the "Aircrew nonnuclear Weapons delivery Manual" max pitch compensation is 45° up/down. Quote: "A 360-degree compensation is provided about the aircraft roll axis and with the antenna set at either extreme limit of 45 degrees in elevation, 90 degrees of pitch compensation is provided in the opposite direction...." With the radar dish tilted 32° up and pitch at -20° the dish would have to move 32+20=52° and max is 45°, so since it exceeds it limits it will point 32-(52-45)=25° upwards. Additionally the radar beam at the 40nm range is a 8° cone shape (±4°), so that means that the lower part of the beam will be at 21°. In the 20Nm range this is tilted further ±3°, so becomes 18° at the lower part of the beam. So "Fox One" is right about the limit of -13° with the antenna tilted 32° upwards and that something isn´t right. FinnJ

It doesn´t seem to work yet. With the Mig-15 and the camara enabled either always or just for Tracks it will show gunsight images in the lower right corner when the gun is fired in Black/White photo style. With the F-5E (Currently) this doesn´t seem to work and looking on the sight there is a label telling "No Film", which I guess is a hint for this feature not having been implementet yet. FinnJ

I wish Belsimtek would have called it Mig-28, since thats how it looks like.

You seem to be right. The left AIM-9 will always trigger the tone when the GUNS/MISSILE and CAMERA switch is on regardless whether the missile is selcted or not. FinnJ

Strange thing with missile tone is that when both missiles are loaded and turned off on the armarment panel and the sight switch is set to GUNS/MISSILE and CAMERA, then the missile tone is present. selecting both misslies and then shooting one of them of and then turn off the other misslie makes the tone go silent until the missile is switched on again. I guess that the tone should be present either allways when the the GUNS/MISSILE and CAMERA switch is On regardless if there are 2 or only one missile present and regardless whether any missle is selected - or the tone should only be present when the GUNS/MISSILE and CAMERA switch is on and any of the misslies are selected (Both, Left or right). Currently there is no logic behind when the missile tone is present (at least I cannot see it). FinnJ

This..... Or maybe (though it´s not realistic) add the option to be able to kind of lock the target in the Viviane inorder to issue "Attack my target" command to to other units.

The issue is present in both the L and M version.