Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I would like to gain some insight from some of you more knowledgeable game designers on what exactly the standards (or most commonly accepted conventions) for creating game assets (textures, models, etc.) are. Or rather if there is anything I have missed.
Here are some things I would like to know in particular...
Conventions for texture files.
Sizes (512x512, 1024x1024, etc.).
File type (JPEG, BMP, PNG, etc.).
Conventions for polygon counts of models (in a modern game).
What polygon count makes something a "low poly" model.
How to use a "high poly" model to generate a good normal map for a simpler model.
Proper way to design UV maps for an object.
Usually my unwraps look alright but nowhere near production quality. Is there a proper technique for this?
Proper way to generate normal maps in realistic fashion.
Also what would be some good applications for developing some assets. Particularly audio. I already use Blender for modeling.
Essentially I'm looking for the tricks of the trade, if anyone is willing to share of course =)
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Not sure if this method exists for data analysis... or even if I can word my question clearly:
If you took multiple transparancies with a map of the world on it, and then placed a 'very light' dot of color at places of interest (one dot on each transparency), when you stacked all of the transparancies on top of each other (in any order really), the 'very light' dots of color would combine to form 'darker' spots indicating increased interest in these locations. Likewise, the 'answer' would become readily apparant just by looking at overlayed maps with little to no calculations
Does this sound like any establised technique that you have heard of? And if so, what is its name?
Yes.
This technique is commonly known as heat map (Wikipedia), and a standard visualization technique.
This is popularly used with multivariate density estimation (Wikipedia).
Picture from Wikipedia, see File:Old Faithful Geyser KDE with plugin bandwidth.png (CC by-sa-3.0 licensed).
I would not call this "data mining". This is much much older. It's a visualization technique popular in statistics, though; but not so much an "analysis" technique.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have code to solve 2D truss structures implemented in C++ (as a console application).
I would like to add some simple graphics to it in order to visualize the initial structure and the deformed form. Example: http://people.rit.edu/pnveme/VenkatCOMSOL42/COMSOLTruss2D/ExtractingInfoinMATLAB_01.png
But I have no idea of how to add graphics in any way. How can I implement this kind of graphics?
Cross platform (preferred) or windows.
I doubt this is the answer you want, but to be honest, implementing plotting functionality isn't trivial, even if you're not doing it from scratch: you'll have to review a number of libraries, choose one, and get to grips with it.
Unless it's essential that the plotting functionality be integrated with the solver (e.g. for a product), I think you ought to consider simply exporting your results to, say, a simple ASCII matrix format that can be easily imported into a variety of environments with extensive and flexible plotting capabilities, one or more of which you probably already know (e.g. Matlab, R, Octave, etc.)
One option would be to generate a file which can be shown by another program. For example, generating SVG and using the browser to display it sounds like it would be good for your case, you can even easily include it in a report.
Check out SDL: http://www.libsdl.org/ It's cross-platform and has a ton of features. It maybe a bit overwhelming for your task, but I thought it was very easy to grasp when I was a newcomer.
There is a derivative of SDL that lets you draw basic shapes such as lines and points and is incredibly easy to use:
http://sdl-draw.sourceforge.net/
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I'd really like to know what knowledge do I have to pursue in order to create scripting languages from the ground up, probably using C++, maybe python, for those are the languages I know.
I've searched through SO similar questions, but nothing comes close of what I'm asking. I intend to understand language processing, not natural language, but scripts that doesn't have the focus on human readability, only on functionality.
My first idea, without any technical background, was to create a scripting language that assimilates a bunch of logical statements and making use of advanced built-in algorithms like logical reasoning, pattern recognition, neural networks an statistical analysis, in order to provide lots of useful(or not) information.
Sorry my bad english, I learned online, as almost everything I cited here :D and that kinda explains my lack of theorical background.
Thanks in advance.
"From the ground up" is a quite relative term, especially if you consider Python as the implementation language. I think what you are looking for is the implementation of a domain specific language (DSL). Good starting points might be this book or this one. DSLs are a wide topic, so if you provide more details, we might be able to give better tips.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
What is the recommended animated model format that a game programmer would load in OpenGL?
I have taken a look at .md2 and .3ds formats available at some OpenGL tutorials. However, it would appear that they are both fairly old. Is there any well-supported model format that a contemporary game programmer would prefer?
If you're a beginner, you should probably start with those formats. (Or maybe MD3, which comes after MD2.) Newer 3D formats don't typically supercede old ones by being objectively better, but usually by supporting more complex features. I'd recommend not making life difficult for yourself by picking a complex format.
If you're not a beginner, then you probably wouldn't be asking this question. ;) Professional developers usually have a bespoke model type that is specific to the engine they're using.
If you have specific requirements for your models then it's possible that there exists a model format that fits your needs, but MD2 and MD3 worked fine for commercial games so they'll probably work fine for you too. Generally you should approach this from the other side - what sort of models can my artists create, or what sort of models can I obtain? What format are they in? Can I use that format?
ms3d seems quite common. (there are links to the format on that page).
FBX is another. There is no good documentation for the format but there is an SDK to load it. On directx .x files would be another option but that's probably not so much use ofor opengl. (And it's not really that well supported on directx any more).
The most common format though seems to be to define your own application specific format that contains just what you need and use an exteral converter to convert to that format.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
In my free time, I'm working on a risk analysis application. I have already finished the mathematical and simulation engines, but I'm stuck with the design of the user interface. I want my application to be as easy-to-use as possible for Excel users, but I don't want to make it an Excel add-in, because Excel takes ages to load add-ins. So I'm going to use the old and venerable MFC.
I want to make these things easy in my application:
Modeling tasks:
Defining probability and uncertainty distributions
Defining mathematical relations between the variables
Separating uncertainty from variability (second-order risk modeling)
Validating the risk model
What-if (sensitivity) analysis
Data manipulation/display tasks:
Importing/exporting data from/to Excel and databases
Displaying nice graphs to the user
Do you know any guidelines I could take into consideration in the design of the user interface? The only examples I know, LINGO and Rockwell Arena, are actually examples of what NOT to do. Perhaps I will need to include a simple scripting language in the system but, in that case, it will be an option for advanced users, not for everybody.
1) For risk-specific functionality (at least, in financial world), one of the important guidelines is to allow easy viewing of summary level risk as well as easy drill-down to details (e.g. enterprise-wide down to security level)
2) Plus, don't forget standard GUI design guidelines - there's always Nielsen and there's JoelOnSoftware's Joel Spolsky's design book and series of articles.
High level,
make sure your controls are intuitive (do what the user expects them to),
minimize the amount of work (eye and hand movements) user needs to do to accomplish most frequent tasks,
Allow easy linking (e.g. no dead ends - if you are displaying a list of securities, make an easy way to jump from security's name to detail screen for that security)
Always always usability-test.