Author Topic: no targeting brackets  (Read 4114 times)

0 Members and 1 Guest are viewing this topic.

Offline leoben

  • 26
no targeting brackets
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?

 

Offline leoben

  • 26
Re: no targeting brackets
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

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: no targeting brackets
Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline leoben

  • 26
Re: no targeting brackets
Hm, game crashed before the problem surfaced, but here you go

[attachment deleted by nobody]

 

Offline leoben

  • 26
Re: no targeting brackets
one culprit i found - using the SSE build of 3.7.2 gets rid of the issue.

 

Offline leoben

  • 26
Re: no targeting brackets
scratch that, it didn't solve anything :(

 

Offline Yarn

  • 210
Re: no targeting brackets
What happens if you use a lower resolution like 1920x1080?
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: no targeting brackets
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?
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline leoben

  • 26
Re: no targeting brackets
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?

 

Offline Yarn

  • 210
Re: no targeting brackets
Can you try the latest nightly build (at 4K resolution, of course)?
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline leoben

  • 26
Re: no targeting brackets
Tried build 11296 - same issue.

 

Offline Yarn

  • 210
Re: no targeting brackets
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]
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline leoben

  • 26
Re: no targeting brackets
nothing. Same.

 

Offline Yarn

  • 210
Re: no targeting brackets
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]
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline leoben

  • 26
Re: no targeting brackets
Do I put this under BP2/data/tables as well?

 

Offline Yarn

  • 210
Re: no targeting brackets
Yes. If the other table is still there, overwrite it.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline leoben

  • 26
Re: no targeting brackets
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.

 

Offline leoben

  • 26
Re: no targeting brackets
also just tried selecting no mods at all, targeting looks good.

 

Offline Yarn

  • 210
Re: no targeting brackets
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;
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline leoben

  • 26
Re: no targeting brackets
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.