Yes. Dark.cfg. Read the new_config_vars.txt file in your doc directory, especially:

d3d_disp_2d_surf_mode <0 - 3>
only works in combination with "use_d3d_display", sets the method in which the 2D overlay (HUD) is handled,
default is 3 (hardware based 2D rendering and 3D rendering in editor). Using the default HW method should
significantly increase performance related to 2D/HUD drawing, especially at higher resolutions. If there are
problems with garbled HUD texts and "d3d_disp_force_rgba_atex" doesn't help, then it may be solved by changing
this to mode 0, 1 or 2.
0: software rendering (normal method for SW rendering)
1: software rendering (alternative method which probably ends up doing the same thing as 0)
2: software rendering (alternative method using lockable dynamic vidmem texture)
3: HW rendering (recommended/default)

use_d3d_display
use Direct3D 9 display system instead of the legacy DirectX 6 DirectDraw one.
Enabling this will automatically also enable "force_32bit".


Also, this might be of use, given the messages you're getting:

editor_water_alpha <alpha>
(DromEd only) alpha value to use when rendering water surfaces in editor solid view, when hardware 2D is
enabled, default is 0.5. The editor doesn't render water with the actual transparency as seen in-game because
for editing it's more useful to be able to see all geometry, and opaque liquids like lava would prevent that.
console command: editor_water_alpha <alpha>


You should also post your DromEd.log. That lists what your actual setup is and can help in figuring this out.