sedenion

In the Software Context properties, Installation Batches tab, you have a delete button. You can also simply delete the file within your Context folder... No guide, anyway you can easily deduct by opening an already existing package, watching the structure inside and the .omp XML file. The version is parsed from the file name, it must be at the very end of the file name, preceded by the v letter (either capital or not). ex : My_Package_v1.zip; My_Package_V1.2.zip; My_Package_v1.2.3.zip; The definition XML file must be UTF-8 encoded, especially if description embed non-ASCII characters... Supported image format for snapshots are : jpeg, png, bmp, gif.

To avoid user to download the wrong version, you should remove the undesired entries from the repository. The repository editor provided with OMM is far more advanced than the OvGME one, it allow to open an existing repository XML file, to add, remove and edit entries individually, then save a modified version. Another, more advanced method, is to create a meta-package with proper dependencies to all proper packages versions to be downloaded. This way, assuming you properly edit meta-package dependencies, you can tell people to download the metapackage, this will download (then install) only the desired packages, in order to satisfy the dependencies.

Hi, After almost two years of developement, here come the first official non-beta release: Welcome to Open Mod Manager version 1.0. Actualy, this release simply includes all the previous fixes and changes of the 0.9.9.x hotfixes cycle, plus some minor fixes. So, this will not change much if you allready downloaded the latest 0.9.9.8 "hotfix". Anyway, here the changelog for this version, from the last "main" version 0.9.9 of feburary: Fix and optimize markdown rendering Fix loading JPEG files may cause application to crash Fix and optimized image processing Fix deleting package may crash application Fix Repository Package parse failing due to 'xxhsum' tag not properly handled New support of paths with non-ANSI characters for ZIP file I/O Fix download low performances on large files over high-speed network Added bypass of access denied for network folders which access cannot be properly evaluated Fixed newly created Software Context not properly selected after Wizard dialog closed Fix potential memory leaks when closing software context Update embedded libcurl library to version 7.83.1 Update embedded miniz library to version 2.2.0 For who that already installed any previous version: As usual you can simply download and launch the setup that will overwrite previous files. However, this release upgraded to libcurl 7.83.1 which embed libcrypto and libssl in its main .dll file, so, the following files are no longer needed and can be deleted from the installation folder: 64 bit build: libcrypto-1_1-x64.dll and libssl-1_1-x64.dll 32 bit build: libcrypto-1_1.dll and libssl-1_1.dll As usual, details and download link are avaiable in the first page of this topic

I can confirm the big bug in le 0.9.9.6 version, but concerning problem with certain characters in the path, please retry using the very last release (0.9.9.7). Explanation: the 0.9.9.6 was released to fix a zip library files access failures due to a bad charset conversion of the file path. This specific bug was fixed, but this introduced this new bug of zero-sized compressed files... So, it is possible that everything work properly with the 0.9.9.7.

Hi, You do not have to create RTF description, you have to write description in plain text (ideally UTF-8 encoded, but Windows-1252/ISO-8859 is also supported), but using the Markdown syntax: https://www.markdownguide.org/basic-syntax (The RTF format is used only internally, dynamically generated to render formated text into the window control)

Sorry for the delay. I confirm the bug in the latest hotfix. I will investigate. Anyway, this should work properly with previous versions. EDIT: Bug fixed in the latest hotfix 0.9.9.7 If you encounter bugs, please do not hesitate to open an issu in Ggithub, I have better notifications than in this forum.

That's why you have errors. You must include ModDX++.tmh file AFTER the target.tmh file, not before, and certainly not inside: include "target.tmh" include "modules/ModDX++.tmh" Then, you must call the "InitMoreDX()" function (with propers parameters) instead of the "Init()" function within your main() entry. Everything is explained inside the ModDX++.tmh file, as comments. int main() { if(InitMoreDX(64, &EventHandle, CREATE_JOYSTICK)) return 1; } In the above example, 64 is the count of buttons of the virtual joystick to create. You can create a virtual joystick with up to 120 buttons. Other parameters are the ones of the usual "Init" function. Anyway, if you are not familiar with programming, I encourage you to simply use my ready-to-use mapping script, and, if you want, modify it as your tasts : https://www.digitalcombatsimulator.com/fr/files/3318341/

