|
|
Post some screenshots |
|
|
The briefing editor does seem to be pretty messed up, as the icons are all shown lumped into the corner. The grid actually looked okay to me, although parts of the background graphics were displayed over the white border at the edges of the briefing window. This is all with the version that has HTL off by default; with HTL on it won't load most missions at all. |
|
2004-05-18 21:21
|
Image1.gif (97,436 bytes) |
|
|
I uploaded a screenshot of this by the way. |
|
|
Assigning to RandomTiger since he's responsible for FRED_OGL. This will be obsoleted with wxFRED but it would be nice to have a stopgap fix. |
|
|
I'm willing to be that this is fixed already. Between Goober5000, Kazan, phreak's new stuff, WMCoolmon and myself, I think the worst bugs (both display and crashing) are fixed. Grab the new build, give it a test, and if it's better then lets get rid of this sucker. |
|
|
message sent to DG |
|
|
I'll take it for feedback. |
|
|
Assigning to phreak; some (perhaps all) of these have been fixed. Phreak, can you post an update? |
|
|
the grid lines and the actual points the ship selection spots are projected incorrectly due to HTL issues. I'll take a look, but its probably some deep underlying issue with the old graphics engine getting in the way. |
|
|
ok ships are rendering in the correct spots now. i'll call this fixed. |
|
|
ugh i thought they were, i recompiled and its still doing this. |
|
|
Are we sure this hasn't been fixed by recent FRED work? |
|
|
I'll say its about 90% done, the text is rendering out of position and all i think i'll need to do is change the FRED fov from 0.5 to something like 0.45 or something. I'll look at it this week. |
|
|
Oh, don't change the FOV please. :( How much is the text out of position? |
|
|
its easily noticable at long distance or when the object is near edge of the screen. It looked really bad when the fov was 0.75, which is when i noticed the retail fred FOV was 0.5, so perhaps keeping the non-htl fov at 0.5 and setting the htl fov to perhaps somewhere between 0.45 and 0.5 may fix the issue. edited on: 08-31-05 09:51 |
|
|
That shouldn't be a FOV problem though. I mean, changing the FOV may fix it but it would only hide the symptoms. The real problem is how to calculate the text position. |
|
|
well its a matrix problem either way, since the text position is computed using the old non-htl functions. We're probably just sending the wrong values to gr_set_proj_matrix() |
|
|
Any more progress on this, phreak? |
|
|
ill get around to it friday since im really busy until then. |
|
|
set to 0.485 since it seems to stop the text from moving. looks like fred is ready for 3.6.7 |
- Anonymous
