aw33com

Some progress. I was able to make a flyable aircraft using someone else's EDMs (cockpit and external). I setup as much as I knew, plus I setup all graphics and sounds in DCS. So far so good. I even plugged in SU-25T cockpit in it for fun as well and flew with SU-57 flight model :) It seems I have a good grasp of how the environment works and I can work now. Now the question to you is this. What is next? I'm assuming external modeling of Su-17. This is where the steps are going to start for me. I have never done any kind of modeling. It does not scar me, but I just don't want to go in the wrong direction. Hence my questions to you: 1. If I need to build an external model now, what are the steps in doing so? I have all the software. 2. Is there an external model somewhere already? 3. How do I get the proportions and all the details? Do I scan/copy it somehow of pictures/documents? 4. What is the best way to develop the model? Should I build 1 part or build it in components in 3d Max and somehow marry the parts at the end? 5. Anything special I need for the development of the model besides 3d Max, ModelViewer, EDM plugin? Any help would be appreciated to start me off. I'll figure out the rest.

I read his post and he says there is no interest in the project. Not sure what that means. No interest by clients to fly it? If there is like few months of work left and Fragger could help me (explain stuff in English that is) along the way, maybe I could take it over. But only if the community is interested in it. It would be a nice start for me before I go after SU-17.

Fill me in on the Bo-105. Why is it dead? I'm not a good system/FM coder. I don't know anything about it. I used to build complicated software in the past, so from software point of you it's not hard for me, but I have never done any Flight Models, 3D, or anything like that. Trying to do it.

Update: So I did some small research and I was able to setup my dev environment: 3Ds Max 2016 Photoshop 2015 Blender Model Viewer GIMP Visual Studio My initial poking around tells me this is doable, but it will require a proof of concept. I need to be able to setup a simple module and make it flyable. Got to be able to go through the entire process from research, design to production. Then I will know for sure if I can do this correctly and how long it will take. My worry is the time it takes and lack of documentation. I will have to reverse engineer a lot of things, which will be slow. Last 2 days I started looking at the DCS structure, code, other people's work and modules. I designed my livery and looked at the code of MIG29A. Even skins were giving me hard time as some undocumented things made me debug stuff for hours what should take a minute max. But so far I'm positive. Will do more research and do a proof of concept. And those that like MIG29 here is the Polish Squadron skin I just made. It looks like the one in real life.

Today I started a research to see if I can produce full fidelity Su-17M4 [s-54, "Fitter-K"] as SU-22M4 (S-54K) export version (Circa 1983-1990). Pure love for the aircraft, and lack of RED full fidelity ground pounders made me want to produce this module. The selling point of the module would be to recreate realistic feel of the aircraft so it handles like the real SU-17 in your hands. The goal of the initial project is to: figure out IF I CAN produce it. What I know, or can do as of right now: 0. This aircraft has and would have tons of love from you guys. 1. I was a software architect and engineer developing trading software for banks. I have coded in most languages (except C++), and I have a very simple but practical view of software. Software dev no matter what languages/framework would not be an issue. 2. Tons of DCS experience and good understanding of what the flight model should feel like. This is maybe the most important thing in the project, because a module that flies correct is very rewarding. 3. I have time, and I'm not budget restrained, as most development would be done by me. 4. Chances are this module would not be fully commercialized, but rather build with/by community. I would want this module to cost only enough to cover the costs. Not interested in making money. 5. Access to SU-22 pilots (possible access to the aircraft). Not sure if I can legally use that. What I don't know: 1. The documentation of SU-17 is not really public. Some things would have to be improvised, or copied from SU-25T, or other sources. 2. Lack of any kind of 3D modeling experience. 3. Not sure if DCS would allow me to use the module in the SIM. In case I would not be allowed to use it, I would still develop it for myself. 4. Development process of a DCS module. [This is probably easy to research] 5. Legal implications/approvals from Russian Federation if any. What the module would be like: 1. The flight module would be very close to RAZBAM modules. As much as I hate their quirky bugs and behavior, I truly adore flying their aircrafts. They seem the closest to reality for me. 2. The module would include Air to Air, Air to Surface, Anti Radiation, laser guided, electro-optical munition, TV guided bombs, laser guided bombs, standard bombs, and pods. 3. Possible the module would start as a FC3 type of airplane and work it's way into full fidelity. Let me know what you guys think, and if you have any ideas on how to produce this, please help. Feel free to post any kind of feedback, don't hold back. Motivation Video of SU-22:

