Skip to content
GalaxyMaster2 edited this page Oct 30, 2020 · 4 revisions

Welcome to the map inspector wiki!

If you are wondering how a particular function of map inspector works, this should help clear it up!

Just pick the appropriate section below:

basic setup
preview window & controls
understanding errors


Basic setup, slider subdivision

Slider Setup

In most cases you won't have to adjust this setting from the default value of 1/8. The value of this setting needs to be between the lowest slider precision used (usually no lower than 1/12 or 1/8) and the highest precision used for consecutive non-slider notes of a single color (for example, 2 blue notes 1/4 apart, equivalent to a 1/8 stream). Therefore you only need to adjust this setting if you use sliders with a precision lower than 1/8 or if you use consecutive non-slider notes of a single color less than 1/8 apart.


Using the Preview Window

Preview Window

Controls

You can navigate around the preview window using your mouse and/or keyboard:

  • scrolling moves the track forwards or backwards
  • clicking on a block or beat number will center the preview around that point, as well as highlight any warnings or errors that occur at that time (see: error messages)
  • holding right click allows you to rotate the view, this can also be done with w/a/s/d
  • holding middle mouse allows you to smoothly scrub through the map

Note Highlighting

Notes are highlighted when they are involved in a given parity error or warning:

  • red highlights surround notes that are responsible for a parity error
  • yellow highlights surround notes that are responsible for a parity warning
  • black highlights surround notes that immediately precede a parity issue

for more information on how parity issues are flagged, see Error Messages

Parameters

Below the preview window are a selection of parameters that can help make your experience more comfortable:

  • render distance adjusts how far forwards and backwards from the center beat is rendered, if you are having performance issues try adjusting this first
  • time scaling allows more or less of a map to be brought into the render distance - if the notes seem too crowded, try increasing this
  • beat marker subdivision does mostly what it says on the tin, it can be adjusted anywhere between 1/1 (no subdivision) and 1/8 subdivision
  • perspective intensity changes how the notes scale as they get further from the camera - feel free to adjust this however you like
  • wall support currently has issues in chromium-based browsers involving long walls and high perspective intensities, so it is currently disabled by default, but in most cases it will work without issue

Understanding Error Messages

Error Messages

For a quick recap on mapping with flow / respecting parity by BSMG, see here

An error message is triggered when two consecutive notes require a wrist movement in the same direction as each other, which would mean that wrist-based players would need to reset their wrist to make both hits. Parity issues are flagged as either yellow warnings (some players may not be able to read or play a given pattern) or red warnings (a wrist reset is necessary). Clicking on an issue message will scroll the preview window to the error so that you can quickly see where it lies within the map. In the case of errors, the time required for a wrist reset will also be displayed, to help you make the judgement of how quickly a wrist reset needs to be performed if necessary.


Limitations

The algorithms used to determine errors and warnings are not perfect. While they will give the correct result almost all the time, there are still cases in which they can get it wrong. Particularly bomb resets and bomb movement are not always detected correctly. If you see strange errors or warnings around bombs, that could be the cause.