kazereal

Without ASM code, you'll might need to return values to DCS from FM like this: https://github.com/ipr/F-16Demo/blob/master/FlightModel/F_16Demo.cpp#L834 Likely some way to do those in lua too but I could never figure out those properly.

Have you tried 38 ? I can't remember exactly now, been a while since touching that code. https://github.com/ipr/F-16Demo/blob/master/FlightModel/F_16Demo.cpp#L780

Computer software will always have more or less glitches. Just learn to ignore it, that is very small glitch.

Or that work required would be enormous for a minor visual glitch. Or that it needs work that would be obsolete at one point. Or there are more immediate concerns to solve for any reason. There are numerous reasons why a bug is not reacted to, often simply it is about prioritizing developer time. Just because you have it as a pet does not mean everyone cares about it same way, end-users don't see the ton of things happening "behind the scenes", so to speak.

Early access usually means stuff like that is not ready and therefore not available, it being early and so forth, you know.. :music_whistling:

Except ED usually calls those "pre-sell" to add to the confusion.. Either way, I'll wait the usual friday evening news and update to see what it really will be..

That kind of speculation has many (implausible) ifs and buts in there about revenue, purchasing habits and so on and so on. Much simpler explanation is that it isn't ready yet. Usually the simple explanation is the correct one (at least according to Occam's razor..)

Monitor refresh rate does not matter: it is separate thing from rendering performance. Looking at direction X has some amount of objects and polygons to render, looking at direction Y might have more to render requiring more rendering time -> lower framerate. On something as complex as Nevada (or Vegas, actually) the variations in required rendering performance can be huge depending on location (height) and direction you are looking at. Modern games can do "port-hole" (portal) optimization where you are certain you will never see more than specified amount of geometry. These are database-driven optimizations where you are limited by design what you can see. In a true simulation like DCS you can hop in a helo, move to any position and look at any distance and orientation in any kind of weather and lighting: similar geometry reduction beforehand simply does not work same way. In addition to having level-of-detail objects (reduced complexity objects) in a far distance, games can render far objects in lower resolution which are then combined with higher resolution renders near the player viewpoint. Comparing to games is not appropriate.

C-101 does have second seat as well.

A and C are pilot-only, B and D are dual-seat trainers.

There hasn't been much competition in that market for a long time. Enthusiast-level devices like MFG Crosswind and Slaw device have higher price point and are not sold on every consumer store. So Saitek and CH have been about the only options in the lower-cost market for a long time. If there's no competition quality is poor and price as high as manufacturer will set it..

Sounds interesting, there's definitely room for more alternatives in the market (in my opinion).

Twice the amount of work: twice the people working on it four (!) times as much bugs. Even more when you need to synchronize some functionality between them: when you change one part you always need to verify anything interacting with it does not break. Amount of bugs increases exponentially with amount of code, not linearly.. And it would not really give any benefits at all: better approach is to give different parameters/data to render at different quality than change the code at all. It would be utterly stupid to repeat essentially same rendering code and same algorithms just to have different quality levels.

I do not know if your imagination is correct or not, but 30+ might include both ramp and parking. DCS does not have way to pull helicopters from hangars with a tractor like you might need in RL. Also having engagement of 30+ might include two or more bases at close distance, I'm not that familiar what was actually used.

You are actually asking two very different questions there. Black Sea map airfields are based on airfields at those locations. Get map for Nevada and check those airfields. If your computer can run that size engagement is entirely different matter..

This reminds, there would be useful to have UN skins (and other similar) for various units: ground units especially but helos too. Some have already but not all of them (unless added since I've last looked).

That only works on desktop windows, not on fullscreen applications. Windowed mode and fullscreen mode are handled differently: https://msdn.microsoft.com/en-us/library/windows/desktop/ms632679(v=vs.85).aspx

It is much easier and quicker to make something that passes for FSX which does not demand as much accuracy or functionality of flight model and various systems. So it is a cost thing as part at least.

Just go to options, clear duplicate bindings and bind joystick axis again. Sounds like you haven't done that before?

Much improvement in the new update, thanks! :)

Question is, when can you make the manual. Manual has to describe the aircraft which you can't do until the aircraft is done.. So it is not about willing to release manual before, it is that there is no manual to release before.. Quick-start guide is often included with release so that could be useful, just don't expect full flight manual before the actual aircraft..

When posting about problems like these, first remove the mods and disable extra programs like MSI AB: these can cause problems, sometimes conflicting with other pieces of code and causing the problems. Also it will help developers to find and fix problems if you can show if the problem occurs after eliminating these possibilities.

You can't use it on pre-purchases or already discounted products. New purchases will extend and add to the bonus though. http://www.digitalcombatsimulator.com/en/support/bonus_rules/

There was somewhere a mention about few weeks to squash bugs before hitting beta. That would mean the conversion is pretty far along already and needs to work out things that have all kinds of subtle changes. For example, without sea on the map you can't use all units there, which airfields can be considered "neutral" in mission generation and so on.

Thanks for responding :)