Game size perspective versus real life.

[bustr]

In the past year I've gotten access to more photos of gunsight reticle from WW2. One specifically from inside the cockpit of an F4U-1D. Since we know the collimator projected image will remain constant inside of the field of view for the reflector plate. Based on the NAVY Mk8 hash marks of 5Mil increments in the photo, the prop blade is 32Mil - 35Mil wide.

Assuming the in game dimensions of things are a scale decided on by it's creator, which we accept everything is proportional to the real world using the dimensions of known objects around the game. And I build my gunsights to 512x512 2pixel = 1Mil. To which a mil file has to be associated with 256 in it so a 100Mil ring shows as 100Mil in all gunsights. I had to increase the Mil file number to 400 to adjust the Mk8 5Mil hash marks to measure the Aces High F4U-D1 prop blade at 32Mil-35MIl.

Now that I have increased the Mil file number to 400, in the game the NAVY Mk8 100Mil main ring is the same diameter on the F4U-1D reflector plate as the French OPL 39 main ring of 140Mil or 4RAD with 256 in it's Mil file. I've been testing the French 140Mil main ring for awhile, and it is a better lead shooting hold off guide than going with an AH default perspective 2pixel=1Mil 100Mil or 105Mil ring.
--------------------------------------------------------------------------------------------

A number of questions come to mind. Some are to the perspective scale of the game. Some are for ease of usability for players.

1. - At the default Mil file number of 256, measuring with the 100Mil main ring of the NAVY Mk8. The Aces High F4U-D1 prop measures 55Mil wide. While from the real world photo the prop measures about 32Mil-35Mil wide.  Does this matter to our game?

2. - Does it matter that when I test a 140Mil main ring in the game with 256 in the Mil file, the hold off timing for lead shots becomes easier making me wonder about our visual scale versus our time to target tables?

The NAVY in WW2 was very concerned about giving their pilots a main ring that facilitated hitting the A6m in it's turns using the AN/M2. So there is a relationship of the .50cal round to a 100Mil ring or effectively 2.9-3 RAD hold over. That's why the NAVY produced it's own licensed copies of the British MkII over the AAF early N-3 and it's slow upgrade from 35Mil 1RAD to 70Mil 2RAD rings. Japan started out with 100Mil.

 The AAF pushed it up to 101Mil in the N9. The British went a full 3RAD with 105Mil in the MkII early on. While the French went 4RAD in the OPL 39(1939) in the D.520 which had the Hiso 20mm shooting through the motor HUB. And the Yak engines are copies of French engines shooting a similar 20mm in which the OPL 140Mil gunsight works better for lead shooting in the game. See a pattern here?

**For cockpit visual perspective using a 140Mil ring, you end up adjusting your default forward view quite deep into the windscreen killing some of your peripheral vision. Cockpit visual perspective is at a premium in our game. You can see trade offs for playability taking place.**

3. - As I suspect, AH visual perspective is fixed by this late stage of the game and not to the ballistics TtTarget. So, if I want to provide a better time scaled gunsight reticle to players without confusing them with editing Mil files. Based on my testing with the French 140Mil OPL 39 and the WW2 photo allowing me to use the 5Mil tick marks in a real 100Mil Mk8 projection to measure the width of an F4U-D1 prop blade.
 
Do I go to the extra trouble to create scaled up Historic gunsight versions from the Aces High visual perspective?

Does any of this even matter?

Have I made readers log off and get drunk again?

[FLS]

I believe Hitech has stated that AH is modeled full size but may appear otherwise due to the selected monitor field of view. Wouldn't the apparent width of the prop in your photo be dependent on the field of view and position of the camera?

[bustr]

Changed the FoV to auto and 512 textures. Still needed 400 in the Mil file for the prop blade to be 35Mil wide just like the picture. I'm using 384 in my Mil files as a concession to other types of reflector plates and getting your face close to the windscreen bars. You can set a list of numbers in the Mil file and only the top number is parsed by the game when you spawn your aircraft. That's my solution to not needing to build "up sized" copies of each gunsight.

2pixel = 1Mil 512x512 mask in standard Hitech universe and Hitech units of measurment.

If time to target and G loads are real world numbers in his physics calculation, then 140Mil in 2p=1M is real world 3RAD based on time to target. That's why "Bag the Hun" never really worked right at 20 degrees and past with a 101Mil or 105Mil ring with 256 in the Mil file. While testing the French OPL 140Mil gunsight I built last year, I was surprised that it worked better based on "Bag the Hun". Messiah has gone through "blue thingy" gunsights with 140Mil ghost rings for me without knowing what I was testing all this time. He is pretty consistent landing 4-7 kills strings in his rides every sortie.

  35Mil = 1RAD
  70Mil = 2RAD
