[leoben]

Hey gang - just installed FSO and BP2 fresh using the FSO installer, have a bit of a problem. If I use the BP2 mod, there are no targeting brackets around any of the ships I target. There's a lead indicator if it's not completely centered, but no brackets. also no targeting indicator where to shoot, no distance counter. This happens no matter which mission, but only using BP2 mod. BP and MVP2014 work fine. Any ideas?

[leoben]

Captured it on video. At the start of the mission, though i get flak, you can see the targeting bracket in the lower right jumping all over at first, then disappearing. Later I target the aeolus, but there are no lead indicators nor brackets, no nothin'.

https://amd.box.com/s/rlr32at6quu7a8xmb3hq5luv8d63q5r2

[AdmiralRalwood]

Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

[leoben]

Hm, game crashed before the problem surfaced, but here you go

[attachment deleted by nobody]

[leoben]

one culprit i found - using the SSE build of 3.7.2 gets rid of the issue.

[leoben]

scratch that, it didn't solve anything

[Yarn]

What happens if you use a lower resolution like 1920x1080?

[AdmiralRalwood]

Hm, game crashed before the problem surfaced, but here you go

No, it crashed exactly as the problem surfaced.

This is the same Int3() that was behind Mantis 3070, but that was fixed in r10868 and you don't seem to need to fly near anything for the problem to occur. About the only other thing I can think of that might be relevant is this:

Code: [Select]

Initializing OpenGL graphics device at 3840x2160 with 32-bit color...
You might be the first person to try running FSO at that resolution. As Yarn suggested, could you try running FSO at 1920x1080 just to see if you get targeting brackets?

[leoben]

Confirmed, this only happens at 4K. I tried the mission Aristeia, which begins a bit 'calmer'. The problem only starts when I select a target that is very close. Until I target Tevs that are far enough away, all's good. So it seems this is almost the exact same problem you linked earlier. Do you think someone will look into this?

[Yarn]

Can you try the latest nightly build (at 4K resolution, of course)?

[leoben]

Tried build 11296 - same issue.

[Yarn]

I have attached a file that is identical to BP2's HUD table except for the +Target Brackets entries, which have been modified so that the brackets are loaded the "retail" way. See what happens if you place it in blueplanet2\data\tables (create the folders if they don't exist).

[attachment deleted by nobody]

[leoben]

nothing. Same.

[Yarn]

So that didn't help. Now I want you to try the table that's attached to this post. It's just the 2014 MVP table--no changes whatsoever.

You didn't say that you tried playing without any mods, so can you do so if you haven't already? (This means playing without MediaVPs since they count as a mod.)

If the brackets work with the MVP table and don't work without mods, then the problem is most likely related to HUD scaling.

[attachment deleted by nobody]

[leoben]

Do I put this under BP2/data/tables as well?

[Yarn]

Yes. If the other table is still there, overwrite it.

[leoben]

Ha, this did it. Everything on the HUD is really small now, but I have proper targeting now.

BTW the 2014MVP mod worked fine, even BP1 worked fine, only BP2 mod had this issue.

[leoben]

also just tried selecting no mods at all, targeting looks good.

[Yarn]

I think I found something that might be contributing to your problem. Try playing BP2 with this build, making sure that you remove all HUD tables from your blueplanet2\data\tables folder:
https://dl.dropboxusercontent.com/u/89353583/FreeSpace/possible_4k_fix.zip

For those wondering what I did, I moved the call to gr_set_screen_scale() in HudGauge::resetClip() so that it occurs before the call to gr_resize_screen_pos(). Here's the patch:

Code: [Select]

Index: code/hud/hud.cpp
===================================================================
--- code/hud/hud.cpp (revision 11296)
+++ code/hud/hud.cpp (working copy)
@@ -1039,11 +1039,12 @@
 
  gr_set_clip(hx, hy, w, h);
  } else {
+ gr_set_screen_scale(base_w, base_h);
+
  hx = fl2i(HUD_offset_x);
  hy = fl2i(HUD_offset_y);
 
  gr_resize_screen_pos(&hx, &hy);
- gr_set_screen_scale(base_w, base_h);
 
  w = gr_screen.max_w;
  h = gr_screen.max_h;


[leoben]

Screwed it up again, but the behavior is slightly different now. The targeting brackets are now almost always in the upper left corner. Sometimes disappearing, reappearing. But it's definitely not where it's supposed to be.