Jump to content

Menrva

+MODDER
 View Profile  See their activity

  • Content count

    4,443

  • Joined

  • Last visited

  • Days Won

    45

Everything posted by Menrva

  1. I don't know what to tell you, nobody has ever reported such an issue. I'd say something went wrong with installation on your end; the installer is simple, it installs the OperationDesertStorm executable and custom initialization screen in your SF2 game folder, and the relative mod folder in the usual "Saved Games/ThirdWire" directory.
  2. You simply cannot do what you mentioned. Stock aircraft skins are read as long as you use the same folder name, because in the .cat archive such skin is inside a folder with such name. The only thing you can try is to place .bmp skins in the main aircraft folder, but that is advisable when a skin is used by multiple skin folders with just different decals. Otherwise, you can convert stock bmp files to jpg and add them to your custom skin folder. It's one or the other.
  3. @strahi please, write with normal font, there's no need to shout and write all in big letters! I am the author of the campaign files, among other things. The infantry models were made by guuruu.
  4. @crisisloaner None of the above replies applies in this case. I had this issue while working for ODS, and it was never mentioned so far. For some reason, the game stopped reading some of the custom aircraft even if the entire files are there! It was crazy. The only solution was to copy them over from a backup folder I had. I suggest to recreate the mod folder, by simply renaming it and fixing the path in the Options.ini file, as well as renaming the executable that is used accordingly. It's a real mess IMHO. I have a huge install spanning from 1948 to 2018, I probably gathered all possible aircraft (no fictional ones, but many prototypes are in it). I count slightly more than 1,500 aircraft folders. I did a lot of work to unify many aircraft folders and remove any duplicates (there's no need to feature both stock aircraft and their third-party replacements, as well as there is no need for many different aircraft folders if the only thing that is different in them is the skin).
  5. That was fixed a while ago in my huge overhaul project (WIP), but with the 60% size it sucks anyway: https://combatace.com/forums/topic/94432-myth-of-north-vietnam-abs-info-needed/

  6. A.M.I. F-104 Starfighter "Storia di un mito"

    Menrva replied to paulopanz's topic in The Pub

    @whiteknight06604 I am afraid this won't be coming soon, as I have to finalize much of the tiling manually, and it's a very time consuming job. Not to mention that we're still busy working on ODS, so much to improve upon. Also, I don't want to release a half assed terrain. Target area wise, it's filled with all possible bases and real SAM site locations. All river courses and lakes have been reproduced very accurately! This would be the perfect companion to the stock GermanyCE terrain. A specific version for the 90s and beyond will be made afterwards.

  7. Human Transport by Fighter Planes, EXINT POD!

    Menrva replied to GKABS's topic in The Pub

    Such pods would only make sense for very black operations. Only a mentally strong operative can keep his/her cool in it. To use them for carrying wounded is plainly stupid. Med evac helicopters are meant to be flying ambulances, where the wounded can still be treated on the way to a hospital. With the pods, that wouldn't be possible. Civilian hostages, I doubt they would like this experience after the traumatic one they have experienced before. Thanks to @GKABS for posting this, nonetheless. It's an interesting concept I've never heard of, something to remember in the history of military aviation, with the likes of circular runways and other such ideas.
  8. The crashes at 80% are a well known issue of the game engine. When there are many different third-party objects, the game is overloaded. Try reducing graphics settings (due to the highly detailed aircraft and textures, avoid Unlimited for all options as a safe approach), it should help. The campaign is pretty heavy since it contains hundreds of different aircraft and ground units, and the terrain is filled with target objects. The cockpit of the MiG-25 actually is an unfinished 3d model, hence it may have issues. Until something better comes, live with it. The other issues have been noted. Thanks for reporting them!
  9. Don't worry, I did not take it that way. I really want to portray the helicopters in the campaigns at least for the AI, but the AI does have trouble with them as well, not to mention that you need fake runways from which they can take-off. As long as they are treated like normal aircraft, they'll remain as additional objects for mission creators. If you wish to make them flyable, you can. Most helos and cargo aircraft already contain proper cockpit files. Just keep in mind that I don't offer any support for them at this time. I hope TW gets back into the game and unlocks the hidden potential of the SF2 series, but until then we're limited to what the game can do. @Viggen The issue you mentioned has been fixed, it will be included in a future re-release. Hopefully only a handful of bugs remain. The massive amount of content implies that more bugs can happen. Despite that, the team has done its best to reduce them to a minimum. With time we can only polish the product even further.
  10. Nations are restricted to Desert Storm participants and to ones proper for the theater of operation; I don't see a reason to be able to fly for a wrong nation in the Iraqi theater, not to mention that each of the visible nations in the mod use custom made national counters for the planning map. It would have been a waste of time and resources to create 200 different national counters which would be mostly unused. Cargo aircraft are not flyable because they are not supported with proper user-playable missions, they are meant for the AI. Heavy bombers have issues when are used by the player, there are instances where they would crash the game to desktop, and overall they are never meant to be used by the player in stock SF2. Other aircraft missing proper cockpits have been left out for quality consistency. Helicopters currently exist as additional AI-only aircraft for custom made missions, they are not properly supported by the SF2 game engine (too many issues and limitations in regards to missions, flight models, usage of weaponry etc., for proper helo behaviour).
  11. Just lower your graphics settings. This mod has a much higher quality fidelity than the stock SF2 games, with many high-res skins and high-poly 3d models, so you need a more powerful PC for it. Unlimited graphics settings are not recommended. Also, the Persian Gulf War campaign is much more complex than any other campaign ever made for SF2. It contains hundreds of different aircraft and ground units, so the game engine will have trouble to deal with so many of them at the highest graphics settings.
  12. @mono27 It was a mistake on my part. A 6 month plan is the minimum. By mistake I referred to it as the 1 month plan. The description at the announcement page has been fixed. My apologies for the misunderstanding I caused. I was told by Erik that the download is meant to work also with 1 month subscription plans, as originally established. So I must correct myself again. The issue should have been fixed; should anyone encounter problems, let us know.
  13. @DoctorQuest We agreed on a 1 month minimum. I was told the download requests 6 by mistake. I will notify the admins about it.
  14. It should be premiering now.
  15. Thanks! Is the CK-2 coming anytime soon? It'd be needed...

  16. 20201224_165015_edited.jpg

    Menrva posted a gallery image in Member's Albums

    From the album Christmas Eve 2020

  17. Christmas Eve 2020

    Menrva added images to a gallery album in Member's Albums

  18. 20201224_165126.jpg

    Menrva posted a gallery image in Member's Albums

    From the album Christmas Eve 2020

  19. 20201224_164916.jpg

    Menrva posted a gallery image in Member's Albums

    From the album Christmas Eve 2020

  20. Thanks, mate. His transplant went alright, so hopefully he'll be back home soon. Likewise, stay safe and strong, my friend. We often forget there are great people in hospitals, doing sacrifices every day for the health of others, especially now that there's an invisible and terrible enemy.
  21. I'm sorry to hear this. At least I hope you get to enjoy Christmas with your family soon. Things are not that bright on my end as well. I'm spending Christmas alone, my dad's been in hospital for more than 30 days, to cure a terrible blood disease he had to live with this entire year. I guess we're not the only ones hoping that 2021 be a better year...
  22. I agree with you. But you miss the point. You branded what I said as totally wrong, and in all honesty I fail to realize why it is so. It's not a matter of opinions. That being said, peace to you all. Enjoy the holidays with your loved ones as much as possible during these difficult times.
  23. Alright. Next time, I'll shut up and let you guys do the talking. I didn't know that informing about risks and legal aspects in general was something wrong. Also, I fail to understand that TK does not care when at the same time he made things much harder for us modders throughout the years. But I'm wrong, so I'm outta here.
  24. If that's the case, then TK might as well hand us out the source code, for free or on sale at a given price. It would make things easier for a thing he does not care about. This entire discussion was pointless IMHO. I just pointed out that there are legal aspects to consider about reverse engineering, in general, not just related to SF2.
  25. I'm not wrong. First, you're talking about doing whatever we want with a code, code which we do not have for obvious reasons. Second, EULAs generally exist for this reason; to have a code totally reverse engineered, it means that you can even rebuild a product from zero. With that, anyone who gets their hands on such a code may well create a derivative product, rebrand it and make it look like as it were a different thing totally unrelated to SF2. This is not a risk developers like to take, EULAs generally restrict users from using their products and IPs in improper manner. You buy a game for what it is, to play it and not to outsource stuff from it. You cannot make up the rules as you'd like them to be, I'm afraid. TK said something in an e-mail long ago, but he was talking about what you said, about smaller patches/tweaks to hardcoded bits of the .DLLs and of the .EXE, which is not the same as reverse engineering the code and share it with the public. To create certain tweaks, some knowledge of how the game works under the hood is needed, but you do not necessarily need to reverse engineer the entire code. I'd rather stick to the EULAs than to some long gone email which TK may always disavow. He is the same guy who locked harmless shader files from modding (though LODs had a reason to be locked). If I were you, I wouldn't swim in such murky waters. Live with what SF currently is. The dead horse has been beaten too much on this matter. EDIT: a quick search will explain you why it's legally risky: https://www.eff.org/issues/coders/reverse-engineering-faq#faq2 TK can say anything in an email, it's the EULA shown in his SF2 installers that counts. Frankly, I never read what his EULA says and I couldn't care less since I like to stay well within what's legal.
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..

  I accept