Tango

The L-39 by Virtual Patriots, LLC is missing from the list, and demonstrates why lists like this are a bad idea, because it makes it appear that fewer products are in development than may be the case. Best regards, Tango.

Classic! :D @c0ff: sucks. @sobek: thanks. Best regards, Tango.

* sigh * This is not open for discussion. Best regards, Tango.

Right, but several members of the dev team, and maybe users too, have both 64-bit systems and 32-bit systems, and maybe run the 32-bit version on a laptop when away from home for example. PM sent. Best regards, Tango.

I have asked the Mods to watch this thread and clean out irrelevant posts. @c0ff: not at all. Call it "market research". Best regards, Tango.

PAE has been a part of modern systems for a long time - not just server boards. It allows the system to see more than 4 Gb of total installed memory by using additional address lines (similar to the way the A20 extension line was used on 386 class machines back in the day). http://msdn.microsoft.com/en-gb/library/windows/hardware/gg487503.aspx Maybe, but we can't just dump people still using 32-bit for whatever reason (though I agree you sometimes need to force the issue). Best regards, Tango.

Which version of DCS do you run (32-bit or 64-bit)? If you run both, please select 32-bit. Please note that your answer will directly affect the direction of current and future 3rd party product development for DCS:World.

That's not strictly true. 32-bit apps can address 4 Gb of memory, but it is split 2 Gb/2 Gb between kernel and program. Thus, a program can only use 2 Gb of memory before it complains of being out of memory. You can prove this with applications that don't use tricks to exceed this, and trying to get them to exceed 2 Gb usage. They will either complain of being out of memory or crash (note that you must be running a 32-bit OS in this example). The infamous /3Gb hack on XP changes the ratio of user:kernel memory to 3:1. This offers programs more access to user memory space (up to 3 Gb) but at the expense of restricting the kernel portion to 1 Gb. This may or may not have dire consequences. Best regards, Tango.

Good luck getting data. A lot of ships are more secret than aircraft (subs most of all). Best regards, Tango.

The designation "F-16" etc.. is NOT protected, but to say "Fighting Falcon" *IS*. F-15E is OK, but F-15E "Strike Eagle" is NOT. People need to be careful. A quick e-mail at the start of the project can always help. Best to find out early than day before release. Who knows - you might even get technical assistance if you ask nicely. ;) :) Best regards, Tango.

This is the key to prevention of mast bump. Don't unload the rotor - EVER. :thumbup: I'm seriously looking forward to the Huey - raw seat-of-the-pants rotorcraft flying. The Ka-50 is positively easy to fly by comparison. Best regards, Tango.

w4nt teh see teh c0dez!!11!1111!!!111 * runs away * :D Best regards, Tango.

He's running Win XP 64-bit. SP2 was the last SP for that OS. SP3 is for the 32-bit version. Best regards, Tango.

I run Win 7 and I'm not kidding when I say perf in games is higher than under XP (sad but true :P ). Not sure why it is failing to run on Win XP 64-bit - to my knowledge it is basically the same as Vista/7 sharing 99% of the fuctions but without the bloat. Best regards, Tango.

Get the 64-bit build of DCS. If that doesn't work, install Win 7 x64. Best regards, Tango.

It's called DCS:WORLD for a reason (hint is in the name). Sure, it was originally developed as a combat platform, but aircraft don't have to carry weapons. ;) The base sim is outstanding - we need more scenery (heck - just a global terrain mesh and reasonably accurate water features would be a great start - "the world" already exists, computationally - just needs scenery). Best regards, Tango.

Create two models is my suggestion. SFM obviously works, but the two are incompatible it would seem from your comments. Best regards, Tango.

Another thing about DCS is that to get the most out of it, devs need to announce early what they're working on so duplication is avoided. There are two devs creating an F-15, and regardless of whether they chase the DCS logo, assuming both are high quality, it will be first to market that wins, unless one is EXCEPTIONAL above what has gone before (compared to the A-10C for example). It is great to see such a wide array of aircraft already. Some devs just chase what is popular and what will sell well regardless of whether there are already 4 others like it on the market for example. In the DCS world this would harm DCS overall, as it relies on there being a wide choice of aircraft, and not just American, but British, Russian and Canadian for example. I think it will be a number of years before the true potential of DCS is realized. I certainly hope development (and compatibility!) continues for a long time yet. One problem with 2 year dev targets for a product, release and then forget about it, is that whilst it may make perfect business sense, it makes absolutely no sense for its user base, or longevity, and that IMHO is no way to run anything. Fine if you want to be a fly-by-night, but no good for long term success. Best regards, Tango.

Ahh I see.... might need to be a specific arg then for that to work. Best regards, Tango.

...so your lights don't work AT ALL? Can you be much more specific about the exact problem? Alex confirmed a bug in the lighting - he's fixed it. Best regards, Tango.

[2] = { typename = "collection", -- white strobe upper lights = { {typename = "natostrobelight",connector = "WHITE_TOP",argument_1 = 512,period = 1.0,color = {0.8, 0.8, 1.0}}, } }, NOTE: strobes are bugged! I can get certain combinations of strobe to work fine, but in other cases they strobe together for no apparent reason. The parameter phase_shift works, but in limited cases and I can't see a good reason for the behavior I'm seeing. e.g. {typename = "natostrobelight",connector = "WHITE_BOTTOM",argument_1 = 513,period = 1.0,color = {0.8, 0.8, 1.0},phase_shift = 0.5}, Best regards, Tango.

Epic fail!!!!!!!! So someone's opinion gets it deleted from your drive.... nice. All AV is junk - get rid of it. If you get viruses often, you want to ask yourself what it is you're doing that is causing you to encounter them so often. Best regards, Tango.

Irelevent - there is no HD activity during this period. I never recommend anyone ALT+TAB out when in 3D - there is some issue in DirectX that has existed for years that means 3D apps eventually fail when you switch out to another application. I've seen crashes on multiple different hardware configs, from different manufacturers. The problems started around DX7/DX8 and have never been resolved. Best regards, Tango.

Yes, we're using the EAFM (External Advanced Flight Model) interface, the same as anyone wanting to do their own FM will need to do. As Beaker already stated, beyond the API, NOTHING is done for you; you are starting out tabula rasa. If you're not familiar with APIs, these are merely interfaces to communicate with the sim. They are not used for processing the flight model in any way, beyond giving the most basic data required to make it function (position in quaternion form). Let me put it this way, if we had less than we have now, the EAFM would not work, ever. It is THAT basic. As far as the EAFM is concerned, you are starting not from the beginning, but from the beginning of the beginning. You aren't following instructions on creating one, you're figuring out how to write the instructions, so you can create one. Forget cooking, you have to build the kitchen first. ...ad nauseam. I hope that clarifies on how wide open the EAFM is for developers. Simply put, it is PERFECT. You just need to know what you are doing with mathematics and aerodynamics, and know how to program. Best regards, Tango.

Thanks for the clarification. Best regards, Tango.