Kegetys

You can see at least some of it "live" in windows debug output, ie with DebugView.

Same old repro steps, same old crash: Note someone has added the "CBU dispersal" part to the thread title, it wasn't originally there and the crash this thread is originally about has never been only about CBUs. It can seemingly happen with any explosion/smoke effect as demonstrated by the repro steps which have no CBUs involved at all. I also tried the repro steps with the P51 and Su25T and curiously I could not get it to happen with them even after 200+ new planes, although I think I had the previous version crash the same way while flying a "real" mission with the P51. But given the nature of the crash (uninitialized memory access?) it is likely just a matter of some random memory allocation order that hides it. With the A10 it seems it typically crashes every time after 50-100 new planes in the repro step (and of course at any time during a mission).

If the EDM model format would be documented by ED then anyone could make an EDM exporter for blender (or any other modeler for that matter). Not that it would likely be that hard to figure out the format as is, but having official documentation would make it much easier.

Will it be possible to add new countries, with custom skins and atc/jtac/awacs/etc. speech as mods in the future?

Nice, I just hope nevada with edge will come soon since the old terrain is quite low detail for any kind of ground action in my opinion. No doubt its fun in co-op to designate targets to other players though.

Looks like the same old effects.dll crash is still present in DCS World 1.1.2.1 :( The Effects.dll name is missing from the new crash report but its there in the windows crash dialog: Repro steps remain the same (With A10C, maybe possible with other planes as well): Though now you do not need to even eject to get a new plane, just hitting rshift-rctrl-tab for long enough will repro the crash 100% every time. This way it often happens when around 200 smoke effects have been created: [860] 00330.063 INFO EFFECTS: smoke 206 created at 21.258000 scale 1.000000, pos = {-317882.781250, 18.020000, 635013.312500} But I already also had it happen once when just dropping a CBU-87 at the beginning of a "blank" mission with nothing but my a10c on it. As mentioned in the original A10C thread it can seemingly happen any time there is some smoke created (or dying?). Because of this almost every mission I fly end up with this crash when things start to blow up, with a debugger it looks like there is some uninitialized or released memory accessed so wether it happens or not is likely completely random. I really hope this could finally be looked at and fixed.

For my G25 pedals I physically swapped the wires from the clutch and brake pedal pots (it was very easy), then when using the logitech "combined axis" option it combines the clutch and accelerator instead of brake and accelerator. In racing sims with combined axis disabled it works normally, only the clutch and brake axis names are swapped.

The project has been dead for a long time now, pretty much since DCS A10C came. Since it doesnt use the DCS "system" but instead my own cockpit renderer and switch/mfd/etc. handling it cannot realistically be ported to DCS either. I think it was more like 5% finished at most :) It was a fun project to test how it would work (adding a fully custom cockpit renderer & handling into FC2) but the work required to make everything work is huge.

I get jittering if the background LED brightness is set to anything else than off or full brightness. I recall there were some complaints that this started happening with the latest firmware but TM doesnt seem to care to fix it.

It could be made so that the pilot will not be drawn on a circular area around the mouse cursor. That way you could use the cursor to "see through" the pilot and click switches.

Minor thing, but there's a new line in TheatresOfWar/aliases.cfg: :)

Most likely it was Fighter bomber or Gunship. Still have both ;)

Having at least some improvements would be nice, like to the "snap-to-runway" landings and some smoother transitions when going from one state to another (like when going to stall, where there is a sudden change of ailerons no longer working at all the instant your airspeed drops below a certain value). Some documentation for the community to improve these areas would be welcomed too.

Yes, this is a 2.08 bug with the vertex buffer manage-emulation. The actual fix is the "compatibleVB" setting, just if you enable the quirk mode it will also enable compatibleVB so it fixes it as well (the quirk mode was needed for A10C Beta, it should not be needed for anything anymore unless something else has the same bug). You'll lose some performance with compatibleVB though.

Would be interesting to have these count in your pilot log and multiplayer statistics in DCS :)

Is it a "generic" P51D (as it was in WW2 times) or modeled after some specific current-day P51D? I guess the todays flying ones might have some differences in instruments/radios or such?

F-35 would at least make the cockpit builders life much easier when you just need a ;)

It looks like there may be something wrong with the cookies. I saw a duplicate set of guest ID etc. cookies created, one set was for "www.digitalcombatsimulator.com" and the other for "digitalcombatsimulator.com". By clearing cookies it worked for a while but now there's two of them again. I guess it always works if you try it with a "new" browser. Also after logging out once I got a security certificate warning saying the server name of "digitalcombatsimulator.com" does not match certificates "www.digitalcombatsimulator.com"

With Opera 11.60 it now always shows me as not logged in the 'payments' and 'cart' page, but at the same time ie. on profile page I appear as properly logged in. It worked fine a few days ago.

The mod has been on a hold ever since DCS A10C beta came out as I haven't had much interest to play FC2 after that. And lack of time too.

I'm quite sure I didn't copy anything from FC2, I just recall I tried at least the F-15C and A-10A and they worked with just setting humancockpit = yes (but I could be wrong, I dont remember anymore as it was just a quick test).

In the first A10C beta at least some FC2 stuff was flyable (by setting humancockpit=yes). They did seem to have quite a lot of problems (crashes when using the avionics) but it would suggest that a lot of the required stuff is still usable like the "lo-fi" cockpits and flight models. If so, then a compatiblity patch may not be a huge amount of work, but only ED guys know hard it actually may be.

You do the check to find out whatever you're testing is not broken, and if fails the check you'd ask the ground crew to replace it before taking off. But since simulating all that is probably not practical, just having the check procedure "repair" it would have a similar effect. Mostly it would encourage you to actually do all the proper ground checks as you'd have a real reason to do it, or you could choose not to do it and risk a small chance for failure. I find that just having completely random failures that you cannot influence in any way and that do not happen because of some reason (as they always do in real life, be it a manufacturing defect or some service fault) can be annoying. (Maybe just because I know it was just some pseudo-random number generator that made the fault happen :)) An option to turn such off would be nice at least.

Is this random breakage completely random or is there things that influence it some way? An idea I always liked is that if you skip some in-ground tests then there is a small random chance of a fault in that or related system, but if you do the proper ground check then it will not fail.

I haven't tried A10C multiplayer and only played a limited amount of FC2 multiplayer, but I would like some more focus on co-op multiplayer capability. Ability to have better briefings (in FC2 only one briefing picture works for example) and better planning & loadout settings. Being able to disable respawning would be nice as well to help resist the temptation to just get a new plane when you die ;) Something I did notice in the mission editor that you can now assign multiple planes on the same flight as clients. This is nice already as you dont need to duplicate the waypoints and triggers for every player (assuming it works :)).