105Mil = 3RAD
140Mil = 4RAD

140Mil, never quite understood needing something as big around as the palm of your hand to aim with right in front of your face. The French OPL39 gunsight was nicknamed the lantern.

[earl1937]

Changed the FoV to auto and 512 textures. Still needed 400 in the Mil file for the prop blade to be 35Mil wide just like the picture. I'm using 384 in my Mil files as a concession to other types of reflector plates and getting your face close to the windscreen bars. You can set a list of numbers in the Mil file and only the top number is parsed by the game when you spawn your aircraft. That's my solution to not needing to build "up sized" copies of each gunsight.

2pixel = 1Mil 512x512 mask in standard Hitech universe and Hitech units of measurment.

If time to target and G loads are real world numbers in his physics calculation, then 140Mil in 2p=1M is real world 3RAD based on time to target. That's why "Bag the Hun" never really worked right at 20 degrees and past with a 101Mil or 105Mil ring with 256 in the Mil file. While testing the French OPL 140Mil gunsight I built last year, I was surprised that it worked better based on "Bag the Hun". Messiah has gone through "blue thingy" gunsights with 140Mil ghost rings for me without knowing what I was testing all this time. He is pretty consistent landing 4-7 kills strings in his rides every sortie.

  35Mil = 1RAD
  70Mil = 2RAD
105Mil = 3RAD
140Mil = 4RAD

140Mil, never quite understood needing something as big around as the palm of your hand to aim with right in front of your face. The French OPL39 gunsight was nicknamed the lantern.

You make some good posts in this forum, but this takes the cake! How in world is an old guy like me, who barely knows how to turn on a computer and shut it down, suppose to compete with guys like you? No wonder I keep getting my A++ handed to me, I can't get the thingiemagiggy into the whatumaycallit!

[The Fugitive]

Neither can Bustr, he just talks a good game!   

[JimmyD3]

Neither can Bustr, he just talks a good game!   

Yeah but even with all that "gibberish" he does an excellent job of helping us out and keeping things anchored in reality.  Bustr

[wpeters]

In the past year I've gotten access to more photos of gunsight reticle from WW2. One specifically from inside the cockpit of an F4U-1D. Since we know the collimator projected image will remain constant inside of the field of view for the reflector plate. Based on the NAVY Mk8 hash marks of 5Mil increments in the photo, the prop blade is 32Mil - 35Mil wide.

Assuming the in game dimensions of things are a scale decided on by it's creator, which we accept everything is proportional to the real world using the dimensions of known objects around the game. And I build my gunsights to 512x512 2pixel = 1Mil. To which a mil file has to be associated with 256 in it so a 100Mil ring shows as 100Mil in all gunsights. I had to increase the Mil file number to 400 to adjust the Mk8 5Mil hash marks to measure the Aces High F4U-D1 prop blade at 32Mil-35MIl.

Now that I have increased the Mil file number to 400, in the game the NAVY Mk8 100Mil main ring is the same diameter on the F4U-1D reflector plate as the French OPL 39 main ring of 140Mil or 4RAD with 256 in it's Mil file. I've been testing the French 140Mil main ring for awhile, and it is a better lead shooting hold off guide than going with an AH default perspective 2pixel=1Mil 100Mil or 105Mil ring.
--------------------------------------------------------------------------------------------

A number of questions come to mind. Some are to the perspective scale of the game. Some are for ease of usability for players.

1. - At the default Mil file number of 256, measuring with the 100Mil main ring of the NAVY Mk8. The Aces High F4U-D1 prop measures 55Mil wide. While from the real world photo the prop measures about 32Mil-35Mil wide.  Does this matter to our game?

2. - Does it matter that when I test a 140Mil main ring in the game with 256 in the Mil file, the hold off timing for lead shots becomes easier making me wonder about our visual scale versus our time to target tables?

The NAVY in WW2 was very concerned about giving their pilots a main ring that facilitated hitting the A6m in it's turns using the AN/M2. So there is a relationship of the .50cal round to a 100Mil ring or effectively 2.9-3 RAD hold over. That's why the NAVY produced it's own licensed copies of the British MkII over the AAF early N-3 and it's slow upgrade from 35Mil 1RAD to 70Mil 2RAD rings. Japan started out with 100Mil.

 The AAF pushed it up to 101Mil in the N9. The British went a full 3RAD with 105Mil in the MkII early on. While the French went 4RAD in the OPL 39(1939) in the D.520 which had the Hiso 20mm shooting through the motor HUB. And the Yak engines are copies of French engines shooting a similar 20mm in which the OPL 140Mil gunsight works better for lead shooting in the game. See a pattern here?

