Leaderboard

Waouawwww Good luck for your project !!!

If you choose the Draken livery under the U.S. and look at the cockpit from the external view, it is of the F1M. Just thought that was kinda neat.

When you say 'nobody' you mean 'yourself' right? Because other people (ED included) have the documents that detail all this stuff.

Please do not make false statements like this, while we have a few areas to tune and add it is mostly accurate. As always, unless you have proof of such claims, please do not make them. Thanks

Not at the moment, I'm putting a lot of hours in it and it's progressing pretty fast though. But still a lot of fixes to do.

New version available: Changelog Version 0.5 - 23 Jul 2022 Added Working FLIR (Star Safire specs) New front panel and instruments 3d model. Version 0.4 - 20 Jul 2022 Added Avoid areas on HSD Contact lines on HSD Flight areas on HSD HSD decluttering ADF, AVD_AREAS, COMM1, COMM2, CNT_LINE, FLT_AREA, IFF, WAYPOINT and VOR data transfer. Changes Renamed the Mission folder to DTC. Download link: https://github.com/luizrenault/a-29b-community/releases/tag/0.5.0b

Hi everyone! I've become tired of editing the default countermeasure programs every time I started the mission. So I've desided to implement a simple editor tool for presets and shared it with friends. While working on the tool i found out there are some quite simmilar tools already exist Neverthless... I think I should share my tool with community. I'll be glad if it will be usefull to you. Your feedback also is highly appreceated same as help with testing the tool. We've verified the tool with several installs on win 10 and win 11, yet there might left some bugs to fix. You may leave your feedback in this thread or on a github. New releases going to be anounced here too. Feel free to suggest new features or share your ideas. This tool is free and will be always free, if you wanna support me - just share this tool with your friends. Download from here: https://github.com/SilverSwift/DCS_CMS_Editor/releases/tag/1.0.0-release Documentation is here: https://silverswift.github.io/guide/

Comparisons are kind of unfair .. I have enjoyed similar content created by a lot of Developers, like the Frenchpack, Airport Services Vehicles, Civilian Assets Pack, and SAM Sites Assets Pack, all of them enhance DCS on significant ways.

Our weather plans are still in progress and we have more features to come, so we still have an element of work in progress here. Can they be improved? for sure and the team are always looking for ways to enhance our effects. I know it requires a lot of patience on your part as we do have long development periods but that allows us to stay in business and profitable, we are not as large as some companies and our team are working as hard and fast as they can. Regarding the clouds, ultra is always going to be the best option for best quality, below that the team have tweaked them so performance is the consideration. My personal opinion is that in ultra with the reverb G2 I dont have any issue, or dont notice the shimmer enough for it to worry my own preference, but I have passed on your feedback, hopefully with the new additions to the clouds in the future it wont be as noticeable for you either. We have some nice cloud structures to come, and I think you will be impressed once they are here. thanks

Hi Felows, A bit stupid to do this when a new DCS Mod is newly out, but I'm glad and proud to announce the very closely coming new free campaign for DCS : L-39 "Free Syria" Campaign V1.01 After years of civil war, the dictator is dead and a new page in the country's history is about to be written. You will step into the shoes of an L-39 pilot who will help the country to get rid of the remaining rebels. What do you need for this campaign ? Syria Map L-39 Albatros Mod Good knowledge of using all weapons. What you get ? Story lined campaign with... ...9 fully voiced missions, never the same, always fun. About 1 hour each to complete. Full documention in briefing AND kneeboard The use of ALL, I say ALL, weapons, but training ones : internal and external guns, LD bombs, HD bombs, illumination bombs, AA missiles, rockets and... flares! Difficulty : Depends on your settings and skills. Basically the L-39 is a trainer. You have few weapons. Thus, in combat, you only have one pass to make. Therefore, the missions are not difficult. BUT... there is no radar, no CCIP mode, no guided bombs. In this case, it depends only on your skill. Then you can make the mission easier by turning all labels on, or harder by turning them off. V1.00 - Initial release V1.01 - Aug, 1st, 2022 - Small trigger adjustments in mission 1 and 5. Cheers Daniel

