Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Store talk:Uplay

About this board

Not editable


uplay_install.state

2
Mirh (talkcontribs)

So.. I was having a problem with Anno 1800, where every launch was constantly buggering me about having to install the VS2015 redist (the thing was probably failing because I already have the new unified runtime).

I started to look for wherever they keep track of installed dependencies, and unlike Steam (which uses the registry) they seem to employ the aforementioned file in the root of each individual <path-to-game>.

It exists in a kinda mixed binary/strings format though.. And I really couldn't find anywhere where actions such as EULA-Denuvo, clearshaderfolder and uplay_firewall\Anno were physically defined. Anyway, moving away the file had a new one regenerate that solved my problem. By comparing them, I could get some (very stupid) glimpse into the syntax.

It seems like every entry's name is preceded by 3 bytes, with the middle one always being 0A. As for the redist entry ("redist" being the first 6 bytes here), the original one was 72 65 64 69 73 74 10 02 2A, fixed is 72 65 64 69 73 74 10 02 18 02 2A. In bold the part where the magic happens.

66.181.161.127 (talkcontribs)

uplay_install.state

Bowi (talkcontribs)

I'm experiencing tonight, but it seems you need to format your HDD to NTFS if you want to back up your games... I tried on an exFAT HDD with Assassin's Creed IV: Black Flag (and III) and now I have to redownload both games.

I downloaded "Liberation" to check whether NTFS would work, and it does. More to come...

(Basically, trying to locate a game which is on an exFAT partition will bring an error message, but it seems it happens even when you don't try to launch the game while it's backed up.)

Games command line parameters

2
Mirh (talkcontribs)

So.. After discovering Steam is itself passing parameters not to be required to Uplay games, I wondered whether executables weren't hiding more interesting switches.

Turns out many of the parameters you pass them, aren't actually "theirs" but Uplays's (which therefore gets in turn them handled)
orbit_orbit_pipe_name
orbituat
upc_uat
upc_dev
upc_local
upc_product_id
upc_uplay_id
upc_arguments
upc_exe_path
upc_game_path
upc_game_version
upc_working_directory
upc_uplay_game_starter_id
upc_steam_free_package_id
upc_steam_required_product_id
upc_steam_bigpicture_mode
upc_language
uplay_dev_mode_simulation_config
uplay_steam_mode
uplay_oculus_mode
uplay_vr_mode
upc_gfn_mode
orbit_uplay_pipe_name
uplay_session
uplay_overlay_no_ui
upc_overlay_disable_create_process_hooks
upc_preview_build
orbit_disable_exception_shield
orbit_launcher_log_dir
orbit_overlay_pipe_name
gamelauncher_wait_handle
gamelauncher_inject_pid
gamelauncher_inject_tid
uplayservice_perform_elevated_restart
uplayservice_perform_elevated_updates
uplayservice_perform_gear
uplayservice_perform_initial_install
uplayservice_perform_set_files_permissions
uplayservice_perform_updates
uplayservice_run_install_script
uplayservice_run_uninstall_script
uplayservice_uninstall_all_games
uplayservice_about_url
uplayservice_help_url
uplayservice_gear_output_file
uplayservice_get_hw_score
uplayservice_game_name
uplayservice_icon_filename
uplayservice_pipe_name
uplayservice_publisher
ucr_report_filename
ucr_hash
ucr_suspend
uplaycrashreporter_pipe_name
ucr_full_process_dump
Other may exist, but I couldn't find anything else with a quick string search across Ubisoft\Ubisoft Game Launcher\ exe/dlls
41.140.151.229 (talkcontribs)

-USEALLAVAILABLECORES -high

Mirh (talkcontribs)

Just saw this in the news.. may be not a big thing and I have not much time..

There are no older topics