Sukhoi2020

Ok, thanks. Let me ask you another question: if DP is destination point (for Red) and I select 'landing', why can I not see the final stretch in my mission as an approach with glide scope? I have created a basic 4-waypoint route, with DP = waypoint 4 (landing). I am still going thru the DCS Manual, but wouldn't selecting a DP as 'landing' create a final approach with glide scope? Or not? What am I missing? thank you.

Are the waypoints set during mission creation supposed to be visible as one flies that mission and hits "F10"? Once in flight, the only way to be able to view those set points seems to be to stop / quit the mission and go back to the editor. Weird but maybe that's how the application works? Also, why are my starting points on a runway designated as "SP" and as "DP", instead of "0" and "4" ("4" for example being the landing point)? Every tutorial I see has "0" -> "a number", so I am not sure if "SP" and "DP" are meant for something else and maybe I am selecting something erroneously in mission creation. Thanks to whomever may be able to assist!

Hi Rocky49. This won't help, but I am also experiencing the same issue w/the editor. I am fairly new to DCS and am starting to get acquainted with the mission editor. I watched a bunch of videos on youtube on setting up missions and I also do not see my waypoints as I fly my own mission. I thought I was doing something wrong (and maybe I am). Did you find out what the answer is? I am 'scavenging' this forum for any post related to the mission editor in the hope that I can find out what I am doing wrong. Cheers

I have been trying to start a basic mission using the Navada map by creating 4 / 5 basic waypoints. I place my aircraft on the runway as "takeoff" and when I add my first waypoint, the location where the aircraft is taking off is automatically designated as SP. What does "SP" mean? Does it stand for "Starting Point"? In many tutorials I have watched, there is no "SP", but a "0" as the starting point. Also, the last point always comes up as DP > Destination Point? (I am just guessing here). And if "DP" = Destination Point, the editor won't allow me to qualify it as a "landing" point, so I am not sure I am closing the loop on a complete linear mission. Also, when I fly my mission to test it, after I reach my waypoint 1, the editor seems to take me back to the SP point, instead of switching to waypoint 2 automatically. Why? Finally, is there a tutorial, or some kind of text that explains how to input the conditions mentioned in the CDS Manual for a more immersive experience? I am not familiar with the script language, not sure how to enjoy that part of the editor without any clear guidance. Hope someone can help - thanks.

@randome TOTEN > Thank you for the tip. I corrected with some slight steering to the right and it worked. Also, I noticed that using one and not degrees of flaps helps. @PoorOldSpike > This is not a mission, rather an Instant Action event (I had that wrong in my question) but I agree with you there! Thanks guys! :) I love this game and this plane :)

Hi, Whenever I select Training in the Nevada module and do a 'cold' start with the Su 25-T, the plane starts sliding allover the runway during take-off as soon as I reach a certain speed (below the roll speed). It feels like the runway tilts to one side; rudder input is useless. I reset my joystick, re-entered all axes inputs and added curvatures and reasonable dead zones. I tried a mission earlier today and I did not experience the same pronounced skidding before take-off. I use a Thrustmaster joystick T16000M, with no rudder pedals. I am not sure the issue is the joystick. The plane starts on a straight line and, with no input from me, starts sliding allover the runway until it's practically out of control. Taking off is really challenging like that. I use the same joystick with X-Plane and MSFS2020, where I don't experience such issues. Was that particular model and / or module designed with a defect during take-off? Why is this happening?? Thanks for any feedback or suggestion!