if you watch lots of ariel refueling videos when the boom is disconnected or the probe detaches from the basket you can always see a little cloud of fuel that sprays out and I think it would be a easy but realistic implementation to the already amazing sim. little clip if your unsure what I'm on about

I think it has some issues dropping targets in A-A. I know we need to post tracks, but that never solves it when many people have problems and then there others who say we use it wrong. Maybe post a poll to see a consensus on how many people are having problems. Not so many of us can be that bad at using the a-a radar. IMHO

Still loving the Mossie but it's been a while since I've heard any updates on the remaining features left on the to do list before the old girl leaves EA, so I thought I'd post a new thread and see if we can get an official update on how things are going. In the newsletters early last year before the Mosquito released it said there would be :- The historical accurate navigation system for WWII aircraft (is this the DF feature on the radio?) Controllable AI navigator and radio operator Any word on how these features are coming along or even if they are still planned? Also is it still planned to have a flare pistol in the cockpit roof which I believe was also planned, and an operational escape hatch also on the cockpit roof? Great to see she is still getting regular additions and bug fixes slotted into recent updates, but a quick update on the remaining items would be appreciated.

While I wouldn't say that it is "completely broken", there are a lot of areas where it is not accurate. Unfortunately, the available documentation is often refused by ED. I can understand that if you have "insider knowledge" of ED's simulation of the APG-73 radar, you might have a good idea of if it is accurate or not according to the developpers, but we don't have access to that information and unfortunately we never got (so far) the radar whitepaper that was discussed some months ago. As such, we have to assume from what we have as users: the available real documentation and the end product we currently use in DCS. Comparing one with the other highlights some significant discrepancies. Some examples: - Jammer/Radar Priority - Waveform selection (should be able to make an STT track appear as if it is guiding an AIM-7 even if it is not) - PVU - Velocity Search - Terrain Avoidance - RWS horizontal slewing - Integration of sources with MSI and the radar, including having a L&S track without radar, getting range source from MSI on an AOT radar track, etc. - Proper trackfile death model that does not rely on the display-only brick age-out setting. Again, I do not condone hyperbolas such as "completely broken", but I personally believe that more than "a few areas to tune" is left to be done on the APG-73 to be "mostly accurate". Hopefully these will be covered and implemented at some point.

See my statement, just because you don't know about the document doesn't mean the person posting and ED don't

He means no harm. He was only trying to show you it can be found if you search long enough. But,the Original A7e model can not be used any longer. There are no permissions. That being said, Some up-dated pics of the cad nav model She is coming along....and getting close.....

A set pitch attitude with a level vsi will result in a set speed. 90 knots is approximately “wings level”, I.e. the horizon line is level with the horizontal lines of the LOS reticle. 40 knots is about 1/4 of the way up the bottom vertical line of the LOS reticle. This equates to approximately 5 degrees nose up. This attitude is important because it is also the attitude of the helicopter sitting on the ground and while it’s at a hover. 70 knots is about 3/4 of the way up the bottom vertical line of the LOS reticle. I can be looking 90 degrees up, left or right, or even have my head rotated and still be able to Any of these attitudes because the horizon line reference is the LOS reticle. This allows me to look anywhere and everywhere and still maintain a constant pitch attitude, this is really important at night, when having to constantly look ahead or up/down to find the horizon line would be insanely disorientating. Long story short, set the pitch attitude and adjust the collective for a level VSI. Pitch is super important for a helicopter because the pitch determines how much thrust is translated to horizontal acceleration.

textures are not complete yet. this is an overview of the finished geometry of the cabin.

I think it's probably a fair bet to say most aren't using the radar correctly, but the radar is also definitely very broken, so it's both. Understandably though, it is hard for people to learn how to use it correctly when the way it works in DCS is pretty "strange" to put it nicely, in addition to some misconceptions in the community that also muddy learning (e.g. "soft" lock) that make it harder. It becomes a circular game of learning how to do it correctly, then learning what is bugged, or incorrectly implemented in DCS, then learning how to get around the bugs or wrong implementations, and then the people who teach others the above have to go through the whole cycle constantly. e.g. The LOST cue in DCS still indicates LOST incorrectly which makes people believe their missile should no longer be supported (this is the right idea for them to have!).

