Rex

Every time I restart a mission, the surface looks like it's 100% water, and it stays this way for several minutes. The first time I launched it today, everything looked like water for 12 minutes into the mission until it finally loaded. Now it's down to 3-5 minutes, but that's much longer than it used to be, and everytime I hit F2 to view another plane, it takes the scenery awhile to load for that view, anywhere from 2 seconds to 2 minutes). This is Normandy 2.0. Is this a known issue?

You can debate all you want how I use my free time and how "worthwhile" (to whom?) it is, but then again, if you're averse to wasting time, you may not want to. Why? Because regardless of how your debate turns out, you'll still have no say in the matter. If you enjoy DCS on any level, then you should thank the tweakers, because your experience would be far inferior to what it is today without them. If you disagree, and if the way I spend my free time makes you not want to use VR, then don't use VR. It's not for you. It's not difficult by any means, but it does require a level of commitment not so easily dissuaded, and it doesn't sound like you have it. I think you've made the right choice sticking with 2D. You can thank the tweakers for making that clear, and for saving you that effort. See, the system works.

Holy crap, it was released today! Saint Omer and Longuenesse are in Pas de Calais! We've getting damn-near the entire coast ... certainly the most relevant parts. Now you can have your Patton unit head-fake Calais while landing the troops 100 miles to the west. OMG, this map just gets better and better! This is awesome, thank you!

I love the drawing feature, but there's something about it that's driving me crazy ... it seems to have the wrong object focus much of the time. There are so many examples, but allow me to define a simple one: You copy a text box, paste it elsewhere, and then start clicking the 'Angle' arrows to change the angle. Except nothing is happening. You keep clicking it with nothing happening, until you realize that the box is actual changing the angle back on the object you copied FROM. I'm often typing text in the wrong box, or manipulating the wrong drawing element because of this. I don't know if the app is goofed up, or if the way I work is goofed up. Maybe both. Has anyone else experienced this?

I stick a couple of Sigfried Line objects on each runway that I don't want to be in the game. Then nobody uses it. Not a perfect solution, but it does the job. I probably spend half my waking life in the real world, and the other half in Normandy 2. Normandy one was great, but V2 knocked it out of the park. That said, it's a map that's not just modeled for location, but for a very specific time as well. That time appears to be just about June 30, 1944. I set most of my missions on that exact day. You can make other dates work, but you definitely have to get a little creative. If you stick things on the runway, the AI will more or less ignore that airfield. I also set the off-date fields to neutral, drain their warehouses of supplies, and sometimes stick a grazing cow or two in there for good measure. These measures do a pretty good job of nullifying the fields.

Yes, now that you mention it I do have to press it twice! I'll try the resolution switch and see where that gets me. In the meantime, I've been using OpenXRTools to get the framerate, and that seems to work pretty well. Not as well as the DCS box that shows which component (CPU or GPU) is the bottleneck, but helpful nonetheless. Thanks for the ideas! Much appreciated.

Hmmm, I used to get FPS that way, but not anymore. I don't remember playing with the size, but I did move it down to the bottom left. i wouldn't rule it out, though, I adjust a lot of things. I wonder if there's a way to reset it?

I used to be able to get a framerate counter in VR, but now when I push the key combination, I get a box with some other stats, but not framerate. Does anyone know how to get it back? I have an HP Reverb 2 and I'm not using Steam(ing pile). Thanks.

One other thing, on some missions, I have the ME call an update() function on every cycle (roughly every second), so if an error occurs in that function, or from a function called by update, it results in "box lock", where you press "Okay", only to have the next box appear almost immediately thereafter. You have to switch back and press 'Esc' in under a second, which can be a little easier said than done, and not very conducive to debugging. So I'm very happy that they allow us to turn it off.

Cool, thanks! Oh, and BTW, I monitor the errors very closely. I mount my DCS drive from a Mac and run a `tail -f $DCS_ERROR_LOG` either straight or with `| grep 'error'` (or whatever) as it's running. I see the exact same errors that the popups show, only with color-coding and way better formatting. Getting them from the log also doesn't stop witchcraft command execution, allowing me to retrieve real-time state via Witchcraft, and even test corrections in realtime. I also have all of my script directories loaded up in IntellIJ with the Lua plugin. I add things like Mist in as external libraries, allowing me to get code completion while being able to following codepaths through the various libs. I'm not saying it was simple or intuitive, but over the last several months I've created a DCS development environment that functions more or less like a dev environment for any other language. The main difference, of course, being that the code can't be run from the IDE, you actually need to fire up a simulator on a different os, on a different machine to see it.

nvm I got it function disableErrorBox() env.setErrorMessageBoxEnabled(false) end

For the last month, I had a very productive script-writing stretch. I was using Witchcraft and some other tools to debug my sessions while they were running, and I was monitoring errors via a tail via the DCS log. Well, I updated to the latest version, and now DCS is back to stopping the sim every time and error is encountered, and popping up the box with the big red "X". To say that it's beyond obnoxious would be an understatement, not to mention, terribly counter-prroductive. It also renders witchcraft basically useless, and command from witchcraft will not run when a box is popped up. Can someone please tell me how to turn these things back off? Thank you.

Oh wow, it went into service after D-Day ... it was a pretty short-lived field in German hands. Thanks!

Despite looking everywhere I know to look (which is admittedly not all that far), I've been unable to find much of anything about the Ronai airfield. After Carpiquet and Lessay, it looks like the next-closest German airfield (at least I assume it was German at first) to the Allied beachheads. Does anyone know about it? If so, can you give me a quick education about it? Thanks.

Thank you!

I know how to do it from the ME, but from Lua, how do I clear the text box in the upper right? Similar to a os.system('clear') in Python?

7 knots in the mission settings, but I'm not sure what it actually is at that spot. This behavior has happened so far on every field I've tried, which is Carpiqet, Criel, and Saint Andre. I think the one in the picture is Triqueville. I've played around with the wind settings, and so far, AI has always taken off with the wind. It's always been a Kurfurst or Spit, though, so it may be plane specific. I also have a lot of scripting stuff running in the background. I have some default mission stuff that sources Mist, Moose, MSF, and WeatherMark. Not sure if that would make a difference. In the tests, though, I'm just placing the aircraft with the ME, giving them a CAP route, and doing a 'Takeoff from Runway'.

I just realized that the AI always takes off with the wind instead of against it. Minor thing but I thought I'd mention it. null

I see he likes to mark his maps up too. I cram so much into mine they're barely readable. For instance, I have most of the Widerstandsnests marked, and details about each airfield, RADAR stations, Pegasus Bridge, and things like the location of Rommel's strafing, aircraft turning radii and max speed altitudes, as well as the battle lines for everything post-June 6th. I have to zoom way in to read most of it. When ED released the drawing tool, they murdered a lot of my free time. They did such an awesome job with this map that it's been a real pleasure to explore.

Awesome! I really like it. Thank you!

I do have the "Save Password" box checked. Since I'm the only person who uses this machine, it's always been checked. I'm getting the invalid username/password right now, even as we speak, and I can't access any part of DCS (Except the forums), but I know why. I remember being to access my modules locally before when the server was down, but apparently this is no longer the case. At least not for me.

Thanks for the heads-up! I'll be better prepared this time.

I'm back in now, thank you for your help. got it. thanks!

"Please note, we are upgrading our database and our services will be temporarily unavailable from 4:00 to 6:00 UTC on the 28th of August, 2023." Yeah, I understood that, my question related to whether it was anticipated, was getting punted from a local ME session. I didn't know if that was anticipated because it's not happened to me for any previous server maintanance.