The version is 0.9.9 but for reason I absolutly don't care now, when released hotfix the tag becam 0.99.N. The 0.99.N are new releases corrected of the previous 0.9.9. To be clear and simple, go here and download the last published release : https://github.com/sedenion/OpenModMan/releases

As usual, the release was a bit too early. I just published a new 0.99.2 hotfix version that correct some bugs, but especially the Markdown renderer, which had serious problems with some ordered or unordered lists. Please see the post just before or the first page of this topic for download.

New 0.99.1 Release. https://github.com/sedenion/OpenModMan/releases This release bring a lot a new things and several bug fix: Fix command shortcuts still working when main dialog is not active. Fix scrolling for Overlap and Dependencies in Package Properties Dialog. Fix missing dialogs for package download errors. Fix Package Editor bad encoding of loaded/saved description text. Fix Package Editor not detected file extension when open an existing package. Fix Network Repository description never saved locally. Update embedded XXhash algorithm to the 0.8.1 version. Update embedded Pugixml library to the 1.12.1 version. New Uninstall tree - uninstall with dependencies - feature. New MD5 (md5sum) alogirthm support for repository files checksum. New Category field for Packages. New custom path or URL mechanism for repository files download. New improved message boxes and icons. New Installation Batch "Install-Only" execution mode. New ability to associate description and thumbnail for dev/folder packages. New improved UI with resizable frames. New Markdown parsing support for package description. Interface The main window is now splitted is two resizable frames whith the workspace as main frame, and package overview as bottom frame. Packages descriptions are now parsed as Markdown syntax and rendered in rich formatted text. The renderer use the RTF Format as rendered by WordPad (this is the same engine, the one supplied as standard with WinAPI since Vista)... So, not everything is beautifull (specialy tables and code or quote blocks, which do not resize properly). Folder-Packages (Developer/legacy mode) now support auto-detection of description text and snapshot image. Both description text and image file must be placed beside the folder inside the Library, and have the same name than the folder, either with or without the version string (this, to allow Mod developers to keep the same description text regardless the parsed version). For example, suppose the Folder-Package nammed My_Super_Mod_v1.2, a text file named My_Super_Mod.txt would be recognized as valid description for this folder. Obviously, My_Super_Mod_v1.2.txt will also work. If the file name exactly match the folder name (meaning : including version), it has priority. Network Repository Application now support MD5sum for network repository file checksum (previously, only XXHash3 was supported, a very good but not common hash algorithm). This, to allow third party to develop their own Repository Definition file in developement context where XXHash3 is not available. To specify MD5sum, you must use the "md5sum" attribute instead of "checksum" or "xxhsum" attribute. If people are interested to develop their own Repository generator, tell me and I give you proper specifications for thumbnail and descriptions encapsulation. Network Repository mainteners can now specify a wide variety of custom URL/Path/Subfolder for each package. The previous "Custom URL" implementation of the Repository Editor was a bit simplistic and were imposing to specify a full URL as alternative download address for the package. The new implementation is more flexible and smarter, building the final URL with completion rules. You now can specify either: An alternative subdirectory that will supersede the default subdirectory (eg. /custom/path) An alternative URL that will supersede the default base URL (eg. http://domain.tld/path) An alternative full URL to file that will replace any other default (eg. http://domain.tld/path/My_File.zip) Miscellaneous The installations Batches can now be defined as "Install Only". This feature was requested long time ago, then I finaly implemented it. When an Installation Batch is set to "Install Only", it does not uninstall any package and proceed as "additive install". This allow to combine multiple Installation Batches that will all performs their own additional installs withou uninstalling the previously installed packages. There is now a new "Uninstall Tree" fonction that allow to uninstall the selected package with all its dependency tree. Meaning, if a Package have a dependencies, the installed (and no longer used) dependencies of this package will be uninstalled. This is especially usefull with "meta-packages".

