Jump to content

kersaint

Members
  • Posts

    48
  • Joined

  • Last visited

Everything posted by kersaint

  1. kersaint

    COMMS Menu

    Hello, why do we have to suffer this kind of incident, the goal I do not know, I paid all my modules in I hear that they must work without defects, I will not uninstall VA, I use it with Elite dangerous, il2 sturmovik, and others that they have never created problems with VA. for now it is DCS that I put in oblivion, and if I have to uninstall something, it will be DCS.
  2. kersaint

    COMMS Menu

    Hello, yes same problem with voiceattack. What a disaster. I shouldn't have done this update, but we're not soothsayers.
  3. Ah, I made a mistake, I did not post in the right place. Yes to move, a thousand excuses.
  4. Yes I am on small flights of personal training. I'm not on easy comms in game on Vaicom pro it's on off
  5. Yes it makes no sense, yet when I fly with the Mirage 2000C or another module, Vaicom pro works wonderfully in VR.
  6. Hello, thank you for answering, I just read it again and I did not specify the situation. So in use without VR directly by playing on the screen, Vaicom pro works very well all ATCs respond. It is only when I fly using VR that the problem is present, so only Kobuleti starting base answers me, the other frequencies are unanswered. Kind regards.
  7. Hello, I want to submit this other issue with Vaicompro. When I fly with the F1 without Vaocimpro the communications work very well with the ATCs, they respond to your approach. But when I do it with Vaicompro, (example) Departure from Kobuleti with its frequency 133000, arrival on Batumi, I enter the frequency 131000 to announce my approach, the display remains on Kobuleti is no answer, if I stay on this frequency and I put the corresponding channel, it is Kobuleti who answers, in fact if I put any frequency, it will always be the departure airport that will respond. That's my concern, would I have done something wrong. Kind regards.
  8. Thank you, so be patient then.
  9. Hello, thank you for having answered, I am disappointed that Vaicom pro is thus neglected, I will do with it, I will continue to use it. Cordially
  10. Hello, when I use Vaicom Pro with the Mirage F1 in dcs World Openbeta, the mirage F1 is not recognized by Vaicom Pro and displays the Christen Eagle II instead. However the communications work in flight with the F1, is there a solution to this error. Thank you Best regards.
  11. Back on the slow repair of the Openbeta version, no event noted, no crash, no blocking, no freeze, flight with the mirage F1 for test. Thanks to BIGNEWY for the solutions given. In case of recurrence, I will post the Log file. Sincerely.
  12. Hello, thank you for replying. I don't have any unofficial Mods except the FrenchPack, I don't use DCS for Steam. I'll do the repair slowly, or even rename the folder just in case. Kind regards.
  13. Hello, since the last update 2.7.16...,DCS World Openbeta blocks, that I am in flight, on the mission editor, on the interface, no matter where I am, it blocks, forced to go through the task manager to close DCS World Openbeta, I have no Mods installed, DCS World Openbeta is clean, I still report that before this update I had no crash, blocking etc... , thank you Sincerely.
  14. Hello, it has already happened to me the crash of DCS WORLD with Frenchpack, it was the fact of having installed it in Users Parties registered Mods tech but also in JSGME and DCS crashed, I disabled in JSGME and I had no more crash.
  15. Well I found, I renamed DCS World to . OLD, I recreated the Mods/tech folder in saved part and all the vehicles of FRENCHPACK V4.8 are operational again. I remembered that Bignewy in a topic said to act this way if a problem arose. Have a nice day everyone.
  16. Hello, I have a problem with Frenchpack V4.8 and Frenchpack_CA V1.5, no vehicle appears in the mission editor, on the other hand they are visible in the encyclopedia, the files appear in the root of DCS World. It happened suddenly without warning. I tried everything, JSGME or OvGME, nothing helps, ah yes I was going to forget, in Module Management in "Installed" FRENCHPACK also appears. and that's also the same in DCS World Openbeta.I did everything to find the problem, but in vain, what should I do. Thank you.
  17. I will look for where is the difference between the two versions, thanks to you. Kind regards
  18. Hello, I did not understand too much what you want to tell me, sorry, what I want to say is that in DCS World Openbeta, there are more units on the ground such as Infantry Soldier JTAC, MAM USAF Pilot, Ammunition box that do not appear in DCS World Stable. Thank you
  19. Hello, I noticed that on the dcs Stable version, several units are missing, thank you. Both versions of dcs World have the same version 2.7.7.15038. Kind regards
  20. Hello everyone, yes that's what I did afterwards I deleted all these unofficial mods, I had an Aircraft folder with planes, like A-4E-C, MirageF1 2.5.5, mirage F1 CT 2.5.5, VSN_SEM and this prevented the start of version 2.7, I was even able to recover the DCS Openbeta folder that I had put in backup , so I recovered my full config. Thank you to Bignewy and all of you for your efforts in finding solutions. Kind regards.
  21. Good evening, Crash version 2.7 at launch. I made all your suggestions and the only one that works for me is the solution of Flappie rename DCS Openbeta in Backup to leave with a new folder DCS Openbeta and it works properly, remains more than to hand over everything else one by one to recover my config before, for now I handed the file Config and the File Logbook, it works Thanks Flappie and those who proposed . Kind regards. ...
  22. Hi, it's the same for me, crash then back office, and crash declaration window does not open. cordially
  23. kersaint

    galons

    Salut à tous, C'est bon je me suis débrouillé pour que le lieutenant retrouve ses épaulettes avec ses deux barrettes. Il y'avait un décalage, exemple le capitaine avait des épaulettes de lieutenant. Merci pour votre aide.
  24. kersaint

    galons

    Bonjour à tous, dans mon carnet de vol de la version 2.5.0 j'ai remarqué que l'épaulette ne correspondait pas à mon grade actuel " Lieutenant ". Cette épaulette comprend une seule barrette au lieu de deux pour le lieutenant. J'ai cherché si quelqu'un avait eu le même bug , j'ai rien trouvé. Avez vous une idée merci. Cordialement.
×
×
  • Create New...