At the very bottom of the page "Language / Theme / Privacy Policy / Contact Us". Click on Theme and you will have your night mode

Kudos to the Aerges team! (And thank you!)

I don't have a solution for the export, but many people use the technique of pointing the HUD pipper at the target before uncaging the Maverick with T1. Then in theory the target is near the crosshair. Do you use VR Zoom and Spyglass zoom keybinds?

I think some people need to hit the books again and refresh themselves on the various flight controls and their effects. Right roll = left aileron down, right spoiler up. Aileron down = increased lift, increased drag. We are turning right, so yaw here is adverse. Spoiler up = increased drag, loss of lift. Drag may be more or less than the opposite control due to various factors (speed, area, deflection, location). Yaw effect may be variable based on location (inboard will have least yaw effect even if very high drag). Just because you lose lift doesn't mean the spoiler is neutral for drag. It is still stuck out in the airflow and has an associated turning moment. The only question is whether the forces ultimately balance out to be noticable or not.

If possible, time permiting,stars aligning, etc.. Could the P-51 please be brought up to the external visual levels like the Spitfire, 190 Anton and P-47? The cockpit is nice, but the external models are painful and really limit creativity in skins. Thanks!

https://www.thingiverse.com/thing:5448295

Currently using the EHSD->DATA->TCN allows you to cycle through presets of TACAN channels for the major airports. This works only for Caucasus, Nevada and PG. Would it be possible to add the missing TACAN presets for the other modern maps? I tested and found there are no presets in: Marianas Syria South Atlantic All TACAN channels can be found here: https://www.digitalcombatsimulator.com/en/files/3312200/ But it would be useful to have it in the presets, especially to keep the Harrier consistent across all maps.

Wow, finally. The hint with the driver was the final game winning goal. Thank you all. Once installed the USB board harware I just installed the official driver from the Inateck Website and it did not work as mentioned. But with your awesome tipp of removing this driver and running it just with the Windows driver. And now it directly detected the headset and I was able to enter DCS and fly with no bluescreen. Had not enough time no to do excessive tests but normally when I switched views or to the map then I often ran into the bluescreen and it made all screen changes now smoothly...... wow, cool, finally removed this bug. Thank you all for your support. Guess now it's time to work through the openxr thread

I don't know ED's plan for fixing this, so I fixed it myself. Updated Canopy bindings are in my tutorial thread: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4691602_menu It includes bindings for 3 pushbuttons (OPEN, HOLD, CLOSE), a 3-positions switch, and for a 2-position switch OPEN/CLOSE.

The LST/NFLR switch has nothing to do with the targeting pod, it's a legacy switch for the AN/ASQ-173 LST or AN/AAR-50 NAVFLIR pods that would've mounted on station 6. Early model AN/AAS-38 Nite Hawk targeting pods had no built-in laser spot tracking capability until the -38B, and required the use of a dedicated LST pod.

Well after getting rid of all mods and a couple of clean ups working again.