The LASTE Switch (PATH/ALT/HDG) has a special behavior in relation with the AP ENGAGE / DISENGAGE button. You can disable this behavior by setting the AP_MODULE macro to 0 in the Run_*.tmc file

This is a brillant idea... I did similar thing the old way by filing the origin piece to make something similar to your alternate model. I never understoud why Thurstmaster never did that. Unfortunatly, I do not have 3D printer...

Here : Maybe the moderation should move the topic in this subsection...

I did more tests and I finaly got the same strange behavior. I have both F18 and F16 grip, so I can switch and test with or without plug and the first thing I noticed is that despite the fact that the F18 grip is declared with "VID_044F&PID_0403" Serial ID in target.tmh, it seem that the physical device (the base) still have the "VID_044F&PID_0402" Serial ID wathever the plugged grip. And TARGET Always detect and select the "VID_044F&PID_0402" device as Joystick, with F16 or F18 grip plugged, and that is the only way that work. During my test, what I noticed is the following: If I let the base plugged to the computer, and witching from F16 to F18 grip, everthing work fine. But if I unplug with a grip, and replug with another, it seem TARGET Script Editor did not properly detect the "VID_044F&PID_0402" anymore... To get thing working again, I simply started TARGET GUI, which seem to force some device detection.

I suspect you installed outdated software, driver, or firmware version. Did you upgraded firmware of both devices ? What are displayed firmware version for Joystick and Throttle ? What are TARGET Scritp and GUI software versions ? What driver version did you installed ?

1) Your TARGET log output is normal, the errors you see are normal and should be only seen as notices. VID_044F&PID_0402 is the UUID for F16 grip, if you have F18 grip it is normal it cannot be found. You can see that it found and select VID_044F&PID_0403 which is the F18 grip. So, everything is fine here. 2) If you downloaded the latest TARGET version, you indeed should also upgrade firmware of both Joystick and Throttle, have done this ? 3) If you use the F18 grip, within TARGET Script Editor you must map/configure the &JoystickF18 device instead of the &Joystick device. TARGET GUI Should automaticaly detect the F18 Grip at startup and show you the the stick device as an F18 grip.

Context is saved with the Context def file (.omc) which should logicaly lie into its Context home folder you created. So simply have to copy and move that folder where you want, then opening the context def file via File > Open menu.

New 0.9.8 Release. https://github.com/sedenion/OpenModMan/releases/tag/0.9.8 This release fix numerous small and annoying bug, add support for HTTP redirect follow and a new menu entry and shortcut for Mod makers that allow to directly load a package or folder into the Package Editor. Add support and automatic follow of HTTP redirect responses. Fix Network ListView columns click wrongly pops up contextual menu. Fix Network ListView not properly redrawn after item sorting. Fix Network Abort button not properly enabled at download start. Fix Package Editor not properly clear properties of modified existing package. New menu and shortcut to load seleted package in Package Editor. Fix not working delete repository button of Network tab. Fix overly long warning messages with huge packages list.

You can't, the Mod is only compatible with earlier versions, and there will be no new version of the Mod, because: The last rework by Razbam correct almost all problem this Mod targeted. The new "vector" way to draw most cockpit indication elements disqualify all texture work by definition, rendering quality (such as antialiazing and filtering) can only be enhanced or fixed by ED team.

I can only tell you to verify by yourself the files in the zip file and in the game folder, try to replace them manually. Or use Open Mod Manager to install mod, this is a better usage...

If you don't use OvGME nor OpenModManager you have to unzip the content of the M-2000C_-_Sounds_Fix_v1.3 folder (Mods and CoreMods), not the entire zip file.

Yes

Ok, I found your problem. If you send HTTP request to https://snakeice.it/ovgme/527/ your web server reply with a redirect, this is the 168 bytes downloaded here, which is obviously not the XML file. You should set up the final URL with www to prevent redirect and everthing work fine : https://www.snakeice.it/ovgme/527/

Yep, this should work fine.

It seem you did nothing wrong, I just tested it and it works... except the Download Path, which should be empty (or just /) in your case, since the base URL for repository definition (xml) is already where files are located.