Moderators: winston, another_commander
OK tried it, looks really good & I'd like to keep it for a while but unfortunately there are missing vertical/horizontal lines on some borders and also some numbers at 1360x768. I've seen things like this with the regular scanner at different resolutions so I suppose it's a core game issue.m4r35n357 wrote:Looking better & better, I'll try this one out today . . . .
Code: Select all
{ // red dot pipper from MilHUD
image = "reddot.png";
x = 0;
y = 0;
height = 32;
width = 32;
alpha = 0.55;
},
Man, you don't waste any time, do you? 
Edit: Just to be clear, the pictures in the post just above were added after I made this post.Cmdr Wyvern wrote:If I can see it, I can shoot it.
And therein lies the problem with using ssi as a sight. SSI paints a vision obscuring green disc that's near impossible to see through. While that's fine for getting initial target lock, for precision aim it needs to make that green blob more transparent, or get the hell out of the way.
I played with the ssi alpha setting, and honestly that doesn't work either. Alrighty then, it needs to get out of the way. Time to rethink the precision sight.
It's not a full cross; there's a center gap a few pixels in size. Targets in the middle are easily visible. Even then, the cross, like the pipper, has an alpha channel so it's transparency is tweakable.CommonSenseOTB wrote:On this I guess we can agree to disagree. Just to clarify, you did turn your overall alpha up from 0.75 to 1.0. The standard settings make the center of the ssi very translucent but you are right that the center being brighter than space makes it a touch more difficult to see extreme range oblects, though the contraster does compensate for that. Honestly, I find a full cross more distracting and obscures the far away target at least as much. With a single pipper, at least you know if you don't see the target and the reticle is red, then you are on target. When the target drifts slightly it becomes visible and is easy to instantly know how to adjust your aim. With a cross, it could be anywhere along the cross, sometimes forcing you to move off target to regain visual so you know which way the target has moved.Cmdr Wyvern wrote:If I can see it, I can shoot it.
And therein lies the problem with using ssi as a sight. SSI paints a vision obscuring green disc that's near impossible to see through. While that's fine for getting initial target lock, for precision aim it needs to make that green blob more transparent, or get the hell out of the way.
I played with the ssi alpha setting, and honestly that doesn't work either. Alrighty then, it needs to get out of the way. Time to rethink the precision sight.
Another problem has to do with how people aim. Some want to see the target and have a nearby reference mark to help line the shot up, some want to not see the target to know that it is lined up. The idea I have in my head right now falls somewhere in between.
Down the road there can be a selection of sights optimized for what one person finds specifically comfortable and practical for their aiming style.
As for the ssi, no worries, I'll come up with something for 2.1. When I do I will want your feedback.
That's definitely hitting homers. Yeah all is as it should be config-wise. I have a laptop with integrated graphics, which should run at 1366x768 but this locks up the whole machine. 1360x768 "works" though, so that is what I use. Even milhud does not display properly, but it's only a couple of missing scanner lines. As I said, I don't think it's anything to do with your OXP, I just have to live with these graphics until I get another computer (on the plus side, I get to use shaders) . . . thanks for looking into it though!CommonSenseOTB wrote:@m4r35n357: I've gone over and done tests with all the resolutions I could test using my cheap HDTV hooked by VGA to my netbook. All the resolutions show the hud appears properly on the netbook itself and I can scroll around when in those resolutions to see this. The view from the HDTV shows that it can display most of the resolutions. The resolution of 1360x768 is displayed properly. What I did note was the HDTV was displaying 1360x768 but the selection in the options of the game shows 1280x768 and yet it works correctly for me. Are your preferences set correctly in GNUstepdefaults? Can your monitor achieve a 1360x768 display mode or is it displaying in a different display mode that is close to the required display but is cutting off some of the screen? I believe there were 2 resolutions my HDTV displayed in a smaller display mode resulting in cutting off either the tops or the bottoms. A few others were not displayed at all because my HDTV is not capable of that high of a resolution. Perhaps you have a hardware issue. Another thought, are you playing in a window? Using a netbook with a native 1024x600 display I never play in windowed mode so I'm not sure if that could be an issue in this. Good luck solving your display problem.
Sounds like one of those infamously onery Intel graphics chipsets in play. Were it an ATI graphics chip, you'd be complaining about it's infamous inability to correctly render OpenGL.m4r35n357 wrote:Yeah all is as it should be config-wise. I have a laptop with integrated graphics, which should run at 1366x768 but this locks up the whole machine. 1360x768 "works" though, so that is what I use. Even milhud does not display properly, but it's only a couple of missing scanner lines. As I said, I don't think it's anything to do with your OXP, I just have to live with these graphics until I get another computer (on the plus side, I get to use shaders) . . . thanks for looking into it though!CommonSenseOTB wrote:@m4r35n357: I've gone over and done tests with all the resolutions I could test using my cheap HDTV hooked by VGA to my netbook. All the resolutions show the hud appears properly on the netbook itself and I can scroll around when in those resolutions to see this. The view from the HDTV shows that it can display most of the resolutions. The resolution of 1360x768 is displayed properly. What I did note was the HDTV was displaying 1360x768 but the selection in the options of the game shows 1280x768 and yet it works correctly for me. Are your preferences set correctly in GNUstepdefaults? Can your monitor achieve a 1360x768 display mode or is it displaying in a different display mode that is close to the required display but is cutting off some of the screen? I believe there were 2 resolutions my HDTV displayed in a smaller display mode resulting in cutting off either the tops or the bottoms. A few others were not displayed at all because my HDTV is not capable of that high of a resolution. Perhaps you have a hardware issue. Another thought, are you playing in a window? Using a netbook with a native 1024x600 display I never play in windowed mode so I'm not sure if that could be an issue in this. Good luck solving your display problem.