Basically: - appCPU = CPU time taken in ms to render the image appGPU = GPU time taken in ms to render the image postCPU = CPU time taken in ms for post processing (sharpening/colours/reprojection/FFR) postGPU = GPU time taken in ms for post processing (sharpening/colours/reprojection/FFR) If appGPU is less than appCPU then you are CPU bound and adjusting graphics options will make little difference to performance. If appGPU is more than appCPU then you are GPU bound and adjusting graphics options will make more difference to performance. When running without reprojection, postGPU is typically <0.5ms, with reprojection this is typically aroun 3-4ms (for my machine). Working on the assumption that you are GPU bound (which is where you want to be) adjust your options to achieve the target frametime that you want, this should give the optimum image quality for the given performance. Everyones VR experience is different so what works for me may not work for you. When running reprojection your fps will always show as whichever refresh target it's running at (1/2, 1/3, 1/4 of refresh rate) but the appGPU frametimes will give a more accurate indication of performance. Calculate you fps by using 1000/frametime, therefore 1000/11ms = 90fps, 1000/16ms = 60 fps, 1000/22ms = 45 fps. When using reprojection you need to, at minimum, achieve the refresh target to keep it enabled, to do so both appGPU and postGPU should be combined and the result compared to the refresh target. For example if you have 17ms appGPU and 3.5ms postGPU your total GPU frametime is 20.5ms; this is less than the 22ms for a 45Hz refresh target so reprojection will stay enabled. With openxr toolkit the reprojection is able to step down to the next fraction of the headset refresh rate, this is 30Hz (and subsequently 22Hz) with a 90Hz headset refresh, this does mean that you can actually tune to achieve the 30Hz refresh target and you can wind the settings up.

We check as many issues as we can when they are reported to us, if we can not reproduce the problem we ask other team members to check to see if they can verify an issue. If being defensive is answering with our own observations then I am sorry you dont like it. As for transparency we post news when we have it to share, the days of old of sharing plans early are gone, to many people become upset and vocal if time lines are stretched or changed. I will pass on your feedback to the team, as I always do even with negative feedback. thank you

you should not mess with config files in game. it is better to set a desired FPS target in your autoexec.cfg in saved games DCS config folder options.graphics.maxfps = 300 I have mine set to 90 personally

Was updated on 2020, check that you are opening the new version instead of the old one, its name is "DCS User Manual EN 2020"

May the Four-th-teen be within you...

Page 86 It says 400-7000m

There has been so many requests for fallon. I hope that we can get a Nevada 2.0 at some point. A paid update would be fine with me. Since the Caucasus update the nevada map now has the oldest ground textures of them all. There is so much potential for expansion on it too.

My first preference is for Viacom to succeed.. Personally I don't see ED picking this up, not at least for a long time. They have more than enough to do already that would be considered higher priority, but then again - they did decide to have a go at radio coms even though we had SRS, so who knows. My personal favorite would be for the developer of VAICOM to release the source code if they're not going to be maintaining it and allow the community to continue it's development, or otherwise have a new mod that is open source / community created.

This is really the kind of thing that will need a hotfix as soon as possible. It is a major problem.

This occurred to me as well ALT2 First then about 30 minutes later Alt1 dies... Engine remained on landed safely. I wonder if its the air temp. I was on the Nevada Map with OAT at 35 degrees Celsius. Ground crew will not repair either. I always have to get a new jet.

I don't think deformable terrain is even needed (and it seems out of scope for dcs in the forseeable future). If we had a selection of texture decals as a base and berms/fortifications as static objects (or checkbox in the unit itself), it would go a long way already. I'm not sure that the decals are possible though. I think the decals we have (craters from weapon impacts f.e.) are perfectly flat and don't follow the terrain. Also z-fighting might become a problem. Probably all solvable with reasonable effort, but i don't know of course... Oh... and the remove trees function should work reliably on all maps. That would also help...

The F1 manual states that TL mode scans from 400m to 6nm and locks on to the first target detected..... its basically a Boresight mode like other aircraft.

https://i.imgur.com/MGT46Qj.png https://i.imgur.com/PJkP5g5.png

with the addition of the JL100 are we also going to be seeing the other variants of the hybrid fuel weapon pylons? I think we can find lots of utility in these, especially the bomb rack variants.