I looked at the cockpit and the buttons are there. Why have buttons if they don't do anything. It takes 5 minutes to Google it. Same thing was with Razbems' Harrier. Harrier's real aircraft manuals are public information. Right MPCD is not wired for Mavericks, but in DCS they are, even thought they can't be unlock. @Ramsay, your post is good, I'll verify all this when I get back home.

I figured few things since yesterday, but there are some new questions. myHelljumper, you're correct. PCA Select is what I was missing. Now I'm able to return to 530s from Magics, or Gun, but the whole thing is designed wrong. It is not like the real M2000, and it's completely inconsistent. Guns and Magic is on PCA, but you can not select it, or deselect it. What is the point of them being on PCA? In real M2000 there is a button for Guns and button for Magic (I assume it's Magic there) on the PCA, and it's not for display only. 1. Question/Problem: Does anyone know why 530s are not wired for Vertical Scan mode? I have never ever seen that on any fighter aircraft. While 530s are selected I can not go into that mode. 2. Question: How do I go back to RWS mode from a Radar Special Mode? Do I simply shot down the radar and turn it on again or there is a nice way? 3. Which radar special mode are you guys most successful with? My Joystick is enough and perfect for DCS. This is not a joystick problem. To those that told me this is a simulator, PCA Select and Special Modes is pure Video Game function, and has nothing to do with simulator or real airplane. My only problem/question was they were using 2 functions for the same thing as oppose to 1 (forward only) function like in other DCS modules. This gives them ability to go back and forth, which is kind on unnecessary. The real problem is Razbam and their unintuitive approach to controls. Same thing is in the Harrier. 5 badly designed controls and flying the aircraft becomes mega quirky.

I'm new to M-2000, but I'm not new to DCS. I am really struggling with the M2000 bindings. I'm aware of the bugs and some fixes, but I'm not sure I understand the way this aircraft is configured. My setup: Joystick: Extreme 3D Pro My problem: Total inability to roll through/select radar modes one after the other. Total inability to roll through/select weapons one after the other. Problem Description: My joystick has limited space, I can't put too many functions there, so I rely on the keyboard. This is 100% fine with every other aircraft in DCS except Razbam modules. They bind functions in a very bizarre way and they never test (OR FLY!!!!) their modules, that's why we have silly errors. In other aircraft I have a single button to "go through" my weapons and select the one I want. Here we seem to have buttons on the PCA, but with this update the Magic can not be selected using PCA. Is there a way to have a single button to scroll through my missiles, and if not, what is the proper way to select Magic? What does PCA SELECT function do? How do I go through radar modes? I notice it has Special Modes AFT and Special Modes FWD. That is the weirdest way to select radar mode. Is there a way to map each mode or scroll through them with 1 button? This is the most difficult aircraft to figure out even though it is so simple. I mastered the Harrier and I'm aware of Razbam software, but this seems so difficult for me. Please help.

^ You misunderstood the post. I replied to his post. None of the 3 things he said are true. Anyway, the whole thing works fine, it was me uncaging too early while banking.

Figured it out. It's not a bug. It was me doing it. What happened was I was taking down ground units around big SAMs, or taking out SAMs using Mavericks. In order to not get shot down, I would have to sneak in and maneuver a lot. I would slew the TPOD to my target from far away and then and I would maneuver the aircraft towards that target. Then, I would uncage the Mavericks and press Sensor Select Forward. Problem was I would uncage the Mavericks and press Sensor Select Forward while the Maverick field of view would be outside of the slewed target. It's not possible to target the Mavericks to something they don't see. Hence the error message on the right MPCD. I just tested it now and it seems to fix the problem. So it's not a bug, but rather lack of patience from me while under S300 or other big SAM. I hope this helps for those that had this "bug". I'm sure some of the suggestions above could work, but I don't imagine flying the Harrier without TPOD. It's not efficient for me. Few notes: 1. My DMT power was always off. 2. "Don't press TDC down (action) is not needed to target with TGP" - This is not possible. In your description you switch from TPOD to DMT and even then you say you actually do press TDC down. With TGP you do need to press TDC down, otherwise it won't fire. 3. "Have TGP on Left MFD" - you can't do that. It's true Mavericks are ACCIDENTALLY wired for the RIGHT MPCD but they won't fire. That is a bug for sure. The real Harrier is not wired for Mavericks on the right MPCD. Long story short all works with TPOD. Can't uncage when the field of view for the Maverick is not there. That's all.

