0xDEADBEEF

Also in dogfight, corner speed is key. Afaik with the M2k its around 450KIAS depending on your loading. If anyone has more precise values I'd be happy to hear them :)

Well thats what I'm doing. Mission Editor and Multiplayer session. Write-access error. Or am I missing your point?

ahh ok, so this also implies that the technique to reduce load-times by just reloading a mission file in multiplayer in a second instance that I've read in one of the beginner-threads is no longer working? weird, i searched for DictKey but didnt get a result neither in google nor the forum search ...

Hi guys! I'm in the process of getting to know the ME. I'm starting with scripting (I have a coding background from 10 years ago, also lua), added MIST to my Mission, but didnt do anything with it instead of loading it. Then I've tried to run DCS in a second instance and reload the mission for faster testing. Once the mission was running in the second instance (DCS 1.5 release) I could not save changes in the ME anymore (running 1.5.2 openbeta, same version as release). After closing the running mission I could save again in ME, but, and this is what I completely not understand: *all* waypoints are now renamed to "DictKey_WptName_%number". While I do have a backup of the mission with proper waypoint names. I would really like to understand what happened. I did a search on the Forum for DictKey_Wpt but didnt get any results. So I felt like opening a new thread. Thanks in advance! beef

645 is the number of the function that is called, i dont know where the 3 comes from. the device number is in file called something like cockpitdevices.lua, you add +1 to every number there.

found the file through the notepad++ search function (i made it search the whole folder), its in the clickabledata.lua in the m200s cockpit folder.

Some more goodies, the Engine Start Panel: {down = 3645, up = 3645, cockpit_device_id = 7, value_up=1, value_down=0, name = "Start Button Safety Cover", category = "Engine"}, {down = 3646, up = 3646, cockpit_device_id = 7, value_up=0, value_down=1, name = "Starter Fuel Pump", category = "Engine"}, {down = 3647, up = 3647, cockpit_device_id = 4, value_up=0, value_down=1, name = "Left Fuel Boost Pump", category = "Engine"}, {down = 3648, up = 3648, cockpit_device_id = 4, value_up=0, value_down=1, name = "Right Fuel Boost Pump", category = "Engine"}, {down = 3649, up = 3649, cockpit_device_id = 7, value_up=1, value_down=0, name = "Engine Start Switch", category = "Engine"}, {down = 3650, up = 3650, cockpit_device_id = 7, value_up=0.5, value_down=0, name = "Ventilation Selector Switch", category = "Engine"}, {down = 3467, up = 3467, cockpit_device_id = 7, value_up=0, value_down=1, name = "Engine Shutdown Switch", category = "Engine"},

there you go! I thought it was Device 11, EW_RWR, and added a 1 to that ... thanks!

I solved the airbrakes with a simple double-on toggle: {down = iCommandPlaneAirBrake, up = iCommandPlaneAirBrake, name = _('Toggle Airbrake'), category = _('Systems')}, did anyone get the jammer going? I could not even assign a working button :( button is 606 and cathegory 12

Boom, i need this little push, haha! please let me contribute the jettison safetycover switch up/down capable. You guys made me look up the functions :) {down = 3248, up = 3248, value_up = 1, value_down = 0, cockpit_device_id = 6, name = 'Selective Jettison Safety Cover', category = 'Armament Panel (PCA)'}, this makes this plane a lot more enjoyable :)

slective jettison doesnt seem to work for me?

<3

ohhh would you mind posting these lines of code here? that would be fantastic!!

so good! thank you!

