Spectrum Legacy

Not sure if it was reported already or not, but found some spare ejection-handle stickers hovering in the rear pit a while ago: Also sorry to the OP, didn't want to start a new thread about it. Cheers guys!

Try the gamecache integrity check first (might take a while if you are not using ssd) and then run the DCS executable directly, which should be located in ../Steam/SteamApps/common/DCSWorld/bin/DCS.exe By the way, Openbeta 1.5 branch works without Steam itself running, at least now (i.e. there is no additional drm applied it seems). It helps to save resources indeed to leave steam shut off, mostly in my case about +0,5gb of free ram and less cpu usage. Best results obtained after fresh reboot and not touching steam at all.

Resource-wise, I find modules directly from Eagle Dynamics to have the best optimization out of the box since day1, both from cockpit and viewed externally as well. From helos I can compare only the Huey vs Su25T and the Huey is more demanding both on cpu and gpu in this case. 3rd party modules sometimes are more resource heavy at beta release (mig21 1year ago with not working lods and higher polygon count in the pit comes to mind), but that is usually addressed with patches promptly. On the side note, not all integrated cards are rubbish, but they naturally offer worse experience compared to dedicated cards, especially they can't push silky smooth stable fps on higher settings nor any heavy postprocessing effects / AA. Surprisingly I can play dcs 1.5 on my desktop htpc though, which features integrated R7, albeit overclocked (comparable with R7 250) on mid settings (high textures, high visibility range, no AA native 1080p, low shadows, ground clutters/trees at low range) ~30fps in battle low at deck, ~45 at medium altitudes, 100+ in the space:) Stuttering can be an issue though. That being said, getting a decent dedicated Gpu and quad core Cpu with reasonable single thread performance is way to go for smooth DCSimming.

Who mentioned the Draken?! Now I ought to take my medication, else I won't sleep tonight.

Only used the chute like 5 or 6x in 1.5.0 but no issues so far. Lifted the guard and pressed the button with mouseclick and key-shortcut, both methods worked each time right away. Chute disappeared from the periscope view without problem. Might be issue with your installation, system or certain livery or mission. On a side note, I have no mods, addons, custom liveries / cockpits or whatsoever installed, just stock plain auto-updated openbeta build (via steam). If you want me to try something specific, let me know.

Move individual *.miz files from each subfolder into the root "Training" mission folder and add the lessons.lua provided by the Cobra. In the end you should end up with ...DCSWorld/Mods/aircraft/Mig-21BIS/Missions/EN/Training/ folder, which contains all 15 miz files (all 15 original missions) and 1 lessons.lua file. Hope it helps. Here is the content for the training folder [ATTACH]122390[/ATTACH]

I too would love to see more of the (for me ideally one of the Czechoslovak) liveries added. Maybe it will come at later date, remember not all liveries made it into the first beta version as of yet. Wish I could help to skin it, but I'm terrible at drawing since the very earliest age. :doh:

http://forums.eagle.ru/showpost.php?p=2493627&postcount=2

Edit: Solved by fresh uninstall and clean reinstall of vcredist 2013 (repair didn't work). Thanks for pointing it out! Same Msvcr120.dll error. I've figured it is vcredist, but running after every one of them to force repair didn't solve the error, so I copied the file from syswow64 into system32 (because the game looks there for the file for some reason). That error disappeared and new appeared: "The application was unable to start correctly (0xc000007b). Click OK to close the application. " I guess it is just mine system and some other dll or more likely path to it is misplaced. Will try to figure things out, or do clean install of standalone, as verifying the cache on steam didn't help. Cheers!

Same, just finished download myself via Steam! Going to check it out... Thanks a lot team! :)

1:30 AM here, time for the power-nap then :D Take it easy guys, we will get there!

Steam beta build (according to SteamDB) went through update 10minutes ago, but it is not live yet for the end-users. It means that it is just a matter of minutes now if all goes well... Thanks a bunch to the whole sleep-deprived team! I salute the grandeur of your enterprise :)

Sweet dreams are made of Draken!

If I understand it correctly, it gives you some manual control over your engine, cutting out hydraulic operated engine control unit, thus overriding the automation. I reckon it was used when the MBG unit got damaged and malfunctioned. In that case the handle is pulled which should recover or provide more direct control (manual system is some kind of backup in this case - i.e. the emergency system), which should help you more to save the plane and RTB. I don't really know whether it provides at some point more performance over the automatic default mode, though at lower and up to 2/3 throttle settings, the engine runs on noticeably higher ata (maybe it is just less efficient). That comes with faster heat build-up and naturally higher powerplant stress.

Of course, experienced opponent won't follow you, but rather perform high yoyo for example. That wasn't the point of this thread however, but OP states a question whether it is possible to do it in DCS or not. Doable as a manoeuvre, not viable everyday "gimmick" or the way how to fight in Dora. Maybe just one of the last resort attempts to turn the tables or cause confusion (who would otherwise willingly bleed the rest of their energy and enter the half or full spin, if not as the last hope move?). I understand that after year spent in virtual dogfights it is hard to look at things from the outside sometimes. Though I know I've tried to.

