Jump to content

grim_reaper68

Members
  • Posts

    722
  • Joined

  • Last visited

Everything posted by grim_reaper68

  1. Hi Just got my first lesson, and as I started the CH47, I saw this ICU light blinking. No info about it in the manual. Is it normal, Did i do something wrong? I also had the EAPS1 and 2 warning, I tried turn the EAPS on, but no changes. And there is nothing about it in the manual too. Do you have the same issues?
  2. I've done it, but still had the same problem.
  3. You have to paste the DDS file in each livery folder. I tried with true, but had the same problem on the A400. I don't know why, but with the same DDS file in the ZIP texture file, it won't work correctly.
  4. I added this line {"MAM_A400M", NORMAL_MAP , "mam_a400m_B", false}; to each livery description.lua file, and the MAM_A400M_B.dds to each livery folder.
  5. Hi for the spitfire_raf liveries, i've found how to have them back. just modify this line in the description files livery = { {"miragef1_common_02", 0 ,"../30-QP 2-30 Normandie-Niemen 2002/30-QP_2",false}; --{"miragef1_common_01_A", 0 ,"../30-QP 2-30 Normandie-Niemen 2002/30-QP_1",false}; and they will be back Of course, you have to do it for each livery.
  6. OK, thanks a lot for the information
  7. Hi First of all, thanks for updating the F1 so well. I just want to make you a feedback about the flight controls. Since the update, it's quiet easier to make AAR, as the controls are smoother arround the center. That's a great point! And in fact, the transition is a little bit to hard between the center position of the stick, and the max position. Especially on the pitch axis (due to AMEDEE). I'm not an IRL pilot, but I had the chance to make a couple of hours on the Mirage F1 CT simulator in Colmar Meyenheim, when I've made my military service. As I worked with the pilots of the RC 2/30 Normandie-Niemèn, some of them let me use the time they didn't use in the SIM. I know it's mostly not representative of the real one, but, as you told about the FFB (what I can imagine is hard to tranfer to non FFB sticks), the stick was going harder as more as you pull on it. I don't how it works in DCS, but maybe it would be possible to make a curve for non FFB, and another for FFB sticks. By the way, as I sat in the sim for the first time (I had a lot hours in simulation games before, so I knew how to basically fly the F1), the pilot explains me that the pitch trim, was also use as an "override". So you could have the stick fully pulled, you could add more pitch by using the trim switch, without having any influence of the neutral position. As told, I made some flight using this "overide", and as I put the stick in the neutral position, the aircraft was flying straight, no need to touch the trim pitch to level it. So maybe It could be implemented too. I hope my explanation are understandable, and may be confirmed by IRL F1 pilots, as I never had the chance to fly in one of the real F1 (the F1B cames couples of years after I ended my duty). Continue make our dreams come true with this Great Module you make. Thanks for all.
  8. could you please locate the pitot tube and other sensors that appears black now on the template? In which file are they located? I tried to locate them by creating a visual livery but they doesn't change. I used flashy colors on the common 3, 4, 5 and 6, the livery changes, but the pitot tube remains at his color. Thanks
  9. just press CTRL+Z (US keyboard) multiple times, so you can shorten the alignement time And press SHIFT+Z to return to normal time of course.
  10. could you please locate the pitot tube and other that appears black now on the template? Thanks
  11. That's the solution! Ok I added the MAM_A400M_B.dds to each livery folder and added a line in each description lua file to make them work.
  12. Nvidia I had a strange appearance too and made a modification to have this result.
  13. From which livery do you talk? If I could have the permission from the Author to publish my modified A400M folder.
  14. Ok thanks for the feedback of this standard procedure in other countries. In France it's not in the landing procedure as far as I know.
  15. Hi Since the last update, the pitot tube and other sensor has moved on the texture, so the skins aren't fitted to the new position, and are totally black now. Could you please share an template so the skin designer could correct their work. Thanks in advance
  16. Very nice video! But opening the chute before landing is not recommended
  17. I randomly set the strobe at 1.25s, seems I had luck as 45 flash per minute equal 1.25s. I doubt about the fact that it's 45Hz, as 1 Hz is 1cycle per second. So 45 flash per minute should be 0.8Hz.
  18. Hi Here is the modification I've made to have the upper white strobe blinking. [WOLALIGHT_FORMATION_LIGHTS] = { typename = "collection", lights ={ {typename = "argnatostrobelight",argument = 200, period = 1.25}, --CT/CR {typename = "argumentlight", argument = 201}, --Green Position }, }, I just changed the argumentlight to argnatostrobelight (line 584 in the Mirage-F1.lua file) and added period=1.25. Digital Combat Simulator Black Shark 2024.07.15 - 22.14.33.01.mp4 I understand that the flyable EE version doesn't manage the white strobe as it's specific to the CR/CT version. Am I correct? We use the "version args" to have the appearance, but not the functionnality remains on the EE version. So the only thing to modify would be to change the color of the white strobe cover to be visually good.
  19. On my side, I've found that my own mod was the cause of crash. After investigation, it was a syntax in an lua file (light section) that was in fault.
  20. I tried to find where the texture of pitot and other sensor are, but not found yet.
  21. Hi When the GBU12 are mounted on the AUF2, they're unable to track the laser from the JTAC. I've made a cross check, by using GBU 12 on the AUF2 and a single GBU 12 at the fuselage pylon. The single works fine. Same at wing pylons when single GBU12 is set up. By the way, they explode correctly when hitting the ground. Seems there is only a problem with the tracking system. Of course they were setup with the correct laser code.
  22. Hi works fine on the french version
  23. After a little investigation, the F1C-200 (and surely the F1C) has red strobes on the top and the bottom of the fuselage. And as far as i could see on the photos, there was only the red strobe on the top, the white strobe was introduced on the CR/CT. Maybe you could make it like an argument configuration option like the other parts of the F1 . I know you have a lot of work and this is only a detail. The most important thing here is in my point of view the color of the front top strobe, that, i'm sure can be fixed easely. For the strobe, I changed it to argnatostrobelight with 1.25s in the lua file which seems to be good.
  24. Try with the french nation, I have them both.
  25. Impressive! I didn't noticed those details.
×
×
  • Create New...