I use Linux Ubuntu and need a good software to reduce the file size of the screen shot and add multiple shots in one image is there anything out there?
Hi all. What i gotten so far is:
I have exported my model from blender to sauerbraten as an md3
(i have like 3 different exporters (md3, md3 + shaders, 16 oct md3 or something like that))
Is md3 the best file format to export and import for me? Will it make things more complicating?
Or will md2 or another one suffice?
-----
Keep in mind that:
- I just want the model to appear in sauerbraten as a movable mapmodel
(wich i have managed so far)
- Optionally i want to be able to load skin.jpgs unto different parts of the mapmodel
(wich i have managed so far)
-This mapmodel should react to the sauerbraten lightning.
(wich i have NOT managed yet)
For now: my mapmodel WITHOUT skin.jpgs is just looking plane black,
no mather how many lights i put around it, no mather how many times i type /calclight or /patchlight
in sauerbraten. And WITH jpgs the skin.jpgs do appear, but they also do not react to the lights around them, wich makes the form of my mapmodel very very unclear.
-----
How will i be able to solve my problem? That is: the mapmodel's form is unclear,
probably because my mapmodel is not responding to the surrounding lights.
How to make my mapmodel respond to the surrounding lights?
- Is it something that should be written in the map.cfg?
- Is it something that should be written in the md3.cfg?
- Is it because i faulty exported my model? Not clicked an option during exporting?
- Will it be solved by exporting in a different format?
- Will i have to add new stuff to my model in blender? Or delete stuff?
Basicly: what will i have to do?
Thank you very much for reading and or commenting!
Happy modelling and enjoying blender and sauerbraten!
I've finally got the Linux version of Sauerbraten and it works great, I've seen the FPS go up to 200 on high quality settings. However, ten to fifteen minutes into the game it crashes. It usually goes windowed and refuses to respond, but it does a lot of unpredictable things- sometimes is spontaneously quits, and it once completely logged me off. I'm sure the crashes occur independent of my input- it's crashed when I'm standing still and when I'm computing lightmaps. It also crashes in between songs. This can get extremely annoying, especially when I'm playing multiplayer. I do have a few clues, however:
-every time I kill the process my wifi signal is low.
-When the error causes it to spontaneously quit, the screen is out of proportion- I can't reach the bottom of the screen with my mouse.
-I was on the map Caves for about a half hour and it didn't crash.
I have absolutely no clue why this happens. If you guys could help me out that would be great; otherwise, I guess I can wait for the Linux Trooper Edition.
Most of these are from a wikihow page, with some modifications and clarifications- Just thought I would point that out there before somebody else noticed and started screaming "PHONY!"
"Criticism is to improve oneself and ones life, but not to insult or disgrace someone."
We use criticism as a system of finding and correcting possible faults to achieve a better end result.
If done properly, criticism is a good way to help us all improve our work by getting bits of feedback from other people, and their thoughts to help better the product.
If criticism is not done properly, for example: by one who is not a mature, diplomatic person, it may backfire. Backfired criticism leads to what may appear to be personal attacks or vastly opinionated arguments.
1: Make sure you have a good understanding of what your criticizing before you do such. Put yourself in their shoes, see things how they might see them. Think how you would like to be treated if this was your own content and other people were criticizing it.
2: Criticism should address any unclear areas and end with ways to fix them or improve them. Saying "The stairs suck," Is not criticism, it's an opinion. Instead say, "You get hung up on the stairs, this could be fixed by clipping each step."
3: Address the good things along side the bad. Do your best to refrain from making the person who's work you are criticizing feel like crap. For an example "The stairs need a lot of work, though the architecture supporting the ceiling is quite well done." This complements the work but also shows where a problem lies.
4: Do not criticize the Person for their work, criticize the work.
One great mistake is to point out the errors of the person and not their work, refrain from insulting people or putting them down because you dislike their content.
5: Don't use the word "You," as it can make what your saying seem like a personal attack, even if your not intending it to. Odds are the person will reply defensively. This is a common thing that is prone to start arguments, like that of which occurred in a node here not long ago.
As an example "You made a large error on the wall that causes players to get stuck," This could be changed to "There is an error in the one wall that causes players to get stuck." Some people will put emphasis on the "You" when they read it which sometimes make it seem more like an accusation.
6: Check over what you've said before you post it. Improper wording can lead to people interpreting what your saying as something different entirely. We don't have tone of voice in text, and if you word something improperly then someone may see it as an insult.
Imagine somebody saying "Great work!" First imagine it in a rewarding, kind tone, then in a sarcastic tone. The difference is made by the text leading up to the words, where as in real conversation the difference is shown in the way we say the words.
7: I can't put enough emphasis on this, but check your spelling and grammar! This goes hand in hand with the previous point, and a criticism that nobody can understand is of little use to anybody. If your horrible at english, or just typing in general, thats alright as long as you try your best. If all else fails then try an online app: for example www.SpellChecker.net
Once your done, read it over a time or two.
This post was read over three times and revised twice.