Most prop planes will roll-over or snap when you pull the stick fast and kick full rudder, e.g. BF109 would do it as well. Dora in DCS is no exception, however the snap is not as violent as for example radial Anton should give, but it sill happens pretty fast, but more predictably / or feels more under control. As the usability of said manoeuvre, say in combat, it allows you to get much faster into split-S that way than by roll-rate alone (granted you can cancel out the snap-roll effectively) or enter the spin otherwise (which again can confuse closing pursuer, who might not have enough time to get an aim on you). Spins however often confuse me more than the by-flyers, I admit :smilewink: I imagine that which snap is faster, either clockwise or counterclockwise would be determined by rpm of the propeller, though it wouldn't be nearly as obvious as on the Anton, in my opinion (as I'm not the expert on aerodynamics here). Will have to give it a try though!

I knew there is something going on with the current, since the lights starts to flicker or fade rather quickly and get brighter once I increased the RPM (though very nicely modelled generator, just like on the vintage bikes/cars). First I suspected combat damage to the generator and/or battery freezing in higher altitude, but now I just wonder whether there is some problem with it like it is not recharging the battery properly, or simply battery runs out fast in the Dora and it is supposed to be like this without much left to do to prevent it. That should lead to various systems not operating properly if the minimum current is not met, radio set being quite demanding (along with external lights and undercarriage/flaps motors). However I haven't experienced problems with the radio myself so far as long as the frequencies are correctly set in the mission editor, while using the push-to-talk button (I've re-bound it back to "\" for convenience).

Really good show, the Arcade Cascadeur in me likes it very much! :megalol:

Thanks for the patch LN, you guys never fail to impress. Can't wait for the release now! About rearm bug in 1.2.10, it is really something to look into, as I still have to pick fresh plane (i.e. spawn reset) after I land and taxi to the parking. What I noticed is that pylon adaptors have rather big impact on FM too, so after I shoot Groms or S24s, I always jettison those pylon adaptors, otherwise plane behaves very much like it was still loaded. If the jettison isn't working (you can hear the jettisoning sounds repeatedly as long as you hold down the button), select appropriate pylons on weapon selector as if you wanted to fire those weapons again and then push jettison button. It should work. Note: All above is 1.2.10 info, as I haven't tried beta yet. Cheers!

Of all the options F-104 would be great, although rather specialized plane. F-5 not bad option either, greater scale of use in DCS I think. Or the gracious P-38 (preferably L version equipped with aileron boosters & airbrake, unlike compressibility-plagued earlier versions). One can only wish...

Regarding Awacs, default radio channel is 00 in most all missions I flew so far (sp and mp). Open radio comm, selects Awacs F7 and then F4 (request bogey dope). Edit: Also for quick conversion between km/miles and ft/m, you can check the reference sheet just under the ASP glass - at least I found it helpful during combat at first, until the unit conversion provided by Awacs becomes second nature. About the "boom and aircraft shake", I experience it exclusively when taking off with SPRD-99 RATO pods. I jettison them right after retracting my LG, but as the airspeed rises, so does the whistling noise of drag (can be heard best from external view, looking from the front of AC to the back), until it reaches the point of boom&shake. After that the noise is gone. I suspect that when we drop the pods, only their 3D visual model is being dropped, while the drag/weight remains on our plane until we exceed max.airspeed or Gs, when even their "code" breaks off. That's my assumption based on experience with the pods so far.

I thought that both white light & red floodlights, along with launch authorisation lights (both radar and two IR lights) are related and were not yet implemented as they require dx11. I've never seen them work myself, so I got that assumption... but I haven't seen any user tutorials or vids on yt regarding this module, so can't compare. Radar lock green light and red break-off lights are working for me though. It might be an issue of gpu and/or graphics drivers then, since some users can see launch authorisation lights, while others can't.

To each their own. I prefer early jets, up to the cold war era at most (1st to 3rd gen jets in general). As I said not long ago, I hope Leatherneck won't ever resort to "game balance" ways because of the other modules are able to do this or that (especially FC). If they ever decide to put LCD into their 21, I hope it will be completely optional, not affecting the original Bis version in any way (or completely standalone product). I like the raw beast, with issues being fixed on it as we fly, I really think it has a grand place in DCS as a hi-fi module even now (considering more of the quality modules set in the same era will be added in the future, I believe, making it even better in the long run). In other words "fight FC3 with FC3", it seems like the same sport indeed, but completely different league.

I would opt for additional command, just like in the case of Flaps. You can either bind each of the 3 buttons to your joystick, or use more streamlined version of Flaps-up and Flaps-down to e.g. your keyboard if you wish. Same could apply in the case of Airbrake, adding third optional on/off toggle command for users without simpit and/or free joystick/quadrant bind left would make both parties happy. Since it is only one button, I see it less as simplification and more streamlining or possibility of choice. Thanks!

If the problem is in SP mission, just hop into mission editor before flying, click on your airplane, select the radio tab where all the frequencies are, (not sure whether you have to change something and revert it back right away or not at all) save the mission and fly. The radio should work in that particular mission. I think the problem is somewhere between dcs mission file and module itself, not being able to tune in to those frequencies. In MP, it either works or it doesn't, depending on the server. I have no info whether you can do something about it, for I believe only admin can edit the mission and "update" the radio channels for each spawn. Indeed it is a bit annoying, but I have hope that in next patch it will get sorted, or people hosting the servers will become more aware of it at least.