alxunru

Already is and already has

The whole polytext thing definitely has its ups and downs. Our solution isn't perfect but for aircraft with large cockpits, where balancing texture resolution and performance is concerned, we like Guy, have gone the polytext route. I wouldn't necessarily call it a requirement for the tiny cockpit of the 737, and based on all of the previews that I've seen from Morten and crew, it certainly doesn't need it. Lovely panels there M

M 0.74...I stand corrected Thats what I get for looking up CR2 cruising speed on google!

You won't conduct a climb at 340 knots in a 777...let alone a regional jet. Your speeds are going to be as near as makes no difference 250 knots until 10000 feet, and then 290 knots for the climb till the mach transition (typically M 0.78 with the CR2) somewhere around 30,000 feet, atmospheric conditions depending. Cheers

Now I know...I should be working on the 777, but after giving Dozer a hand with some blender techniques, I was left with a set of windows and nothing attached to em. Two hours later and not actually wanting to go to bed even though I should have, this is what I'm left with. *shakes head* About all I can do is laugh Cheers

Old airplanes...like used cars. You never know what you're going to get in the cockpit. All part of the fun haha!

Goodness...I must be living under a rock. No idea you were working on this one. Model is looking fab!

Thank you and my pleasure

Garrettm30, Check this out. http://www.xpjets.com/2010/05/30/so-what-the-big-deal/ We go into comparison of with vs without normal / specular maps and try to show some of the ways that the effects can be used to enhance the appearance of an aircraft Cheers Alex

Great little read. Glad to see that you came to the same conclusions in the creation of normal maps that I came to for our purposes. I must be doing something right after all It really does add a new dimension to aircraft rendering in the sim. Thanks for sharing! Alex

Not to drag the topic of artifacts on, but I have had a bit of experience with the marching ants issue in the development of the 777. When normal maps first came out, I experimented with them and noticed the artifacts immediately on areas of the mesh that once had been clean. There were artifacts in strange places, like the tip of the nose, a couple of polygons on the top of the wingroot, and some on small details. Turns out (and I've confirmed this with Supnik), that these artifacts are the result of faces being mapped on edge, ie a line representing one polygon. The video card can't make sense of the normal mapped surface and sure enough, it spits out garbage. The severity of the effect is dependent upon lighting conditions, sun position, intensity etc. Here is what Supnik told me a couple of months ago in response to my inquiry. Take this a step further, its actually pretty easy to fall into this problem with the publicly available set of Blender scripts simply due to the sims rampant growth. Take a small antenna. More than likely I'm just going to planar map it as I'm not terribly concerned with distortion at that small size. If I've finished off the top of the antenna to be smooth, I'll have several vertices that are likely to be very close together. Consider that I'll be using a small texture area (call it the same pixel area that I would have mapped this to on a 1024 sized map) on a 2048 map. Blender's export scripts only export UV coordinates to four decimal places (believe me, I'd love to have 5 for the UV coords). That gives you 10000 possible coordinates across a 2048 pixel surface. That sounds like plenty, until you have vertices that are closer to one another than 0.2 ish of a pixel. Doesn't take much math to realize that by increasing your texture resolution from 1024 to 2048, you've effectively halved your UV coordinate resolution. The exporter will round your tightly packed UVs off to the nearest decimal, and because of that they can be plotted to the same texture space. It is why the tip of the 777 nose and tip of the screwdriver tail exhibited the marching ant syndrome. If you UV map intelligently, these kind of pitfalls can be avoided relatively painlessly. You might need to do a little bit more texture work, but the final textured surface is always going to be better off for it. And do note that you're only ever going to see these artifacts if you have a normal map in place. No normal map, no problem. Here's a quickie test to demonstrate more or less whats going on. Hope that this helps people out Cheers Alex

oh hello ;D Awesome comes to mind. Fabulous texturing! Cheers Alex

Made me laugh

Haha, I believe it lol. Looks great!