mhe

Since DCS World will integrate everything so far in a single but huge install, I am wondering how much administrative work for the sim enthusiast this will mean in the long run. Updates to the A10 for example did not always go so well, so many people have made it a habit to do a complete reinstall once a new patch is released. Now a World installation is much more complex and a complete reinstall with all modules and having to reconfigure everything (multiple screens, exports, Helios and whatnot) for each module would be a daunting task. So will there be an integrated updated or even Mod Manager, making it easy for us to keep things up to date without having to resort to manual reinstalls whenever a module or even World itself is updated? Considering you could make the update application also into some sort of marketplace for mods and payable content, this might also be an economically smart move? I'm interested in what you guys have to say about that idea... :thumbup:

No problem, I just didn't think it would go as far as keeping up the speculations about things that are more or less proven already. If it is what makes you happy, then go for it. Didn't want to stop you cold in your tracks, not that I could even if I wanted to anyway. So it might be best to chill out a bit as well. :) And yes, if I were to a party where people are speculating about already (almost) proven facts, I'd pull out the fact sheet and end a pointless debate, as facts are facts and thus are set already. Unless you actually meant that phantasizing about alternate possibilites or the next plane after the F-18C, which would be perfectly fine I suppose. ;)

Well, if you put it that way, I think I have lots of bad news for you... :D Didn't mean to rain on anybodies parade, but these speculations actually lead nowhere (apart from a forum full with gossip and speculations, making it harder to find stuff over time). I was kinda wondering when somebody was going to suggest that ED will make an ATC sim because a patchlog featured a nicer model for the tower. ;)

Not this again... haven't we all agreed that it's going to be a F-18C due to ED already having registered the domain F-18c.com? For the people who don't know how to handle a WHOIS client: And before anyone asks: the status "NOT DELEGATED" simply means that there is no authoritative DNS server for that domain yet. But the domain is rightfully registered to ED.

Headspace's tutorial is immensely helpful but I still haven't figured out why the hell he creates a flightplan consisting of markpoints when he could just switch to MARK on the auxiliary avionics panel, slave SPI to steerpoint and just set the markpoints as steerpoints with DMS commands. Much faster than creating a flight plan. But as with every good A/C system - there is usually more than one way to do it...

Thanks a lot, that mission card editor is a godsend! No I don't have to bother ED to make a print function for the mission planner... :D

Gave this a try today and so far it works almost perfect. Only the 1024 grid thing pisses me off. Not that I wouldn't do the calculations right - it turns out the rules stated in the readme only apply to the main viewport defined in the monitor lua. There are several layers to consider: 1. In windows I run Eyefinity 3+1 (6036x1080 + 1920x1080) 2.) in DCS I have the total resolution set (7956x1080) 3.) the 3D viewport covers the the 6036x1080 area and the touchscreen gets the exported gauges and MFCDs. Key is the FOV of the overall screens in the options.lua and the correct FOV of the 3D viewport in the monitor.lua I tried to make the radio menu spawn on the second screen, i.e. outside the 3D viewport. If i set a x-coordinate to 1024 it will spawn on the right edge of the 3D viewport. If I set something higher than 1024 it will not render at all! Funny thing is - once the menu is displayed anywhere, I can drag it with the mouse to the second screen and all is well for that particular session. It's not that much work and can be done during preflight but I'd rather have it spawn in the correct location right away. Does anybody know how to accomplish this?

My wishlist would include Dx10 support to be able to run the sim in crossfire in window mode oooor just implement exporting of all the gauges and screens over the network to another machine. Would be a sweet feature for pit builders. Also unbreaking the Lua facilities for the radios would be nice, mapping keystrokes in Helios just isn't as good as the native support that worked up to 1.1.0.8.

What I still don't get is, that one has to drag something somewhere after starting the sim. If configured correctly, it should start with all the exported screens already where they belong.

What do you mean exactly by "I have nothing left on my main screen".

This problem seems to be a legacy one. I added the touchscreen later when everything was up and running. Changing the resolution was done via editing the options.lua because I run a 3x1 + 1 setup, so the desired resolution doesn't show up in the dropdown in the options menu and I didn't know back then that I could simply type in the resolution. If done via the options menu, the new aspect ratio for the overall sim is automatically recalculated, but not so if the resolution is set via the config files. I didn't change it from the 5.6 I had because I figured this number only affects the 3D portion of the rendering system. Boy was I wrong. The aspect ratio of the 3D view is set in the monitor lua. And if you don't have the right aspect ratio set in the options.lua, all coordinates and size parameters in the monitor definition lua seem to be interpreted wrong. If your overall res is what you stated, the calculated aspect ratio is to be set in the options.lua in your home directory (saved games in your files, DCS folder). In the monitor definition lua, the aspect ratio has to be set accordingly to the 3D output, i.e. you subtract the vertical resolution of your touchscreen from the overall res and do the same calculation again. 7968 - 1920 = 6048 -> 6048 / 1200 = 5.04. So the aspect ratio in your monitor lua for the main viewport has to be 5.04. If done so, all the coordinates and sizes for the indicators will behave correctly and you don't have to position and resize every gauge by tedious trial & error.

Hi there, I think I cracked the problem with the distortion of the exported displays and also the broken coordinates problem. The problem seems to lie in the aspect ratio settings. In the DCS options menu, you must enter the resolution covering all your screens manually. The aspect ratio is automatically calculated and put into your options.lua file in your Windows savegames. When configuring the monitor lua, the main viewport definition should contain the aspect ratio for the 3D view alone. If you put the same aspect ratio as calculated by your main screen into your options.lua, the coordinates of the exported displays and their sizes too will be broken. In my case, I run a bezel-compensated eyefinity screen setup with one touchscreen aligned to the right. Large virtual screen has 6048x1080, so the calculated 3D view aspect ratio is 5.6. Overall sim resolution is set to 7968x1080 (6048x1080 for the main screen and the 1920x1080 touchscreen to the right of that). So for the overall aspect ratio (the one to be set in options.lua) is 7968/1080= 7.377777778 in my case. It's kinda beyond me why the aspect ratio has to be used for this carthesian coordinate calculations, but the devs must know what they're doing.