Search the Community

hi simmers. i started again playing dcs world on a new highend pc. instaaled everything new. but found out i couldend lift of at first.. search on internet but found nothing .. so looked arround on settings and disabled everything on the VR tab becase i think maybe this is interviring somehow... and yes.. now i can lift off but only when pulled back just slidly pull back the stick, whits didden;t happen when everythin was set on installing dcs word on the VR tab. when in flight and pulled back harder and plain start to be very nerves rolling left and right and hard to fly straight, but no or litthel nose up, only on just al litthe pull back nose goos up slowly... nose down no prolblem .. roll .. no prloblem. joy movement in plain working normal.. all settings have bin deleted and just have hardware setup, no douibles.. only needed, but still the same on every plain i tried.. heli no problem flying joy in windows setting properties al work normal. did not chanbge nothing yet .. all are standard hoop somebody can help ,, thnks in advanced ! pc specs vidwo RTX 4060 TI cpu intel i9 14900k ram kinston 2x 32gb mobo ASrock Z790 RIPTIDE WIFI M2.SSD 980 2 TB PCU SILENCE 1050W

Hi everyone, Would it be possible to change the 'START' time at waypoint 0 for aircraft to be desired takeoff time, for aircraft either starting from cold or hot starting from parking. Right now its function is identical to late activation, triggering 'group activate' at the time specified - which is already easily achieved (though involving a few more steps) via the triggers menu, making it redundant. Personally, it would be better if this time was the desired takeoff time, which would allow us to consider the time required to start-up and taxi (or just taxi for aircraft hot-started from the ramp). Right now, the ETA displayed only considers distance from the previous waypoint and airspeed. Of course, you can 'fix' the time and the ME will calculate the ground speed required to reach the waypoint, but if I factor in the start-up and takeoff time, it may set the speed outside of whatever the valid range is for whatever aircraft. This doesn't seem to be an issue (the ME doesn't flag an error, though it will draw a red border around the time and speed) though in aircraft like the Viggen, which has an automatically generated kneeboard containing the list of waypoints and waypoint parameters, you'll see an incorrectly calculated speed, which will conflict with HUD indications, which is obviously undesireable. This would also allow us to better define TOS directly from the mission editor, and use that to inform aircraft settings (this more applies to DTC improvements, but right now the Viggen will use the time set in the mission editor for TOS, though the problem is that it doesn't consider the time required to startup and takeoff, which leads to the above problem). This would also allow us to define a schedule for ATC to follow, which when/if it's improved should then manage aircraft such that they takeoff at the desired time (or as near to). Ideally AI aircraft would spawn at mission start (unless late activation is desired), then start-up (which should take a realistic time) at a time such that they will takeoff at (or as close to) the desired takeoff time.

I have an AI aircraft waiting on the runway, ready to take off. However, it should wait until a unit is in its zone before it's allowed to actually take off. Is there something in the Advanced Waypoint Options to do this? I could delay its take off time, but there's no real way of knowing when the unit will arrive. Failing any other options, I guess I could do the ol' switcharoo and get rid of the first plane that's waiting and spawn a new one when the unit is in the zone.

This is episode 3 of my new Short Funny Moments & Stupidity series. Haven't shared EP02 as I'm not litterally going to spam the forum with all episodes, so just find the others yourself