Hello Virpils, Just want to share some useful things about F-14, which are not obvious after reading manual / guides, and could reduce learning time for new players: * Disable Jester auto switch from PD-STT to P-STT (this switch could produce STT lock lost!) * TWS targets filtering - RIO can assign MAND ATTK & NOT ATTK for selected track on TID using CAP also with Data Link enabled you can see 2 HAFU symbols on TID (upper for your own radar and lower for DL) but unfortunately WCS doesn't recognize Friendly targets from DL, so unless Jester or RIO marks a target track as Friendly, even if DL shows it as Friendly, TWS can add this target to priority list for shooting with AIM-54, so with small cluttered TID repeater display in pilot cockpit and in a harry to launch your missiles, you could overlook that a Friendly DL target is still marked as upper Unknown and shoot it! * ACM cover up - AIM-54 is launched active, thus NO tracking TWS & STT targets at long range!!! * TCS slaved to Radar - when TCS is in any AUTO mode, TCS lock will stay on the last locked target, until lock is lost due target leaving TCS gimbal limits or unlocked by RIO using HCU half action in TCS HCU mode, so in order for TCS to always point to the STT locked target - use TCS MANUAL mode (in this mode TCS won't lock a target, but always will point to STT locked target or ADL if no STT lock) * CMS Jester Flare Mode - PILOT: DLC button releases flare, NORMAL: DLC button releases chaff * Climb profile MIL power: just keep 5 units AOA * Climb profile AFB: climb with 0.9 IMN until 30kft, then level and accelerate to 1.4 IMN at 30kft, then climb with 1.4 IMN * Cruise: keep 8.5 units AOA * Radar/Visual FIX on ST (surface target) point will just update its coordinates without any changes to INS * Radar in Pulse Search mode can be used for ground mapping and looking for ships

Why did you purchased a 70’s aircraft instead of an F-16 or F-18 ? … what were you expecting?

In my experience, people, especially the ones who derive enjoyment out of imaginary street cred the delude themselves with by "mastering" old, non FBW fighters that are rumored to be difficult to handle care very little about how the actual aircraft functions in real life. There's this trend in flight simming (which is likely the result of the simplistic modelling of very old sims) that difficult is more realistic. So if the aircraft is bobbing and weaving all over the sky it's surely going to be more realistic than a well mannered aircraft because the real aircraft must be difficult to fly, even if this doesn't reflect real behaviour.

WIP items of the Mirage F1 CE: Autopilot: o Implementation of R and G modes. o Fixing oscillations in some regimes. o Mode logic, failures and tests overhaul. Implementation of S530 F ‘supermatra’. o The S530 D used as a placeholder in some AI models will be replaced by the F variant. Full implementation of the intercom (will enable communication with JTAC). Adjust adverse yaw behaviour. Pedal toebrake and control stick animations will be added. Implementation of miscellaneous armament: o CC - 420 external cannons. o JL100. o Etc… Implementation of countermeasures and jamming pods: o BARAX. o PHIMAT. Radar: o BZ short range mode. o Different detection ranges and target visibility conditions in IC and HA modes. o Radar noise visual appearance in various modes. o Elevation control in V1 mode for 7 and 15 nm ranges. o Radar slaving of the IR missiles’ seekers. Optical Sight: o Radar related symbology logic - relative velocity, range, correct display sequence with the radar tracking a target. o Gun sight is not correctly fed by the radar measured target distance yet. RWR: o Addition of specific F1 RWR sounds. New pilot 3D model with new helmet, 3 variants. Improved external model textures. Cockpit panels texture overhaul (dark cockpit) due to game lighting. Option to adjust the speed of the fuel selection dial. The Flight Manual has to be completed. New missions will be added over time. Main known issues of the Mirage F1 CE: Wrong number of flares at mission start (14 instead of 15). Jettison of CLB4 bombs when infinite munitions are on does not stop bombs from respawning. R530 jettison should eject the pylon too. Clickable sounds for the shock-cones and high sensitivity nose wheel steering not audible. Control stick switches sounds not playing. First preset radio channel is tied in both radios in ME. Some liveries are inaccurate. AI flight model is underperforming. We are aware of other issues that we will solve over time.

Considering the plans I have for the Campaign right now, the mods will prob be the least disliked part of the project Either way, I even have a story plotted out. Writing it all down so I can start work once the asset pack is released. EDIT: aaaand now we get actual Sweden in a map. Will version 2.0 of the Asset Pack contain Cold War Units or will you just beg ED for your assets to be included from the get go? XD

Ugh....I hope that's not what it looks like because it looks frankly....pretty terrible....