**For cockpit visual perspective using a 140Mil ring, you end up adjusting your default forward view quite deep into the windscreen killing some of your peripheral vision. Cockpit visual perspective is at a premium in our game. You can see trade offs for playability taking place.**

3. - As I suspect, AH visual perspective is fixed by this late stage of the game and not to the ballistics TtTarget. So, if I want to provide a better time scaled gunsight reticle to players without confusing them with editing Mil files. Based on my testing with the French 140Mil OPL 39 and the WW2 photo allowing me to use the 5Mil tick marks in a real 100Mil Mk8 projection to measure the width of an F4U-D1 prop blade.
 
Do I go to the extra trouble to create scaled up Historic gunsight versions from the Aces High visual perspective?

Does any of this even matter?

Have I made readers log off and get drunk again?

I would love to help you but no very little. Could get some photos or video showing what you mean.  I dont now any thing about how to use the gunsights and would appreciate some time in the TA or video teaching about them. I have always wondered how to use them. Appricate any help you can give me. Because I am horrible at deflection shots.

[hitech]

If no file exist the default mil is 128 not 256.

So if you are using a 256x256 texture 2 pixels = 1 mil.


Moving your head forward or back will change the mil size of the prop because your view point is closer or farther away from the prop.


HiTech

[Megalodon]

A number of questions come to mind. Some are to the perspective scale of the game. Some are for ease of usability for players.

Only question that comes to mind for me is ......where is the French plane to go along with that sight?... 

Have you considered making a <laymen> tutorial to go along with your excellent sight package explaining how each is supposed to work?  You have such a grasp of of the subject......

I think your contribution is great Bustr and HTC should implement all of your historic gun-sights, providing it's okay with you, in their next upcoming whatever <patch/revision/succulent>! 

 

Thank you,

[pembquist]

upcoming whatever <patch/revision/succulent>! 

Cheeseburger. Upcoming cheeseburger.

[bustr]

Hitech,

Your original solution after the post by Baumer July of 2010 was 512x512 2pixel = 1Mil with a Mil file containing 256.

When I adjusted the mil file to 400, I tested at the HTC default head position to have the prop width be "7 of the 5Mil" Mk8 ticks wide. The prop at HTC default head position with 256 in the mil file is 55Mil wide. In real life the prop through the Mk8 in the F4U-D1 cockpit was 7 ticks wide viewed through that known standard of the Mk8 reticle(100Mil and 50Mil rings with 5Mil ticks between rings). Depending on the distance of the camera from the reflector plate in the 1945 photo, the width of the prop might vary 1Mil or so relative to the Mk8.

Have I been confused how to making my gunsights 100Mil in the HTC environment?

Does 512x512 with a Mil file and 256 in it not equal 256x256 2pixel = 1Mil?

Using the 512 and mil file format, offline at 600yds, the 180ft diameter target is 100Mil using similar triangles. Or 99.96719160104987 using Angular Mil.

I guess it's a "simple curiosity" that I had to increase the mil file size by 144 to have the HTC F4U-D1 prop blade match the 1945 photo. And coincidentally Messiah and I are getting better timing on lead shooting. So maybe 4RAD just gives a player a crutch to lean on if he wants to push his head forward of the default HP and save it. And for all I know Waffle likes "Fat Blades" for some reason.

I suppose a slider in the gunsight selection app to take the place of the mil file, allowing players to scale up or down would cause support nightmares.

Newguy: Waaaa, my gunsight is all funked up and tiny. You suck.......
Skuzzy: Were you playing with the size slider?
Newguy: ARrruuuuuhhh?????>@U@< 

[LCADolby]

I think on a 50" screen the 3Dcpit on the 109 can be measured within an inch of the real 109s cpit width.

How cool is that 

[Copprhed]

Pretty damned cool, since i use a 50" screen

[hitech]

Does 512x512 with a Mil file and 256 in it not equal 256x256 2pixel = 1Mil?

Your question is worded strangely.

A 512x512 texture with 256 in the mil file, will be 2 pixels per mil.

The mil file is simply the width of the texture in mills.

HiTech

[hitech]

Bustr: I just got your email. What is your question? Because different mill sizes for a prop only mean the view point is different.

HiTech