illern

I been trying to use timesystem (TID- Output and Time fin in HUD) while flying the Red flag campain for the Viggen. But as a few other has written it doesn´t work like it should I think. For example: In mission 7 the target waypoint is M5, it has a ToT at 17.23.00 according to the TID - Output. I input 0.84 mach and press B4 Input 0.57 mach and press B3 and the same for B2 and B1. When flying at 0.57 to B2 the time gets way behind. The fin is at the bottom and when I get to B2 the TID - output says I am 2min behind schedule. As soon as the waypoint changes to B3 I am all of a sudden 5min ahead of schedule. Also did a test when flying towards B4, the fin was at center indicating I am behind. Change to M5 and then I am way ahead and I haven´t even increased the speed to mach 0.84 yet. Something looks like it´s off with the time calculations. Also as others have stated it shows 9 instead of a - sign when behind schedule. This test was on v2.2 alpha /illern

I manage to do a workaround for this that works on my machine at least. Since I don´t have space on my SSD for the whole DCS I have it installed on the striped raid array. But I did move the folder "Eagle Dynamics\DCS World 2 OpenAlpha\Mods\terrains\Nevada\Surface" to the SSD and made an Symbolic hardlink to it instead. Now it reads the surface file from the SSD and the rest of DCS on the array. Now I can use the radar without any problems at all. Here is how I did it: 1. Copy folder Surface from path above to a new folder on the SSD. I made mine "C:\Hardlinks\DCS2\Nevada\Surface" 2. Rename original folder to Surface_old 3. Open up Command prompt as administrator 4. Make a hardlink directory in the original path that points to the new path.(/J is for Directory junction aka Hard symlink) mklink /J "D:\Spel\Eagle Dynamics\DCS World 2 OpenAlpha\Mods\terrains\Nevada\Surface" "C:\Hardlinks\DCS2\Nevada\Surface" Exchange the path for your path. First is the new link and second is the new folder location. 5. Now you have a folder shortcut named Surface that points to another location but Windows thinks the files are still in original place. The mklink command is explained on this site where I took it from. https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/ /illern

Any more news on this problem? Wanted to test the new campain for the Viggen but cannot play NTTR at the moment due to the radar problem. Have done some testing and as soon as I turn on radar (with range more then 15) I get 1-10fps. This is due to 100% disk access to DCS folder. Turn off radar and fps returns. The file being read is "Eagle Dynamics\DCS World 2 OpenAlpha\Mods\terrains\Nevada\Surface\Nevada.surface5" 3,4Gb big. (Normandy has a 6Gb file maybe thats why some have even more problem with that map) See attached picture of the diskaccess during radar on. /illern Edit: v2.2 alpha Disk with game is 2 SATA3 HDD in Striped raid. Using Oculus rift.

Hi! In the FR22 radio and the base selector there in one channel missing. There is no channel 10. In all other places where there is a "ALLM" channel between the normal channel numbers it will continue counting the channels after "ALLM". But not here, it goes from 9 to ALLM to 11. /illern.

Hi! I have done some testing with regards of the fuelsystem. Why sometimes we have 135% fuel and some other inconsistency. All tests are done from the mission editor where I set up the initial fuelload. Then enter aircraft and change fuel in rearm/refuel communication dialog. See attaches table of test and results. Example: First test, started with 0% internal fuel, 0lbs and total 54% without X-tank... Fuelinstrument in cockpit says 45% as will refuel dialog. Change to 100% in refuel dialog and you will end up with 124%. Added X-tank in refuel dialog and 100%. It will be 126% as it is supposed to. Remove X-tank in refuel dialog and 100%. It will be 103% as it is supposed to. (Had problems inserting my table so I attached an image instead) Problems: In the first test with 0% internal startfuel and you do a refuel in the F8 menu without X-tank you will end up with 124% fuel. Add an X-tank and it will show correct amount of 126% When we use an X-tank from mission editor all fuel values will be incorrect when you enter the aircraft. Especially when you set 100% internal fuel in mission editor. Then you will end up with 135%. If you enter refuel dialog when you have 135% it will correct the problem when you accept 100% in the dialog. In the #5 test when I changed from 45% to 50% in refuel dialog and after refuel opened up the dialog again it now said 72%! If you start a flight with X-tank and 126% fuel and use fuel so you land with less then 100% it will not refuel the X-tank. You will only get 103%. To get 126% again you have to drop the tank and then refuel they will add a new tank with fuel.(maybe this is supposed to happen?) /illern. Edit: Always forget the version. v1.5.8 beta