Got it. Thanks guys. Too bad. I love the Tpod and the Harrier.

Right, but why is that? I'm asking cause I noticed this happens mostly when I'm under pressure and I'm in a steeper dive. Trying to find the cause for going into INS.

Got it. Do you have any idea why it works sometimes and sometimes it does not even though my behavior is the same each time? Obviously I only use the Tpod. Will try your way.

What causes this idiotic Maverick error? 40% of my flights result in this error. I lock the target with TPG and boom the screen goes black. I sometimes manage to fix the problem by going back to Nav mode, and then back to A2G mode again. There must be something I am doing wrong. Anyway, any help would be appropriated. I'm sure I'm doing something wrong.

https://ruptly.tv/en/videos/20190407-041?search_key=6e307a4e-4217-4b61-ae5f-c58b18ec8dd6

Technically correct, but so wrong from many view points. No one wants to limit anyone, especially when they paid money for it. Why be negative and limit something if you can build nice attackers on RED.

The RED side is badly missing precision guided ammunition attacker airplanes. The BLUE (NATO) aircrafts dominate the SIM and create inbalance. On the RED side we have 2 precision strikers: SU-25T KA-50 On the BLUE we have: F/A 18 Hornet - Strikes and CAPs itself. Most powerful airplane in the SIM creating the biggest inbalance. A10C A10A Mirage 2000 Harrier Viggen F14 Tomcat F16 - future aircraft with similar power like F/A 18 Hornet Here is a list of RED attackers that could probably be legally developed with minimal work: SU25-TM (SU-39) Grach This is a modernized version of SU-25T that uses 90% of weapons we already use in DCS. The modernization is basically KOPYO-25 Radar in a POD, 2 anti ship missiles, R-77, and RVV-AE. In DCS we do not have RVV-AE, KH-31, or KH-35. The rest we have. So this is something we would have to find out if it's legally possible to model. This aircraft would allow the RED attackers to carry long range SEAD and 29-T/L missiles at the same time, and it would allow to provide it's own CAP with R-77s. SU-17M4 (SU-22M4 export variants) - Lovely Bomber Attacker with guided munition. One of the pretties aircraft ever. If you combine SU-25T, F-14 Tomcat, and Harrier you get SU-17. Almost the same avionics as SU-25T, but in a sexy design. Very good performer. It has 12 hard points and carries most weapons we have in DCS. We are only missing: KH-23, KH-27, KH-28 (we already use newer variants in DCS). SU-27SM Circa 2003. This is the aircraft we badly need to combat the F/A 18 Hornet. SU-27SM was SU-27S (the one we have in DCS) with R-77, guided air to ground missiles and newer avionics, but not that much newer. The aircraft has DDIs, but nothing crazy. I wonder if we would be allowed to model it. The added weapons were: KAB laser guided bombs, KH-29 missiles, and R-77. Everything we already have on SU-25T and MIG-29 in DCS. MiG-27. Ground attacker version of MIG-23. Carries almost everything we have in DCS, but the aircraft was not popular, and customers bought SU-22 instead. Yakovlev Yak-130 circa 1996. Two-seat advanced jet trainer and light fighter. It carries guided and unguided weapons we use in DCS for the most part. I bet a full fidelity model of one of the above airplanes would sell extremely well. This is something for RAZBAM, as I believe they provide the best flight model out of all DCS modules. ED/DCS should not develop any more flight models, as their flight models are flawed, and don't resemble real world aircraft. They are buoyant and fly like boats/bricks. I wonder which out of the 5 would you guys like the most.

