Jump to content

Sanbato

Members
  • Posts

    43
  • Joined

  • Last visited

Everything posted by Sanbato

  1. the stinger and the mistral do not have the same characteristics. as a result, polychop has created a missile (which does not exist in DCS) from scratch from missile models provided in DCS with behavior that does not match the mistral
  2. I might be able to answer that part, but I think Borchi will do it better than me who does not work at polychop. i can just tell you that the max was done from polychop about it. ED has a lot of subject to deal with third party developers and their own modules (as well as the platform), so wait and see.
  3. it's not a bug, it's a development choice dictated by the limits of the game's environment.
  4. the mistral missile is coded in the game to touch up to 7km (against 6.3 to 6.7 depending on the version and shooting platform IRL) thrust, memory occurs on a third of the max distance. which is the case in your video (approximately). you see that the slowed missile has about 6 seconds (thrust, then inertia, then slowdown). the smoke of the thrust is present all the way, but not the thrust. it is therefore a problem of display of the thrust and not of its effect. this was not the case during the mistral tests, and this seems to have happened following updates on support (dcs). I doubt that the correction of this slight problem is the responsibility of polychop.
  5. the function has been removed due to latency issues
  6. not these values, are very important in flight. for info, IRL no driver is stupid enough to let his battery unload. and if it happened by "accident", the maintenance team, would put a new battery in the shortest time (or connect a GPU), so the notion of unloading a battery, in a game (because it is a game and nothing else), is perfectly useless. For info I work in the aeronautics, on helicopter (lynx and panther) it turns out that when we arrive at 4000 door opening / closing, we must change the hinges. it's not simulating in DCS, it's unacceptable and prevents me from stealing ^^. here, how do I see this thread and its usefulness
  7. it is precisely a flight simulator not an electric test bench simulator. steal and stop looking for useless detail. if you want to have real constraints, pass your pilot's license and fly IRL.
  8. here is a very very good resolution ^^: wait 24 hours before posting to stay courteous and concise ^^ I congratulate you ^^:thumbup: I advise you to post on the subject dedicated to bug reports, with a maximum of data and your crashlog
  9. for the autohover, unless I misunderstood your problem, it is normal that it does not work as in single. only the cyclic chain is automated when you are in multicrew. Concerning the problem that the copilote leaves, is something that was present during the tests but in memory, it was solved (but I could be wrong, it's been a long time now ^^ but i don't think so ^^). i think polychop will work on it as soon as possible.
  10. today, the copilot can no longer drive in multi crew. it was deliberately deleted by polychop, because of latency problems. It's not a bug, it's the new configuration. the copilot will be in charge of navigation (nadir, ADF ...), radio and armament (gazelle M). the pilot will be in charge of the piloting only. for the problem in the minigun, too much information is missing to answer ^^
  11. not to mention the lack of respect with which you speak to those who try to help you or explain things as they are. but do not worry, I understand that it is useless to explain anything to you. I give up, and I will not try to help you anymore. have a good game
  12. my message was very calm and was meant to reassure you that polychop exists and is always at work. but you persisted with a conspiracy theory, followed by a history of breach of trust or whatever. that's what angered the other speakers ^^ @dimi: I'm not a cacochyme I'm a crocophage
  13. hi, polychop still exists ^^, but since it's a very small structure, they may not have time to answer right now. on the other hand for the bug fixes like the camera, they are in the hands of ED (their part of the code). polychop has already acted in its part of the code to solve the problems (or at least a large part) that really bother us right now hope that ED will have time to solve the problem as soon as possible
  14. apparently yes, thankfully! ^^ There have been recurrent sound bugs in the gazelle for a long time, despite the efforts of polychop to suppress them. but I have not yet been able to see what you are describing. can you give more details so that can try to reproduce the phenomenon? (version of the game and the device, multi or solo, conditions mission etc) simple curiosity on my part. it may also help polychop to better understand the origin of the problem. I know that some sounds were disabled (temporarily) because there were problems, that's why on the gazelle L the sound of the barrel is a canon sound by default. maybe your worries come from too
  15. what I say is that one should not make a hasty judgment without having all the elements of reflection. why the first reflex is it to say that if they do not answer, it is because they do not care. polychop is a very small structure. they do not have a community manager, so, we can easily imagine that polychop people who answer, are the actors of development. in fact, they are probably not as available as us to go to forums. when you want a response from them about a bug, increase your chances of getting an answer by giving a maximum of details about the conditions under which the problem occurs (version, multiplayer or solo, multicrew etc ...). just saying "it does not work" is not a bug recovery. they can not exploit the information, if there is no data. and repeating it 100 times will not make things go faster ^^ we are in a topic that is used to the bug report not a topic to give his opinion (if it does not directly affect the operation of the gazelle) ^^ so yes everyone has the right to speak, but in the good topics ^^
  16. Who knows if they did not do it? I'm sure they brought the problem back to ED. We must not forget that some third party developers are not big companies, but small structures of less than 5 people. they do not do it for money, but often for passion. Bringing up bugs is very good, but just saying "it does not work" is not very constructive ^^, especially when it has been done a good twenty times before. for me, making the bugs go straight to ED qd they are concerned, is not something forbidden, on the contrary. I prefer to support polychop rather than to overwhelm it permanently. I also remember that there are not 1 but 4 gazelles modules and that L modules mistral and minigun, are not unplayable if the viviane is dead. ^^ otherwise, other solution (the one I chose) I did not update the release (since it was easy to guess that the bugs viviane would be present) which allows me to fly with the gazelle without problem
  17. I know, but the problem is not related to the polychop code alone. cameras and screens as well as some other data, are directly dependent (at least in part) on the ED code, and not only on the code of third party developers ^^. so ED may not be aware that the problem persists. that's why I propose to inform ED directly
  18. I advise you to raise the problem directly to ED
  19. If you really like the gazelle, I really advise you to join a squadron to fly with it. it is in a group that the gazelle gives its full potential in the role of recognition and destruction of heavy armor
×
×
  • Create New...