DPI Wizard

Very strange, same issue with the standalone version. Tried running as administrator and everything, and I can see through process monitor that the game tries to write to the file, but gets an error. Tried manually creating the file, deleting the whole Black Desert folder structure etc, but to no avail.

If you are not configuring the game according to the FOV that Auto FOV gives you, the calculations will be wrong. So you should always use the same FOV in the calculator as you have in the game, or else the calculations will be incorrect.

Nice, removed the notes now.

Dynamic with the default values are a perfectly viable option, but you can't compare the results form this with any random calculator elsewhere.

Correct, but make sure you are using the Auto FOV set to Hdeg 16:9 and 103 to automatically fill in the correct FOV to use for these games. All methods can be used, it depends on what you want to achieve. You should try the most common methods (like MDV 0%, 100%, 133.3334%, MDH 100%) in a game like Apex, and see when one of them feel best for all aims. If none are good, then you should look into the other methods to see if they might suit you better. Their descriptions are in the instructions.

That's probably it. Actually I see that the Steam client doesn't save the sensitivity between sessions, so it's probably a bug. I'm getting the standalone client now to verify.

The sensitivity slider is not accurate, expect some discrepancy. View full update

Both these are added.

It's already added as a special option when you select Quake 1

I don't know if this is region based or old entries that are not in use anymore, but I only have the gameVariable.xml file directly under %USERPROFILE%\Documents\Black Desert\UserCache\, and all it contains is this: <CheckQuestList Version="1"/> <QuestSortType Version="1"/> <QuestSelectType Version="1"/> <QuickSlotData Version="2"/> <ShortcutKey Version="15"/> <ChattingMacro Version="2"/> <UIData Version="2"/> <GameOption Version="1"/> <EquipSlotFlag Version="2"/> <BlockList Version="2"/> <MessageFilter Version="1"/> <GameOptionGlobal Version="2"> <ChatLanguageType Value="1"/> </GameOptionGlobal> <UIValue Version="4"/> <VoiceChatInfo Version="2"/> <PetInfo Version="2"/> <SkillCommandLock Version="1"/> <SkillCoolTimeSlot Version="1"/> <ItemLockedInInventory Version="2"/> <QuestOption Version="1"/> <UISettingPreset Version="1"/> <PetOrderList Version="2"/> <PetGroupInfo Version="2"/> <MemoList Version="1"/> <GameOptionCustomize Version="2"/> <ButtonShortcutsList Version="1"/> <FairySettingData Version="3"/> <ConsoleQuickMenu Version="6"/> <ConsoleWorldMapBookMark Version="2"/> <BlackSpiritSkillBlock Version="1"/> <JournalBookmark Version="2"/> <DynamicPanelScale Version="1"/> <VehicleSkillCommandLock Version="2"/> <SkillPresetMemo Version="2"/> <MonsterChaseData Version="2"/> <WorkerNameChange Version="1"/> <FairyQuickItemSlot Version="1"/> <RecentAlchemyHistory Version="1"/> <UISortOption Version="1"/> <ArtifactBagPresetInfo Version="1"/> <SelectCollectTypeChange Version="1"/> <PhotoMode Version="1"/> <WorldMapQuickScreenPosition Version="2"/> <AutoUseBuffItemInfo Version="2"/> <ChatProcessMacro Version="1"/> <JewelPresetNameData Version="1"/> I tried added the mouse sensitivity variables, but they didn't change anything, and were removed by the game on exit.

Works great, it's added now. The only suggestion I have is to show more decimals. 6 should suffice, and I see you can currently enter 6 and they will be applied

Just added! View full update

See the game notes for instructions on how to disable smoothing. View full update

See the game notes for instructions on how to disable smoothing. View full update

Can you be a bit more specific? Everything should be correct as far as I know.

Any tips on how to get scopes would be appreciated. I've tried getting the 4x from the west side of the tunnel on mt akiyama, but no luck.

All scopes should be treated solely based on their FOV, not what game they're from, what the hipfire FOV is in that game or how the game scales aims by default. A scope with FOV X should always have a 360 distance of Y regardless of game.

I've updated the FOV setting, but adding the scopes will take some time.

That's what Monitor Distance does, set the percentage to where on the monitor you want the movement to match, where 100% is the side edge for horizontal, or top edge for vertical. The coefficient should match your monitor distance, a placeholder value will be automatically calculated as a suggestion based on the conversion setup. In most cases you should use this value. As for ADS FOV, it depends on your preference, if you want the ADS to scale with your configured FOV, or for it to use a fixed FOV regardless of your configured FOV.

See this post