Jump to content

PuFu

Member
  • Content Count

    8755
  • Joined

  • Last visited

  • Medals

  • Medals

Community Reputation

4118 Excellent

About PuFu

  • Rank
    poly bully

core_pfieldgroups_3

  • Occupation
    professional poly bully

Contact Methods

  • Skype
    ic_pufu
  • Biography
    yarr
  • Steam url id
    http://steamcommunity.com/id/rhspufu/

Profile Information

  • Gender
    Male

Recent Profile Visitors

5143 profile views
  1. PuFu

    RHS Escalation (AFRF and USAF)

    the same way all other weapons in rhs are folded. check your rhs keybinds in rhs menu
  2. PuFu

    RHS Escalation (AFRF and USAF)

    please use feedback.rhmods.org. Indeed there needs to be a balance between real life dimensions and game engine limitations.
  3. PuFu

    RHS Escalation (AFRF and USAF)

    RHS doesn't create content for a specific type of gameplay. You can feel free to create a dependency addon that changes the configs for some vehicles as you see if for the pvp crowd. But that's precisely what we strive for - realism to the extend of this engine capabilities. It just seems our idea of realism doesn't click with your own... i didn't read that entire wall of text for obvious reasons but that is what was pointing towards RHS depicts whatever each individual that is part of RHS wanna work on, as long as it was/is used/fielded presently and/or in the past 30 years or so.
  4. Testing it doesn't mean USN has ever actually operated the aircraft. not the same thing and that is what jester here is saying on that note, this is recent - https://www.military.com/daily-news/2019/10/25/air-force-makes-move-buy-limited-number-light-attack-aircraft.html
  5. PuFu

    RHS Escalation (AFRF and USAF)

    i got to quoting myself...
  6. PuFu

    RHS Escalation (AFRF and USAF)

    https://www.artstation.com/artwork/QzDBk3 mirrored for the non-social media users
  7. PuFu

    RHS Escalation (AFRF and USAF)

    when there is something to post, it usually happens here as well as on our social media channels. OKP7
  8. PuFu

    RHS Escalation (AFRF and USAF)

    We never said that there will be or won’t be a usaf livery (down the line) The reasons for this particular inquiry were simple and logistics oriented - should we stick the p3d in gref directly or in usaf and have gref versions dependent on usaf? we choose to get it directly in GREF, for the reasons stated above
  9. PuFu

    RHS Escalation (AFRF and USAF)

    Wouldn't it be better not to concern yourself with what other people are wasting their spare time on? I'd think that would be the sensible thing to do...but hold on, this is the internet, where people actually think their own opinions matter the most, especially for stuff they receive for free... You must be new here...have a read - http://www.rhsmods.org/faq
  10. to develop a bit on the subject. @Jester504 is still the original author of the Super Tucano project. If he wants to have a separate stand-alone release (independent from rhs one) that is 100% up to him. But some (to be read most) of the configs, animations etc are dependent on rhs configs/functions/scripts. So some substantial changes would be required to do so, not sure if he has the time for it, all things considered.
  11. PuFu

    RHS Escalation (AFRF and USAF)

    There was actually no change in terms of our license and/or the fact that we have never allowed the ACU/ABU and BDU to be re-textured from its very first release. It seems you simply ignored the license altogether for the past year or so. You seem to disregard the fact that out of all the RHS content, the ones that we (or in fact the original author(s) ) doesn't tolerate re-textures is under 1% out of all the custom content provided, so it is an exception rather than the rule. I am not gonna comment on other people's motivations here, nor generalize things like you just did, but...I can tell you though that arma modding community has been plagued (maybe more than others) by theft, commercial and monetization issues and cases of blatant disregard and ignoring other people's licenses and limitation that (might) come with a mod release. There might be a connection here. On the other hand, as an example, the gorka's cut i did only comes in 2 variants of color iRL, no camo variants whatsoever, and it is the same in the mod. Sure, someone did retextures and added camo variants on it as a separate addon dependent on AFRF immediate after. I personally don't mind it whatsoever, even though it is 100% wrong, but someone else might consider that to be an abomination. The easiest way to stop these sort of "abominations" is to limit/deny 3rd party modifications. That being said, we are getting really offtopic here, this has nothing to do with RHS anymore, there will be no changes on this matter.
  12. PuFu

    RHS Escalation (AFRF and USAF)

    We are very sorry to hear about the fact that we've disappointed you this way. /s Hidden Selections is a feature that allows us to have multiple textures on the same model file without duplicating everything, it isn't in fact a feature aimed for 3rd party retextures to begin with. You might want to read our EULA once again - http://www.rhsmods.org/page/EULA#re-textures - Retextures are actually not allowed (we use a non derivative license) , we can choose to tolerate it (or not). There is a very important distinction to be made here. What would actually be out of place would be to disregard any of our individual developers desires in relation to the content they produce and release for you for free.
  13. While i agree with the fact that the author simply shouldn't have posted anything about a release date to begin with, there are always some things that come in between a proposed release date and an actual release date (BIS engine, personal life etc). Again, it is simpler not to post such release date to begin with, as it seems random people of the interwebs (supporters) can get some bad blood and get dissapointed over it Because everything should be taken with a big cup of salt when it comes to hobby stuff. Being disappointed doesn't necessary mean publicly express your dissatisfaction. I have noticed people are getting their hopes up either way, and have expediencies that are more often then not unrealistic to something that is being done in spare time. This entire discussion section of BIF is nothing but a hype train. I honestly do not see the reason for it anymore unless there is some sort of real discussion going on between developer and the interested party. If for one reason or another the supporters cannot grasp that over 60% of post here are never gonna see a release day, its on them not on anyone else. Hobbyist developers are not entitled to anything, just like users aren't - that being praise, or requesting shit just the same. But then again, if one does modding exclusively for people's praises, then that one is doing it wrong to begin with. It is not about being bad or good. it is about being able to distinguish the fact that different people have different interests, and your own wet dream asset might be wet just for you. I really do not get why, after so many years of the same thing, people still believe their request / desire is worth any penny and why they keep doing the same thing over and over again. I can tell you from my own experience that doesn't feel flattery in the slightest after putting a lot of work into something that gets released, the first comment being - "why isn't A or B in yet" or "when will C or D gonna be added", as if anyone is purposely not adding (emphasis on adding rather than creating) stuff out of their magic hat that produces content from scratch on its own out of the fucking thin air. The moment said supporters realize their ability to use a mod is simply a byproduct (and not the scope) of some random bloke on the internet decided to produce (in general for his own private enjoyment) and publicly release such content, then this entire community based around 3rd party mods will manage to grow and evolve. Conclusion: a. Never post about planned stuff or release dates unless you are able to deliver - fair point. It is otherwise simply better for all involved parties such details to be kept under wraps until it happens (you can see all the old farts that are still about creating stuff doing this for the past several years). b. Public release should never be the scope of a mod. The scope should be the developer's fun and enjoyment while creating whatever he wants to create. As such, this entire BIF section should be taken lighter than it currently is. c. The developer(s) is not entitled and should not expect anything (besides his license / EULA respected that is), be it early/late praise, feedback or criticism (purulent or constructive). d. The user(s) is not entitled and should not expect anything , be it a release, his request be produced and delivered, his feedback taken into consideration and long time support and compatibility of the content that he gets to use.
  14. yeah so? even if there is no release in the end, why would you care all that much?
  15. then how can you get how some random people on the internet get upset for not receiving something that some other person is doing for his own personal enjoyment, for free, in his spare time? don't you find that contradictory? promise the what? please... the few people that are still modding for their own enjoyment, not someone else's. and you wonder why people do not pose anything in relation to release dates anymore...
×