Hi. Thank you for the solution. Should have read the manual again before posting. Have read it again and it works as you described. Flares release on quick release button. ("Fast countermeasure release" in control settings) /illern

Hi! I cannot get the flares to release no matter what setting I use. If I load up a U22/A and a chaff/flare pod. Make sure I have both chaffs and flares in them. (Load up using ground crew) I have tried every setting from A-3, 0 & 4 and R RF F. I then use INT och KONT to release but only the chaffs get released on R and RF settings. Anyone else have this? /illern

I also thought that it was an error with the TILS when I tried it from the beginning. But there is 2 quite good pictures in the LNS viggen manual that describe what will happen. As the other said the transmitter is offset from the runway on the left side. It´s pointed so it cuts the runway centerline at 900m out. So the actual guide beam TILS is using is almost always to the right of the runway. At 10-20km out from the airfield you will be quite far off to the right side. Also depending on how you do the aproach you can get a 45 deg steering command to get to the guide beam. Page 143-144 has these pictures in the manual that comes with the game.

Yes it happens at every spawn.

So I made a video of the problem instead of trying to describe it. A 30s clip when I have engaged the autothrottle at 500m. The AC is clean with no external load. Gear down and now I´m easing it up to 12deg AoA. When I hit 12 deg the throttle goes bananas. That is not a correct behaviour of a regulator. The throttle move between min/max position several times in an instant. Hope the video works, I´m not used to making them. /illern

I have also noticed wierd behavior after the patch if you are in SPAK and fly straight and level. Even the smallest amaount of right rudder and back to center(confirmed with contol input window) the aircraft will bank heavy to the left. To stop that you need to input left rudder once and back to center. If in the left bank and disconnect SPAK it will also stop and you can fly straight and level again.

I´m in 1G and no more. I´m doing this really gently. Also with more tests if you gently holds it at 12deg AoA the trottle will switch between Min/max several times in a second. You can both see it and hear it since it will go below flight idle and you can hear the click when it is below FI.

I have found a problem with the autothrottle. At mode 1 it looks like it´s working correctly but in mode 2 and 3 it´s not. In mode 2 and 3 it´s supposed to regulate the throttle so the aircraft is at an angle of attack 12 or 15,5deg. Engage the autothrottle and increase AoA to more then 12deg in mode 2. The throttle will at this point be in max throttle without the ab. Decrease the AoA and when it hits 12deg the throttle will instantanious go to min throttle and from there start building up throttle response again. Same thing with mode 3 and 15,5 deg, when it comes down to 15,5 it will go to min throttle. This makes the aircraft loose altitude rather quickly. First of all it should gently reduce throttle response when coming down to setpoint AoA. Then in the SFI manual part 1 capt 1 it also states that the throttle have higher authority to speed increase than speed decrease meaning it should be slower at decreaseing throttle responce than increasing. Ref: Swedish SFI part 1 chap 1 tab 10 page 3.(manual page 165) It should also increase the engine rpm by 1,5% when the gear is lowered when in autothrottle. I cannot see that this is happening. /illern

I had the same issue. But don´t know at the moment if my SI Slav was set to Från. Took off från airport nr12 in the kneeboard list and set L1 to nr13. When I used the TILS aproach the adi showed the right hight but wanted me to be way off to the right. Same with HUD.

