sedenion

"BEEP"... simply

New version with fixed bug i discovered myself. The backup path were not updated internally when config was edited until software restart, resulting on backup corruption if we enable mods after editing the backup folder without restarting OvGME. Features / Changes (1.6.8 ) - Fixed config edit backup dir not updating which produce backup corruption. - Added warning confirmation message if backup folder is already used.

Ho, this method was unusable for Master Arm switch some mounth ago... i see that this now works fine, thanks.

Hi, Remarked i have the same problem here : 00000.387 ALERT SOUND: Can't start XAudio2. 00000.387 ERROR SOUND: can't start renderer Problem on both 1.5 and 2.0 My sound card is an Asus Xonar DSX (if that can help) PS: FIXED, i found the problem. I was working on a fresh Windows 7 installation, with a recuperated DCS installation, and the system DirectX version was not up to date. To solve the problem, download and install this : https://www.microsoft.com/en-us/download/details.aspx?id=9033

Hi, I am sorry, i come back with this... is there any chance to have optionnal separated bindings "Master Arm ON" and "Master Arm OFF" in addition to the current Toggle ? This is not vital, but that would be very cool for Warthog users...

The DLZ texture coordinates was indeed catastrophic (forgot to update it)... this is now fixed.

Fixed the download bug on big files... New release exe and installer available for download (still the same version 1.6.7, but the bug is now fixed) For the curious guys, the problem was the following: The download size (http content_length) was limited to 2147483647 bytes, because of string conversion using a function that convert to a 32bits signed integer value, wich is limited to 2147483647 as positive value... So i changed to use a convertion to 32bits unsigned integer, which is limited to 4294967295. This mean, the maximum download size is now ~4.2Go ... (If one day, someone make a mod bigger than 4.2Go, i will search how to convert a string to an 64 bits integer value... but for now, 4.2Go should be enough)

no, i should set up a local http server to make tests, best and quickest way.

I was drunk when i coded the feature the first time... or something like that :) More seriously, there were a problem in the XML parsing process. Should now work, but this now required to have an XML node named "<mod_list>" with "<mod>" inside. If you follow the name rule, this would be fine. Ok... this will be very easy to debug a download on a 2.5Go file... :/

How it never end ? still at 99% forever ? finish with an error ? Possible, but need lot of work from current stage... and i am lazy right now :)

Thanks, I'll see that soon.

New version available (see first page for download links) with XML parsing fix + new feature to test XML file parsing offline. OvGME 1.6.7, 2017-18-01 - Fix XML repository parsing error. - Add XML parsing test feature.

I still need details... Do you edit the generated XML file ? If yes, at what moment, after what action, in what software, etc...

Can you please detail step by step what to do to reproduce each bug ?

This one ? : https://github.com/sedenion/ovgme/issues/9

I am pleased to annonce the update of this mod for the latest M2K module version. I don't have tested all HUD modes, if you see something wrong, tell me so i correct it as soon as possible. I also added my VTH Glass fix, for a more transparent and realistic Hud. (Download link in attached piece in the first post.)

I am pleased to annonce the update of this mod for the latest M2K module version. (Download link in attached piece in the first post.)

No, sorry.

Personally, i will only regrets to not been more vigilant... I don't need antivirus, i only need to be carefull about what i download. Since i well know my system, because i well known and strictly control what i install, i am able to eradicate any malware that bypass my vigilence. This already happened (one time), and this was a matter of few minutes to fix it and send an insults mail to the editor. But okay, it is true, not everybody is able to do what i do... That's it. The way around that, is: don't use antivirus :music_whistling: Windows sufficiently uselessly scratches the hard disk to add another useless "real-time virus check" and an endeless loading time. This is my point of view... i force nobody to adopt it.

The fact, i have nothing against you, i have something particularly against Avast, Norton, and more generally, against the business of antiviruses, which i consider as useless and kind of "lawful malwares" who divide your system performance by two to mostly annoy you with scary addvertesing and false-positive alerts. My experience teach me that antivirus blocks only the well known viruses. When there is a new virus, and if your antivirus did not updated its database (which need the virus to be well known and identified), you are good and ready to be infected without any alert of your antivirus. All computers infected by malwares and virus i seen, were ALL working with an up to date antivirus, almost all the time, precisely Avast... what a joke. There are plenty of other free antivirus than Avast: Avira and PandaFree for example.

Ok, guys... The things are fair simple: 1. OvGME is NOT a malware, as other said, this is open-source, and everybody can verify that there is nothing "evil" in the software. 2. If OvGME si tagged as "dangerous" or "infected" by an antivirus, the Antivirus should tell you WHAT malware or virus infected the executable, because all malwares and virus have a name, a signature. 3. If the "signature" is a real virus or malware, you tell me, and i check if i am infected somewhere, if the installer is infected, i apologize, etc... 4. If the "signature" is any Avast "*Rep*" alert, this simply mean Avast does not know OvGME and consider it automatically as "not trustfull", which is pretty logical, since OvGME is not a mainstream program, and i have not paid Avast to make it seen as a brilliant beautiful secure software by Avast 5. This is not the first time Avast provide this kind of false-positive, since, this is now THEIR BUSINESS PLAN: terrifying users to forces small editors to make some "certificates" or whatever. 6. I shits on Avast and Avast will go to hell. If you have put money in Avast, i am sorry for you. :smartass: 7. You should never put money in any antivirus, you better have to be careful of what you download and on what joint-piece you open.

By "Kill Avast" i would have say: Uninstall Avast. You choose...

This is a false positive... FileRepMalware is similar to DomainRep alert. All these alert are based on some "reputation" (this is what Rep stands for) according some a priori rules. The generale true rule is : "The editor of this software not paid our compagny to have a full audit of its software, so we let it at a low reputation power, because we need money" (i sumarize you the business model) My advice: Kill Avast, use another antivrus.

What malware ? Name, signature, version ? ... try with another antivirus, Avast is the champion of false positives...

New release available, see first page. Tell me if problem occure again.