Source codes of the shaders could help in modding the graphics.
Modders who wrote new shaders for Oblivion or for Morrowind
should know more about these issues.

Addition of tesselation support of DX11 could be one mod.

1. Legal issues with intellectual property. Could be solved by changing the contract though, but that cost money of course.
2. Tessellation isn't as easy as "just add support to it". If support was added to it, it might as well be implemented (optional obviously). I don't think you realize the sheer amount of work that needs to be done for tessellation implementation.

1. That wouldn't be a problem since creation engine is Bethesda's intellectual property now. Benefits of using an in-house engine.
2. Well, DX11 is the support. The amount of work, let us worry about that.

Also, I can only speak for myself now but we would want more than open shaders(I'm editing Oblivion's native shaders right now.). Complete renderer library perhaps, or maybe partially since Gamebryo is out of the way now.

Wish all you want. It aint gonna happen!

nvm

Yeah, well, you know, that's just, like, your opinion, man.


Obviously. I think he talks exclusively about PC though.

Edit: I love both of your signatures. I wish we could live in a world where that was obvious for everyone.

What does it say? Sigs don't display on the mobile version.

It says the obvious, that we are forum posters posting about our opinions.

"...That's just my opinion, though."

"## Not Intended to be a factual statement"

PS. I know why your posts are one liners now. Sorry about earlier.

I wish I actually knew how to write DX shaders so I could lend a hand with getting it all up to where it should be, but I guess I'll have to be content working on the other end of things once others get tessellation and such working.

Thanks, no problem. I post pretty much exclusively on a touchscreen phone, so I keep my posts short usually. Trying not to speed up the inevitable arthritis!

Tessellation will likely need more than shaders, like new assets. It might need a complete overhaul which might be close to impossible but I can't say that because I have seen many impossible things becoming reality by modders.

You can learn about shaders via MGE and OBGE. It is pretty simplified to write shaders for both and I say it is really easy to jump and learn. Start with examining my shaders, they are the most basic ones.

wow your right where the heck did I see console? didnt todd say that skyrim would support dx11 but there wouldnt be that much of a difference

Tesselation support would -require- new mesh assets. The problem is what other runtime effects are being implemented. Throwing any form of runtime polygon generation into the mix takes skill across the board. The most common event is geometry ballooning, which is just as it sounds (tesselate the wrong model, and suddenly it explodes....or part of it does. And there is a lot of variables, so that it is impossible to predict accurately). The next biggie is possible loss of UV coordinates (this depends on exactly where in the pipeline tesselating and UV processing lay. After texture maps are applied, fine. If before, then the UV coordinates are no longer valid, and the texture will error out. Either just not load, or throw a console error that stalls or crashes the game). Depending on how the render engine is configured, you would either have invisible figures, or some default color like pure white. Of course you will also get into the issue of texture tearing and general crappy looking with tesselating.....just as you get when you take a bump map and use it as a displacement map without lowering its value =http://forums.bethsoft.com/index.php?/topic/1191391-wishing-for-open-source-shaders/a lot=. Plus it there are normal maps in use, there is -already- a form of software tesselation in use. DX-11 just makes it possible to use the GPU for the processing.

Until the game is in the modder's hands, there is no way to tell what can be done.

That would be cool, but you know what they say;

"Wish in one hand..."

lol

bliviongate:

It's the assests I'd have better success with. I know my way around modelling software, though I admit a weakness in UV mapping (the main hold-up for my current F:NV model).

And after a few forays into Basic, Java, Python and MEL, I think I can safely say I'm not much of a programmer.

Changing a text costs money?

F****** lawyers...

-Will there be finishing moves on Dragons?
-Will there be dissmemberment?
-Will there be an Werewolf Riding A Dragon While Holding A Spear easter egg WRADWHAS FTW

We'll never get it. But! I will be pretty happy with rendering techniques papres! Really wish to know more about "how Skyrim is rendered"))


R u sure? As far as I know, it would requie just 1 new asses per object - displacement map, which could be easily generated using normal maps, that should be in the assest in release.
Geometry shader eats that map and generates new tris within borders of older ones, UVs are interpolated between verts. Then vert shader eats new data and repform projection. Then pixel shader eats projected pixels and fill them with color. So, it's all done with just one run _while_ object is drawn. Where's the problem?


Lolwhat?! Normal mapping is just a displacement of texture coordinates reading + lightning applying, NOT a tesselation.
Tesselation means creating as much new polys to detail surface, as you want (until you hit low FPS barrier). Normal maps are to create fake for this.
Cheer me up, run in wall.

As far as I see, the only possible barrier is compiled shaders instead of sources, written on HLSL/GLSL/Cg in game assets. And locked packing, sure))