Jump to content

Flogger23m

Members
  • Posts

    801
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Flogger23m

  1. Still can't seem to get it to work. Must be missing something very obvious. Would like to get it sorted because I am getting close to placing emblems/numbers on my current project:
  2. Still not sure what to do. Here is an example that I tried to update: Issue still exist. Which part is creating the issue? And now for another slightly related question. As it was, all my liveries/skins had no numbers/markings. For some I would like to keep it this way. For others I would like to add numbers and Russian/Ukraine air force markings. I assume once I get the main issues sorted, the following indicate country specific markings (Mirgorod AFB (831th brigade) in this example): Whereas the numbers are represented by the following: If I don't want numbers/markings, I simply set it to false on all accounts. If I do, I set it to true. Do I have this correct?
  3. Just had someone else download a custom skin and the same problems occurred for them. A number appears on the custom skin, and if there is a vanilla skin and the custom skin is viewed first you will see the problems I posted in my original post. I assume the latest update must have broken something for custom Su-27 skins. Is anyone else having a problem with custom Su-27 skins? If you have time, you can always test if you experience the problem by downloading any custom Su-27 skin/texture. There is no shortage of them in the download section or on Lock On Files.
  4. I just checked some other custom skins I downloaded (that I did not make) and they all share the same issues. Essentially I am creating a folder in: Eagle Dynamics\DCS World\Bazar\Liveries\su-27 The textures files are .dds and called Su27_tex01 through 07. This is how I and apparently others have been doing it. I have no issues with custom F-15C skins; just the Su-27s. And to clarify, this an example of what my description.lau file looks like: livery = { {"su27_tex01", 0 ,"Su27_tex01",false}; {"su27_tex01", 3 ,"empty.tga",true}; {"su27_tex02", 0 ,"Su27_tex02",false}; {"su27_tex02_compos", 0 ,"Su27_tex02",false}; {"su27_tex03", 0 ,"Su27_tex03",false}; {"su27_tex03_compos", 0 ,"Su27_tex03",false}; {"su27_tex03_compos", 3 ,"empty.tga",true}; {"su27_tex04", 0 ,"Su27_tex04",false}; {"su27_tex04", 3 ,"empty.tga",true}; {"su27_tex05", 0 ,"Su27_tex05",false}; {"su27_tex05", 3 ,"empty.tga",true}; {"su27_tex06", 0 ,"Su27_tex06",false}; {"su27_tex06", 3 ,"empty.tga",true}; {"su27_tex07", 0 ,"Su27_tex07",false}; {"su27_nose_numbers", 0 ,"empty.tga",true}; {"su27_tail_numbers", 0 ,"empty.tga",true}; {"su27_tail_numbers_top", 0 ,"empty.tga",true}; {"su27_tail_numbers_down", 0 ,"empty.tga",true}; {"pilot_SU_body", 0, "pilot_su",false}; } name = "Z Yellow 13" countries = {"RUS","UKR"} Made a typo above and accidentally posted a vanilla description.lau twice.
  5. MIG-23s don't have an A2G radar for those that keep suggesting it. My guess? F-16 and maybe a WWII pacific era plane. People seem to mention there was some media released showing off that era.
  6. Going to bump this real quick. For the text, if I set everything to from true to false, should that fix my issues? Thinking of doing it to the text and tail numbers. Not sure what the other stuff pertains to though.
  7. Great news, although I remain skeptical on the AI. Even the enemy/friendly AI still has its quirks and I have a hard time believing there can be quick, accurate and competent AI to fly with. Also, can be play offline as an RIO and have the AI do the piloting? I imagine it would be difficult learning the functionality of the RIO if you can only do it online (limited hours for two people to train together). Also a bit disappointing there is no D version, but the A/B are still interesting aircraft. I do wonder what other aircraft are coming along. Finally, I know this has almost no chance of happening, but a simplified avionics "FC3 level" version would be wonderful.
  8. Thanks for the reply. I assume something is going to change when the port over the textures to work in EDGE? Maybe take advantage of some new graphical features.
  9. Is Leatherneck going to release a texture template for the MIG-21Bis? Something similar to the following: http://www.digitalcombatsimulator.com/en/downloads/misc/ Really like the MIG-21 and would like to make some attempts at a basic retexture.
  10. Thanks for the reply. Here is an example of my custom file: livery = { {"su27_tex01", 0 ,"Su27_tex01",false}; {"su27_tex01", 3 ,"empty.tga",true}; {"su27_tex02", 0 ,"Su27_tex02",false}; {"su27_tex02_compos", 0 ,"Su27_tex02",false}; {"su27_tex03", 0 ,"Su27_tex03",false}; {"su27_tex03_compos", 0 ,"Su27_tex03",false}; {"su27_tex03_compos", 3 ,"empty.tga",true}; {"su27_tex04", 0 ,"Su27_tex04",false}; {"su27_tex04", 3 ,"empty.tga",true}; {"su27_tex05", 0 ,"Su27_tex05",false}; {"su27_tex05", 3 ,"empty.tga",true}; {"su27_tex06", 0 ,"Su27_tex06",false}; {"su27_tex06", 3 ,"empty.tga",true}; {"su27_tex07", 0 ,"Su27_tex07",false}; {"su27_nose_numbers", 0 ,"empty.tga",true}; {"su27_tail_numbers", 0 ,"empty.tga",true}; {"su27_tail_numbers_top", 0 ,"empty.tga",true}; {"su27_tail_numbers_down", 0 ,"empty.tga",true}; {"pilot_SU_body", 0, "pilot_su",false}; } name = "Z Yellow 13" countries = {"RUS","UKR"} Two of the default ones look like the following: livery = { {"su27_tex01", 0 ,"Su27_tex01_for",true}; {"su27_tex01", 3 ,"Su-27_decol_for",true}; {"su27_tex01_BN31", 0 ,"Su27_tex01_for",true}; {"su27_tex01_BN31", 3 ,"Su-27_numbers_red",true}; {"su27_tex01_BN32", 0 ,"Su27_tex01_for",true}; {"su27_tex01_BN32", 3 ,"Su-27_numbers_red",true}; {"su27_tex02", 0 ,"Su27_tex02_for",true}; {"su27_tex02_compos", 0 ,"Su27_tex02_for",true}; {"su27_tex03", 0 ,"Su27_tex03_for",true}; {"su27_tex03_compos", 0 ,"Su27_tex03_for",true}; {"su27_tex03_compos", 3 ,"Su-27_decol_for",true}; {"su27_tex04", 0 ,"Su27_tex04_for",true}; {"su27_tex04", 3 ,"Su-27_decol_for",true}; {"su27_tex05", 0 ,"Su27_tex05_for",true}; {"su27_tex05", 3 ,"Su-27_decol_for",true}; {"su27_tex06", 0 ,"Su27_tex06_for",true}; {"su27_tex06", 3 ,"Su-27_decol_for",true}; {"su27_tex07", 0 ,"Su27_tex07_for",true}; {"su27_nose_numbers", 0 ,"Su-27_numbers_red",true}; {"su27_tail_numbers", 0 ,"empty.tga",true}; {"su27_tail_numbers_top", 0 ,"Su-27_numbers_red",true}; {"su27_tail_numbers_down", 0 ,"empty.tga",true}; {"su27_detail", 0 ,"Su-27_detail",true}; {"su27_detail_compos", 0 ,"Su-27_detail",true}; } countries = {"RUS"} So it looks like more lines were added? Would copy/pasting the new lines fix the issue?
  11. They aren't. Like I said I have used them fine for months, but now when both are present (my custom + default ED textures) I get this issue. When I only place either my own textures or default ED textures in a mission I don't have an issue. Which is what I find odd.
  12. Hello, Been having an issue as of late when using custom skin textures. Never had this issue for many months until a few days ago. Whenever I place a custom skin/texture in the game along with a vanilla skin which comes with the game in the same mission I get the following issue: Top skin is official, bottom is my own. Whichever I view first appears fine. For example, if I first view an offical Su-27 skin it will look fine, but then looking at my custom skin will result in odd textures. Likewise if I view a custom/mod skin first, the official skins will not work until I restart the game. I have not changed a thing with my custom skins for months so I was surprised to see this occurring. Is there anyway to prevent or fix this?
  13. Congratulations to the winners. :thumbup: Thanks for the giveaway to.
  14. To clarify, only if it has a physical presence in your state. With Amazon building more local facilities more and more states will start charging sales tax there.
  15. Congratulations to the winners. If anyone else is going to do a drawing for the F-15 or Su-27 I'll throw my name in that hat (for a friend).
  16. Thanks for the giveaway. Would I be able to enter the F-15C contest for a friend?
  17. Since it wasn't stated, I assume we can't enter for a friend? If yes: I want the MIG. Good luck to the winner. As always, thanks for the giveaways.
  18. Which is too bad. I know things get delayed, although you have to wonder why they announced the Straits map to be released in late 2014 some months back. They are only ~60% done with the artwork and it doesn't look like they started on the other aspects like AI navigation for the map. Did they really think they would have been able to complete it in a span of 4-5 months back then? Going from releasing in a few months to pre-alpha over half a year later is a bit of a stretch even for a release date estimate.
  19. I like both. An option to disable it wouldn't hurt though. Scoreboard is only shown when pressing the ' key anyways.
  20. Agreed. Going to A2G to A2A mode has two options and uses the same switch. It should use one switch/button on your HOTAS to. Any information, or if someone has a pre-done .lau that changes this for all the applicable functions would be appreciated.
  21. Thank you for the giveaway ivan_st. I will take the Mi-8MTV2.
  22. I will take the Bf.109K-4. Thank you for the giveaway OP, and have a nice Christmas/New Year.
  23. MIG-21, because I like them more than F-86s. Plus, there are more weapons to use. I just got it the other day and hardly played with it, but the cockpit detail is amazing. Perhaps the best DCS cockpit. Really nice module.
  24. Have a nice holiday and new year cichildfan.
  25. Edit: Looks like Another member is gifting me a copy of MIG-21. In that case, I will withdraw my entry. Regardless, thank you for the giveaway. Good luck to the winner. :)
×
×
  • Create New...