No no. You can do this on the ground even though the documentation says otherwise. Unless you misunderstood my word "start". I meant to say cold start. Sorry. There was a famous manager at Microsoft in the 90's. He would say to you, "But we are not shipping your computer".

I was not able to put my Mavericks in IRMV mode. I figured out what bugs, bad documentation, and lack of knowledge causes issues for lots of us. Below I will show you how to fix the problem, what I was doing wrong, and how to use Mavericks correctly. Known thread (11 pages) with IRMV problem: https://forums.eagle.ru/showthread.php?t=206985&page=11 Problems that cause the issue: 1. Keyboard Mapping bug The binding for enabling IRMV mode and AWACS Calls is the same by default. LWin + U You have to fix this binding and restart the session. 2. Incorrect MPCD I was using (right) the incorrect MPCD for Mavericks. I read Chucks Guide only and never knew selecting the right MPCD will not work. The Razbam documentation is very buggy as well. Read 3 for more info. 3. Mistakes in Guides and Documentation Razbam official documentation is completely disconnected from the Harrier. It's written by a document writer who never verified anything. Same thing is with Chucks Guide. It is a good beginning, but the use of Mavericks is missing information in that guide. a. Bug number 1 in Razbam documentation: Maverick Video will not display on the right MPCD. It will display, but you won't be able to trigger the MPCD Mode. This confused me the most, since I was able to see the video I assumed I am doing it the right way. b. Bug number 2 in Razbam documentation: Mavericks will not be able to cool down unless you are in the air. You can cool them down on the ground, you can uncage them and enter MPCD mode. Can't fire. c. Incomplete way of firing Mavericks in Chucks Guide. Chuck does not distinguish the difference between Internal and External sensors in his guide. He only shows you 1 way of using them. Do not follow that guide for Mavericks. Most videos on YouTube are correct, so look it up there or follow my instructions below. How to Fire Mavericks in it's simplest form: Assumptions: Your keyboard binding is correct, and you are going to use LEFT MPCD. Mavericks have internal Cameras and do not require internal sensor (DMT/TV). 1. Cool down Mavericks. You can do this even on the ground. No need to be in the air as the documentation says. 2. Enter Air to Ground mode and enable all your firing switches. 3. Go to stores and enable Mavericks (do this on your LEFT MPCD). 4. Uncage (map uncage keys) the Mavericks (sends video from Maverick to your LEFT MPCD) 5. Enable IRMV Mode (this requires to map Sensor Select Forward). 6. Slew to target and wait for lock. 7. Fire This way you must uncage and enable each Maverick, but this is the simplest way of using them without the help of on board or external sensors (TPOD, TV) If you have any problems let me know. Razbam documentation and overall lack of any kind of proper guides is bad. This airplane has so many other bugs it's a nightmare if you do something out of order, and it's super easy to do it as everyone's guide is different. Bad, so bad. Ground this thing and fix the errors, or make better documentation. Running: Latest Open Beta.

I have never been more frustrated on DCS as I am with the Harrier. We have gazillion YouTube videos, documentations, guides, who knows what else, but what we are missing is common sense. I'm not the smartest person in the world and I just got my Harrier. I had no idea prior versions of the software did not HAVE INS Alignment option. I had no idea I had to align it, and I had no idea there is an option to change that in the DCS World as well. It took me all day to start and take off the airplane because every documentation is either old, unpractical, too long, or too short (showing off), or missing steps, or not realizing there are extra steps already SET. So this is what I and other noobs would really appropriate: 1. Explain different types of take offs in the Harrier and why they are there, for what reason, and what loadouts are possible with them. 2. Explain different aircraft setups for different type of takes offs. What is that I need for vertical vs normal, or other? 3. Explain difference between INS alignment or auto alignment option SET. Why would I even need this in DCS? 4. Explain what this airplane needs for flying? What flaps setup? Auto, Cruise? What should I do with that H20 while flying? What nozzle setup for flying? 5. Do I even need ground power? Original documentation talks about Ground Power and APU start up, but no one does that it seems? What is the most practical way to start it? I don't need you to show me the buttons, i can figure all this out myself. Just tell me in English what is that I need. Please don't take my post in a negative way, I am trying to help you. The entire DCS is missing a top down view of things. There are way too many bugs, old docs, inconsistencies. Everyone out there has a different start up procedure and it's all wrong I noticed. This airplane is simple, but the documentation and guides are so complicated for no reason. There is something about Russian airplanes and overall war doctrine, they are way simpler, with way more common sense. I am coming off from that side of flying, and I am really struggling here with NATO planes. Put yourself in my shoes, no HOTAS setup, just installed the module, not knowing about past issues, and try getting it off the ground. You follow guides, instructions, videos, and nothing works because it is either outdated, or simply missing steps. You will see how hard it is for no reason.

