JorgeIII

Your're right Quirk. The axis tunes Bushmanni and I posted are better than the one copied from de A-10 but not good enough (lack of precision). I enhanced the axis curve and managed to get the same precision of the keyboard. Values: Y Saturation:56 Dead zone: 13 (you must use a deadzone so the slew x & Y axis don't mix up) Custom curve: 10, 10, 10, 10, 10, 10, 17, 40, 60, 80, 90. Try it and enjoy, :thumbup:. Basicaly I looked for the smallest amount of movement I could get on the shkval with an axis. Using a saturation of 100 the smallest movement of the Shkval correspond to a custom curve value of 6. Under 6 the Shkval wont move, and over 6 it becomes too sensitive too quickly. So I made a flat curve with many 6 in the first 2/3. Then I found it worked better with a lower saturation. I used 56. The smallest custom curve value wich would move the Shkval with a saturation of 56 is 10. This value still moves the shkval a little too much, is up to ED to correct this.

Thanks Bushmanni, I'll try your custom curve values myself. You leave Y saturation at 100, right?

Try this for the X and Y axis of the Slew in the TM warthog: Y Saturation: down to 15 (10 to 15) Dead zone: 2 No curves. It works well (with a Sat of 15), but sometimes I have to use the keyboard if the target range is over 6-8 km. If you use a saturation of 10 it wil be easy to lock distant targets but the shkval will move much slower. Why no curves? It should be easy with this values plus a curve of +20, but the Shkval doesnt register the small imput of the first 2/3 of the curve.

May be its related with ballistic coefficient an final energy at impact? GBU 10 and GBU 12 (Laser guided) drop in game much faster than GBU 31 and GBU 38 (inercial and GPS guided). This difference in falling velocity doesnt looks right. Energy = M.V 2 (square velocity). So GBU 10 & 12 will have much more kinetic energy. Penetration is related to Energy on impact, bomb design (materials and shape, tipe of point, like FMJ vs hollow point and HE vs AP) and fuse time. Most likely is a bug.

Please ED fix this ASAP with high priority, we will appreciate this. In the squadron we waited till DCS Wolrd was out of beta to make it the official version for flying. We couldn't have any flight since this weekend. We won't be able to use the sim until it's fixed or a work arround is found. We are getting this connection interrupt problem, even if we have a low ping and hight bandwidth with no package lost connection to the local dedicated server. If it help the missions tried included slots for A-10C, SU-25 and ground vehicles. The problem is intermitent but frequent and only afect some of the connected pilots. Changing in game options for connecton speed doesn't help. I will upload log files when I get home.

Well after reading the forum this problem seems to be related to Master server, to come and go, last arround 30' while most or all the players can't log in and get a CTD and then go away and everything its working ok again for a few hours. It's very funny, most of us started changing things in ower PCs while the problem lasted (booting, unplugging peripherials like trackir, muting TS, etc) and after 30' when this problem temporary remited from de M Server side we asociated what we where doing with a solution. Many "solutions" posted in other threads...jaja. Hope it dosent take too long for a real solution. Of course, next time it happeds, the first thing i'm gona do is close TS...

Finded a solution: close Teamspeak, run DCS World Multiplayer, connecto to Master Server and then launch Teamspeak again. You can also mute TS instead of closing it. It worked for all of us today.

Same problem here, just started and all my sqruadron has the same CTD when trying to connect to Master Server (about 10 pilots). We where flying just fine till now.

Anyone else tried this? I would like some confimation before messing up with more lua files. Thanks.

I have a two monitors setup, copied the .lua file from DCS A10 to DCS World, selected the profile in the options menu, unchecked fullscreen, and everything its OK in the A10 and no conflicts with P51 witch I use with only one monitor. Don't know what will happen when we can integrate de Shark to DCS World. Hope they make a selectable profile for each aircraft so in the near future we don't have to change the profiles every time we choose to fly a different plane. I found two problems with the 2 monitor setup: 1) Rearming & refueling menu is splitted between the two monitors. 2) Radio comms menu is on the left of the left monitor, uncomfortable to read. Any known way to place them correctly? Thanks.

I just configured imputs and multimonitor profiles in 5', not too hard. I found two problems with the 2 monitor setup: 1) Rearming & refuelling menu is splitted between the two monitors. 2) Radio comms menu is on the left of the left monitor, unconfortable to read. Any known way to position them correctly? Thanks. PS: Hope ED makes a monitor profile selector for each DCS World Aircraft, I wouldn't like to have to change the profile every time I choose to flight a different plane.

Impressive! Hard to tel the difference from real P-51 photos. Excelent job!

Crashed in the first 2 attemps to take off, don't have a track of those. It'll take some practice to master the control of such a torque force (single propelled engine and about 1200 hp!). This video shows the next 3 successfull (barelly) take offs and landings. Great sim!

Hitting some BTR-80 with the .50 cal. Quite effective at close range! Got some damage and lost my sights in the process. For a nice shooting advance to minute 3:00. Link: http://www.youtube.com/watch?v=49ASZjeFAcQ&feature=player_detailpage

Thank you. It´s finaly working as it should. I´didn´t have the other joystick connected. I don´t have an exact diagnosis and solution but here is whet I didn´t, might help anyone having this problem: 1) Disabilitated Force Feedback from the game and de .lua file again. 2) Disconnected and reconnected all periferals (Mouse, keyoard, joystick) 3) Reiniciated the PC and the game. And all was working fine! I still get the problem sometimes, witch is quite disturbing when it happens while autohovering, but´s tolerable. I changed TrimmerTauInverse at FMoptions.lua to 4, it´s feel like it trims better.

Any one?

I’ was flying BS with a Logitech joystick (Freedom 2.4) with not problem at all with trimming. Yesterday I bought a Saitek X52 Pro Joystick. It´s a fine stick, but I can´t trim correctly with it. Trimming Yaw works just at it should: I release the trimming button, rotate the stick to the center and the position of the yaw control stays exactly where I released the button, but with the stick centered. The Ka 50 doesn’t change the flying path in the process. Trimming pitch and roll is different with this joystick. I´m flying stable, press and release the trim button and put de stick at the center: the position of the controls (Ctrl + Enter) move to and intermediate point between the point where I release the trim and the center, this makes the heli go crazy. If I keep the stick centered and then trim nothing should happen. With this joystick when I do this the controls go forward and stays in the middle from the center to the maximum pitch forward. Pressing and releasing the trim button one or two more times without moving the stick from the center makes the controls stay at the maximum pitch forward. I hope I´ve exposed the problem clear enough. From what I´ve read in the forum I think other users with trimming difficulties with the X52 pro might have this problem. What can be wrong? I first thought it could be related with trimming times. I changed TrimmerTauInverse at FMoptions.lua to 0.5,1,4,11 and 17 and nothing. I then thought it could be a Force Feedback related problem. I changed de Producer file: ForceFeedbackEnabled = false, and deactivated the force of the controls inside the game. Nothing, the trimming problem persists. Any ideas? This simulator is almost not playable without the trim function. Thanks.