Jump to content

DirtyFret

Members
  • Posts

    231
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by DirtyFret

  1. Yeah, me too. Had to fly the whole route all by myself. I have no idea if I missed any other triggers or action in Mission 2. Nice sightseeing though :pilotfly: Off to mission 3 hopefully I get to shoot something in that one. :)
  2. If removing this tweak via JSGME doesn't work may I suggest you try either the repair (Standalone version) or the Steam "Verify Integrity of Game Cache.." function.
  3. Oh :cry: Sry, I must have messed up the files. Should have double checked before "announcing" stuff and jumping up and down in joy. :P But yeah, the GAU tweak file (on post #1) has been now updated with the correct directory structure
  4. Yep it doesn't , they moved the shell_table.lua to DCSWorld\Scripts\Database\Weapons\ But it seems ED have fixedthe dispersion issue. The native shell_table.lua show now values of Da0=0.0009. Or maybe I have somehow messed up the files. The original value was Da0=0.0017. If this is the case I am very happy to announce that this GAU tweaking is now obsolete.:D
  5. Patch For 1.5.4 Annunciator light issue fixed R863 numbering corrected Patch instructions: Copy/extract the content of the zip file into your Vasilisa Blue/Gray/LightGray directory. Patch1.1.zip
  6. Thankthankyou. :bows I was getting somewhat desperate and grayhaired unable to solve this. So they have changed the mapping. I'll get to fixing these ASAP. Might take a short while - I'll have to redo the corresponding files and I am heavily loaded with work for this week
  7. Argh. Y U must tease :D
  8. Hmmm. I can't replicate the problem. I am using Steam 1.5.3 version with Caucasus map (obviously:)). This was a quick test with the instant action mission "Target Practice". I have also checked that the DDS file structures haven't changed and so I don't think that the texturemapping has changed. In what version does this problem appear and is it persistent in all mission and settings you have tried? Have I misunderstood the problem/issue? I'l try to do some a bit more testing to see what I can find.
  9. Thanks for letting me know msalama. I'll try to troubleshoot this ASAP.
  10. Thanks, Well spotted. :thumbup: Corrected to 200 rounds. Pack updated.
  11. Fixed the MW50. My apologies that it took so long.
  12. Yeah, pretty sure the values are m/s and kg, I found in other .lua lines comment lines indicating so. Fixed the MW50 issue. Should be working now. Links updated in #1 post.
  13. I have been playing with the 1.5.3 Steam and tested all of the version with any discernable FPS hits. There might a small hit but I can't really tell the difference. Are many of you experiencing a drastic FPS drop issue? Bummer. I'll see what I can do once I get my hands on the 1.5.4 version. Could it be the new IC?:helpsmilie:
  14. Thanks for spotting this. I'll try to fix this issue asap. I assumed it's m/s and kg, but that's just an guess. I totally made up those values based on my tests, I wanted 1-3 hits to kill a pony and 3-5 hits to kill a bomber. Ill try to see if I can fix that MW50 issue.
  15. Good to hear you like it but Sry to hear about the FPS issue :huh:, may I ask what version/color of the cockpit are you using and with which map/DCS version?
  16. LightGray version has been uploaded to DCS User Files. Pending approval currently. The impatient ones can spam F5 on Mi8MTV mods or on my user files. :D Additionally the switch bases on the central panel have been reworked to HD level. Please keep in mind that the LightGray combo has not been as thoroughly tested as the BLUE and GRAY before release so there might be some (or even major) issues with mismatches or texture overlaps. Report them to me by PM or on this thread please. POST 1 updated
  17. Hey all, sry for the absence. I've been swamped with work, academic stuff and happy family life :D. I've had almost zero flight time in DCS and subsequently have had only very limited time to work with the updates. ..but I am slowly working on them. The switchbases on the centralpanel are (almost) done. Also the light gray version is coming along slowly but steadily. Soon TM @Devrim Thanks, I am happy that you like it. The text style I chose because of personal preference but I have to agree on the backwall issue. It could be (alot) better. I'll eventually try some iterations on it and if the spec maps start working it might actually start to look like metal and not concrete :D To my defence the backwall was the first section I edited back in late 2015, my skills are now better than that @UN249 Sry not yet. I cant write/read cyrillic. If I find a russian skilled collaborator with photoshop skills I hope we can publish a RUS version of this.
  18. Looks nice. I won't change the current color layouts in the existing packs but this paint combo I like alot so I might do a "Lightgray (#D3D3D3 or #C0C0C0) version of it. Quickly looking through my PSD files I would guestimate that it will take no more than ~3-4h of additional work to do this "repaint" so I might do it. No promises yet though as I am still working on some other minor upgrades on the Gray and Blue-one but will see :smilewink:
  19. In the meantime I reworked the GVRN panel and started work on the switch bases. WIP WIP Constructive critique/comments welcome
  20. Absolutely it is. Here is a good mod to clean the glass from our good friend Devrim. Or if you prefer the original just swap the mi8mtv-cpt-glass.dds file from the original cockpit texture pack.
  21. Glad to hear. Thanks for sharing.
  22. Thank you very much Alpha, I appreciate the fact that you took the time to send that. I'll incorporate this into the next update (Soont(tm)).
  23. Oh well thats kind of a relief. I was beginning to be quite frustrated because I couldn't find anything on how to even start fixing this problem.
  24. Thanks for the screenie. Those numbers/font are definitely from my remake. I'll try to locate those numbers and test the description.lua for some hints as to the cause of that. In 1.5.3 the numbers and R863 are fine and work as intended. I do not own the NTTR 2.0 map and without it might prove difficult to fix this.:noexpression: I'll see what I can do. (maybe buy the NTTR map? :D)
×
×
  • Create New...