I downloaded a "Mod" for improving the Panel Lights in my Mig29S, but the textures completely screwed up my cockpit. Can I re download the original? I did not backup mine :(

If this helps anyone, I posted about all this here: https://forums.eagle.ru/showthread.php?t=227397

I will surprise you, the EP-13 modes behave correctly, even though there is lots of bugs around the aircraft weapons and it's documentation. Read below. I became the deadliest pilot in DCS in SU25-T by not following the documentation due to bugs and outright wrong information. I simply retested every weapon behavior myself. I purchased the Viggen and hoped it would be completely different this time. Guess what. Viggen weapons behavior has many bugs, but the official documentation (RC1) and guides have even more bugs. I don't want to post the bugs here, as the list would be big, but I will concentrate on your problem above. Side note: I never flew the real Viggen, and I don't know anything about it. Correct Info: People that built the aircraft put Radar and EP-13 controls on the Radar Stick. The Radar Stick itself has 3 modes: A0,A1,A2. Those modes were installed for both Radar and EP-13. The documentation and Mission Editor refers to them as "Radar" modes only, which does not relate full info to people and creates confusion. They should be called Radar Stick modes. For Radar: A0 - Radar Off A1 - Radar On A2 - Radar On / Alternate View For EP-13 A0 - Default View (Automatic Mode) A1 - Black on White A2 - White on Black (Alternate View) The above settings are modeled correctly in the Viggen. What is wrong is the official documentation. Brightness and Contrast knobs are not modeled in the aircraft but are listed in the documentation. When you enable RB75 with Master Mode in ANF the EP-13 goes on. The Radar Stick is in A0 Mode by default. This is called Automatic Mode in the documentation. I have a feeling the Automatic Mode was developed for attacking at Night. If you were flying at night and turned on the EP-13, it would by default use the Automatic Mode and adjust your EP-13 for the current condition without having you look for Modes. This makes perfect sense to me. I can't test flying at night because when I change the clock in my Mission Editor to Night Time, I don't have the aircraft. I need to figure out that bug to be able to confirm if the Automatic Mode works. To sum up my post: Ignore the documentation and test for yourself. Hope it helps, and YES, you are correct the docs are wrong.

Just bought SU-33 without FC as I don't need the others, but there is no way to download it. I bought it on the DCS World website since my Module Manager 2.5.3 does not have the aircraft. What am I missing? Is there a different way to download it. Does anyone have the files, so I could use my key? When I bought the SU-33, the "new" icon appears in my DCS World main menu but there is nothing "new" in Module Manager when I go there. Please help. And also my Module Manager has every other FC aircraft, but SU-33.

OK, so I have to ask. I'm a software architect and I'm unable to use this module even though the installation was designed for a 5 year old. What I did: 1. Downloaded your Mod from here: https://www.digitalcombatsimulator.com/en/files/2539621/ March 12, 2018? 2. The Folder structured was moved to here: C:\Users\[uSERNAME]\Saved Games\DCS\Mods\aircraft\Pak-Fa It shows up in the main menu when I open up DSC World. It is enabled, but Instant Action is disabled. It can not be used in Mission Editor either. My setup: DCS World 2.5.3 Please help me with the installation, and I have a second question. I noticed you have your plane on GITHUB as well, but the folder structure is different, things are missing. Possible to use your latest builds from GITHUB or they won't work? Thanks in Advance