Hi guys. I've been having frequent network problems with the last update. Lots of disconnects, lots of servers not visible. Yes, kind of the usual thing, but it was worse, lots of other report the same. I still wanted to double check my network settings, and found something interesting that happend while upgrading to windows 10. I checked my firewall settings, and it would only let DCS though in private networks. Well, during upgrade my OS, so I found out, all your safed WIFI Networks are put to public! Which my firewall blocked!!! (had the box next to public unchecked) :megalol: While I cannot really imagine this is the cause of my dcs related networking problems (I still have them generally in dcs and only in dcs) because I think either it doesnt work at all (if dcs was blocked by win-firewall to public networks with my wifi set to public) or it has no influence at all. :huh: But anyways, since I saw Newy post something like "check your firewall settings" in the server not visible thread I went check it, found something and thought like hum, maybe I got disconnected because most of the people have fraud settings :smartass: (5 minutes ago i got disconnected with a mig21 in gunsights during a mirage, he lagged away briefly then the game froze, pipper on him :cry:) So - telling everyone to check his firewall settings will work about as good as telling people in mirages to call raygun and/or vID bogeys - not very well. But maybe there is a way to check on launch of DCS if the user has proper firewall settings and if not promt him to change them? Maybe this would solve all the networking problems we have? yes I'm being pathetic right now I'm sorry! At least this post may be a reminder to check Firewall settings :) After all I'd like to apologize for maybe discussing this too emotional. As far as I've heard ED is working on a new netcode and I'm sure that when its finished it will be good and solve these rubberbanding and freezing issues. I'll be patient. You guys have done such fantastic work on creating a flying-world, I'm certain you will connect it properly in the near future.

Ahh that server is sooo much fun! guess it will turn back on, no?

This is awesome Capt! Can't wait till its gone! you think it would be possible to get the beriosa only on an ipad too?

Here's the logs from my last crash. M2 vs. Migs server, less than an hour into the game. Win 10, GT750m w/ 2gb, 16GB RAM, i7, no overclocking. Froze for less than 10s, then crashreport. Logs.rar

Maybe some of the testers knows, whats the exact rules of getting a loss for slot change? Is it when you land damaged? would repairing before changing plane then keep us from getting a loss?

You're right. I apologize for my juvenile rant. I just could not hold myself back after the 5th crash this evening and 10th bandit rubberbanding away from my missiles. Sometimes emotions cook over, and the only reason for that it: it's so much fun to fly online against real others. So even though sometimes the anger cooks over, it's only because I enjoy this sim so much. I sincerely look forward to a time when most bugs are ironed and the new netcode doubles the joy of online gaming. I've sims played offline for years. Ever since I started online I play a lot more and the fun quadrupled. I can only recommend it. Of course you are free to play on or offline ;)

I'm aware that changing slots now counts as a loss as per releasenotes. When reading the releasenotes I was concerned that changing a plane always counts as a loss. I've had 3 occasions so far where I returned from a sortie, landed safely and got a loss after I switched to another plane. If this is a new feature - I don't like it - if it is a bug like I suspect, please investigate :)

Although I've made it a good practice to restart DCS when I change mission or Server, if I don't the Unit Type in the Stats screen would turn into a number instead of a string. Like "01234" instead of "F15" after I load another mission.

Hey ED! Congratz to the release of 1.5! Its a big improvement over 1.2, but theres some small things that I personally think would improve gameplay heaps: - bring the new netcode, please!! End the rubberbanding, the framerate-decreases and the fricken crashes. especially when theres so many people online. Please make this your highest priority. Dynamic campaigns can come after, the netcode is really the gameplaykiller no1 for me. - fix the scripting. Proper scripting would skyrocket user generated content. Please move this up a bit on the priority list (right after the netcode) - improve the chat! The chat really feels like its something that had to be implemented, and it has been done quick'n'dirty. it works, but it really needs some love - fix some of the small bugs, like the Su27 losing the ENR mode after respawn, they've been around for too long. I can't really imagine they are so much work to fix. In general I think DCS-World is in a good shape regarding big features, it might be a good time now to polish out the gameplay-killers in the details. Thank you very much for your hard work, it is very much appreciated! Deadbeef

I'm having frequent crashes on the 104th when it's crowded. I'm always super motivated to go into a fight with so many enemies, but the fun usually ends when I arrive near bullseye with a freeze shortly followed by the crash message. Logs.rar

I don't really get what you are trying to do. If with your radar off, at 6000m the f15s will easily see you on their radar. What I would do is turn on radar and draw a picture for yourself, remember where they fly, which heading and speed. Then dive for some hills and mask. This is the only way not to be seen by F15s. Pop up for short timespans to check if the picture in your head is still valid (if necessary) while maneuvering around the F15s. This way you can pop back up anywhere between their 3-9 line and 6 oclock. Send them an ET when you are in range and they will go down without even noticing whats going on. Keep in mind that by not using your Radar you will not pop up on ther RWR, you will still pop up on your radar (your RWR will warn you about this).