Jump to content

Esac_mirmidon

Members
  • Posts

    6518
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Esac_mirmidon

  1. Thanks a lot prccowboy ¡¡¡ This is one of my favourite mods ever. Is great for inmersion and mission editors. Just a dream of options and loads.
  2. Gotcha ¡¡¡ That trick fix the issue. Just add the parts file to the skin folder and rename the file + add the line to the lua and perfectly fine now
  3. I have the same problem. It seems the terrain " remember" the hits by CBU´s and the texture effect of the explosion remains in place.
  4. Just try this: Fly the final leg with the VV pointing where im telling you ( at the right of the landing deck, roughly aim to the Crotch ) and feedback the results. Forget about BRC on final. Just align with the landing deck and keep the VV all the way pointing at that place and follow the ball for glide path With different carrier speeds 11kts-27 kts whatever you want. I will asure you will land perfectly aligned with the deck and the bolters or wave offs will be safe. Take alook at this video, how on every final approach they are pointing the VV where im telling you
  5. The BRC is just a navigation help for initial-break-abeam pattern. When you are turning to the groove-final the BRC doesnt matter anymore, just follow the visual tips ( position of the carrier, height at the groove, height at the final when you intercept the glide path. Is just an instrumental pattern from abeam to final. In final just aim roughly for the crotch and follow the ball until wire catch. Thats all, the Carrier´s speed doesnt matter if you compensate the drift pointing at the same place on the carrier. Is not the Carrier´s speed, is where you are pointing your VV what is important. If the Carrier is moving on the wind of course. If teh Carrier is not aligned with the wind then you must face this kind of drift and you need to compensate more. Maybe you are facing a carrier not aligned on the wind, and thats why you are drifting more. But if you point the VV on the right place i can asure you will not drift at all from the deck center landing point. Just COMPENSATE your VV all the way to the wires TO THE RIGHT SIDE of the landing point. NO matter if the carrier is moving fast or slow. Dont align using heading numbers ( BRC - 9º ) , align on final using the VV to the right of the landing spot and use the ball lights. You are compensating the drift with your VV position on the Carrier, if you keep a X heading on final all the time instead moving your VV, then of couirse you will drift on final, because you are moving ,the carrier is moving, the wind is moving, etc. XDDD
  6. First make the Carrier sail at a combined speed ( wind + carrier speed ), about 20-30 kts. Ideally 25 knots is a good combined speed. Second, take note on the editor about the wind direction and make the ship sail on the same heading. ( if wind is COMING from 090º TO 270º, make the ship sail the same FROM 099º to 279º ). This will make the wind flow exactly over the angle deck. Third you dont need to compensate for carrier speed. Just compensate for your own AoA speed for landing. Your On Speed is the important thing + BRC of the carrier ( Ship into the wind heading ) Fourth, the angle deck is -9º left from the BRC so you need to compensate on final not the carrier´s speed but this angle off deck position in relation to the ship BRC. This is made using your Velocity Vector, pointing to the right, more or less to the angle between the angle deck and the front of the ship ( The CROTCH ) and follow the meatball on the IFOLS to correct your glide path. If you follow the ball on final and the velocity vector more or less on the Crotch, you will fly compensating that -9º angle off while approaching easily. The rest is practice. Think about carrier landing as a runway landing with a slight wind coming from your right that is pushing your nose to the left. To compensate that wind you must turn your nose a little to the right ( to point the velocity vector on the runway ). The carrier is the same. The " light wind fro the right pushing your nose to the left " is the -9º deck angle off , so you need to compensate a little moving your nose ( VV ) to the right. That all. But use the ball to correct your glide path, not the Crotch, or the LSO will catch you on the cabin very angry for not follow the ball and follow the Crotch ¡¡¡ The image is a tip where the Crotch is.
  7. What kind of flight modification? Can you extend a little about it?
  8. They have changed the way ships sails over water, is a different approach to that effect. Some like the new ones more, other not so. In real life depending on the conditions you can see those wakes or barely nothing except the white turbulence.
  9. It´s possible to make the S-70 windows transparent or at least some kind of glass texture? Right now is just opaque grey.
  10. Thanks a lot Hawkeye ¡¡¡ More things to fix: The Hiryu Carrier without deck planes has a different color section on the middle of the ship not present on the fouled deck version. And also there are 2 pilots floating on the end of the ship Also i dont know why my DCS crashes when i use Fouled deck versions of any carrier. I will try the new Soryu Fouled deck version. But only the empty deck carriers are working without DCS crash on my end. PD: SO The New Soryu is not crashing when using fouled deck version. NICE ¡¡¡¡ But this carriers ( old versions i have ) are crashing when using thre fouled deck IJN Hosho IJN Kaga IJN Ryujo IJN Hiryu Thanks a lot if you can take a look, to make the same changes as the new Soryu
  11. Thanks a lot mate. This IJN pack is perfect for a Marianas WWII campaign.
  12. I´ve seen the Soryu Carrier model has floating elements on the front of the ship, at different heights. Maybe worth a check
  13. Yes, is quite simple. Navigate to: DCS World\Scripts\Aircrafts\_Common\Cockpit and edit with NOTEPAD++ the following file. localizer.lua On the very top you can read: country = "EN" if LockOn_Options.avionics_language == "native" then country = "RU" end CHANGE "RU" for "EN" like this: country = "EN" if LockOn_Options.avionics_language == "native" then country = "EN" Save changes and thats all. Take in count that with every update you must do this again, or just copy and overwrite the file from the backup folder after the update. PD: Taz option is even easier..... XDDDDD
  14. Fixed and working like a charm AJ. Thanks a lot for your kind patience and awesome support bug hunting.
×
×
  • Create New...