I´m going to further explain why I think its wrong. In the manual of the real Viggen it explains how the afterburner works. In Chapter 1, section 9 point 3.2 it says: "The thrust changes linearly through each zone in succession as the thrust lever is moved, but there is a slight stepwise change as each zone cuts in or out." It also says somewhere that the 3:rd stage is longer. But that is also visible on the indicator. As the function is implemented now it looks like it is 3 digital stages only. The needle jumps between stage 1,2,3 to fixed positions instead of analog positions as stated in the manual.. /illern

Hi! According to the manual the picture on the radar should be visible for about 30s when activating the memory mode. From page 117. Memory mode When pressing the memory mode button, the radar transmitter will cease to transmit and the current radar picture will be frozen. The displayed picture will last about 30 seconds. When I use it I will only get the picture for 5s then it has faded out completley. /illern

When I use the afterburner I can´t get it the nossle to fully open. See attached image. I have the throttle at 100%. Checked both with the controller indikator in the overlay(see pic) and in Axis tune. But the nossle indicator is only at 1/3 of zone 3. /illern

I have pedals that are 2 single axis.(its an Thrustmaster T500 RS wheel) In order to have thoose pedals in DCS i need to use both axis on the same rudder input. So I put Y saturation to 50% on both and invert one axis. If I´m in SPAK mode then the wheel turns correctly but the rudder missbehaves and doesn´t center. If i´m disconnect SPAK mode then both wheel and rudder moves and center. After liftoff and gear up I can use SPAK and rudder again.(it is REALLY sensitive to rudder input) I cannot use any other Y saturation due to the two axis. They need to meet in the middle.

I had the same Black screen bug whenever I tried to change controls. I did this to fix it. Find this folder after the bug and you forced DCS to shut down: C:\Users\[you]\Saved Games\DCS.openbeta\Config\Input\AJS37 In this folder I had one empty folder "Keyboard". Right click on AJS37 folder, choose properties and untick "Read only" for all sub files and folders. Restart DCS and it worked for me. *Edit, I did a reboot after the first failed attempt but it was the same. Didn´t work for me until I made the change above.

Well, now I feel kinda stupid... Been looking at the control settings and didn´t spot the wheelbrake axis command. Had a analog slider set to the wheelbrake on the F-86 and it was not at the 0% position.... Problem solved. /illern.

Hello! Just tried to taxi and takeoff in my F-86 and found it impossible. It needs >90% thrust to start moving when it is on the ground(tarmac at airfield). It is supposed to start moving at 65-70%. The wheelbrake is off as it will stop when above 90% and I apply the wheelbrake. This happens everywhere it is on the ground. Tried training missions and instant flight. The parking brake lever is in its in position. All my other aircraft is OK. This only applies to v1.5.5 beta. It works in v2 and I dont have v1.5 stable installed to test. My beta version is the latest, v1.5.5.60565 I have tried the repair function of DCS and I still have the same issue. Anyone else have this issue? /illern

ok, now I see that I got it wrong with the aerodynamic trim tabs. But I have done some more testing and it looks like the only trim that actually are doing something is the rudder trim. Apply even the smallest rudder trim and the airplane is going nose down right or left. Only way to get the airplane to fly straight is to set exactly center position on the rudder trim. The other two trims are only moving the trim tab and limiting my stick movement. Noting actually happens to the plane until I get to the end of trim when I no longer have any movement of my stick left, then the plane suddenly turn and you cannot do anything about it but reset trim so you can turn the opposite direction. /illern

If I use for example right trim then left aileron can´t move as far as before trim. If I trim full right aileron then i can´t bank left at all. Likewise to the left trim. When on ground I still can use full left and right aileron even when fully trimmed. But in the air it gets crippled. Trim is not supposed to limit normal movement of the surfaces. It should only deploy the small trim surfaces. Attach a track where I use full aileron movements to show that it cannot move to one side after trim. Start on the ground when it works and then takeoff to show when it stops working. /illern trim.trk

Feel how the aircraft is moving and correct your stick and rudder input to keep it in the air. I landed my A10 with only the right rudder left.