Forum posts
Doesn't seem "nit picky" to me. And, technically, it's exactly a double post.
Elon makes a good point.
Make the lever brush. Make another brush with the ORIGIN texture. Group the two brushes together. Then select them and tie them to a func_rot_button.
Make the lever brush. Make another brush with the ORIGIN texture. Group the two brushes together. Then select them and tie them to a func_rot_button.
Tie the lever brush to func_rot_button and set Distance (deg) to 72. Set Delay Before Reset to desired seconds to go back to normal.
No. No. 
And...? What was the solution?
What mod? !FLUID_YELLOW isn't in HL wads.
What did you find from Tommy's lump error?
Could it be the same as the HL error
WARNING: Texture lump "xxxxxx" not found ?
See Tommy's error page (Links).
WARNING: Texture lump "xxxxxx" not found ?
See Tommy's error page (Links).
Lookin' good, Madcow!
Carving is not the same as clipping. The user chooses where the clip lines go.
Sounds definitely like your card. The applications you mention all involve directx, heavy graphics use.
The players are never in that areaOkay. For that area of Pennsylvania, however, in general, you should see little, if any, sky through the trees from any height or position.
From the angle of your screenshot, you should see little, if any, sky through the trees.
http://images.google.com/imgres?imgurl=http://www.bolender.com/Frank%2520Lloyd%2520Wright/Fallingwater/June%252030%25202004%2520visit%2520to%2520Fallingwater/06%252030%25202004%2520019%2520Ronald%2520Bolender%2520Fallingwater.jpg&imgrefurl=http://www.bolender.com/Frank%2520Lloyd%2520Wright/Fallingwater/Fallingwater.htm&h=1600&w=1200&sz=612&tbnid=QJTaBeuOVwYlGM:&tbnh=150&tbnw=112&hl=en&start=4&prev=/images%3Fq%3Dfallingwater%26svnum%3D10%26hl%3Den%26lr%3D
http://images.google.com/imgres?imgurl=http://www.bolender.com/Frank%2520Lloyd%2520Wright/Fallingwater/June%252030%25202004%2520visit%2520to%2520Fallingwater/06%252030%25202004%2520019%2520Ronald%2520Bolender%2520Fallingwater.jpg&imgrefurl=http://www.bolender.com/Frank%2520Lloyd%2520Wright/Fallingwater/Fallingwater.htm&h=1600&w=1200&sz=612&tbnid=QJTaBeuOVwYlGM:&tbnh=150&tbnw=112&hl=en&start=4&prev=/images%3Fq%3Dfallingwater%26svnum%3D10%26hl%3Den%26lr%3D
Why? The graphics engine has to have a rule to decide which is the inside and which is the outside of a polygon.
It's called a "right-hand rule," Madcow. If you wrap the fingers of your right hand in the direction that the polygon vertices are created, your thumb points in the direction of the "outside" on the polygon.
Notice in Hammer that, if you point the fingers of your right hand in the direction of the positive X axis and curl the fingers to point to the positive Y axis, your thumb points along the positive Z axis.
Some graphics engines use a "left-hand rule."
It's called a "right-hand rule," Madcow. If you wrap the fingers of your right hand in the direction that the polygon vertices are created, your thumb points in the direction of the "outside" on the polygon.
Notice in Hammer that, if you point the fingers of your right hand in the direction of the positive X axis and curl the fingers to point to the positive Y axis, your thumb points along the positive Z axis.
Some graphics engines use a "left-hand rule."
Hmm. These make excellent HL2 architecture references, also!
Nice yard, SM.
Nice yard, SM.
XSI doesn't know when your finished, Madcow. You can export it and compile it anytime! In any case, you should look at your model in HLMV periodically, just as you would periodically look at your map in-game to see how it's coming. You may, of course, see the "backside" of polygons but it will also reveal problems that you don't see in XSI.
It needs to be textured is all. Save a version (a "throw-away" copy), texture it, export it and compile it.
It needs to be textured is all. Save a version (a "throw-away" copy), texture it, export it and compile it.
Try moving your lighting around. The black may just be shadow. Add some more lights.
You can also see how your model looks in-game. XSI doesn't light it the same as the game will.
You can also see how your model looks in-game. XSI doesn't light it the same as the game will.
I ran the bsp but it was too dark to see anything, even with the flashlight.
The rmf is too difficult to work with because you use all custom textures but:
1. clear up all the errors first. (empty func_wall and unknown target name) Looking for a problem when there are existing problems is never a good idea.
2. the multimanager targets itself. not sure why you do that but it can't do any good.
3. the entities (multisource, func_breakables and multimanager) look okay.
(I set up a quick map with the similar entities and it works.)
4. Try cordoning off the roof that has the beam and work with just that room until you fix the problem. Start by not triggering anything with the multimanager except the beam. Then add back in the other stuff later.
I ran the bsp but it was too dark to see anything, even with the flashlight.
The rmf is too difficult to work with because you use all custom textures but:
EDIT
I deleted the func_tracktrain and rebuilt it with the default func_tracktrain flags. You had some flags changed. Leave them at default. I rotated the func_tracktrain so it appears in the correct orientation when it spawns. Don't worry about the position of the beam. Put it somewhere in the middle of the room. It will move to the first path_track when it spawns.
I repositioned beam_1 so the beam spawns in the correct position rather than setting the height above track. Works fine.
The rmf is too difficult to work with because you use all custom textures but:
1. clear up all the errors first. (empty func_wall and unknown target name) Looking for a problem when there are existing problems is never a good idea.
2. the multimanager targets itself. not sure why you do that but it can't do any good.
3. the entities (multisource, func_breakables and multimanager) look okay.
(I set up a quick map with the similar entities and it works.)
4. Try cordoning off the roof that has the beam and work with just that room until you fix the problem. Start by not triggering anything with the multimanager except the beam. Then add back in the other stuff later.
I ran the bsp but it was too dark to see anything, even with the flashlight.
The rmf is too difficult to work with because you use all custom textures but:
EDIT
I deleted the func_tracktrain and rebuilt it with the default func_tracktrain flags. You had some flags changed. Leave them at default. I rotated the func_tracktrain so it appears in the correct orientation when it spawns. Don't worry about the position of the beam. Put it somewhere in the middle of the room. It will move to the first path_track when it spawns.
I repositioned beam_1 so the beam spawns in the correct position rather than setting the height above track. Works fine.
Just to be sure it's not machine-specific, you could post the map (or just the bsp if that's your preference) to the Problem map vault and see if others have the same problem.
I have an outboard USB drive I use to transfer large files from one comp to another. It came as FAT32. First time I tried to transfer from the new drive to my onboard drives, I got similar errors. Reformatted the outboard to NTFS to clear the problem.
Sounds silly, maybe, but you might try emailing yourself the file so it's not transferred from one type of drive to another.
Sounds silly, maybe, but you might try emailing yourself the file so it's not transferred from one type of drive to another.
May not be the same problem but I got similar errors copying from a FAT32 to an NTFS drive.
That's already in effect, ZL.
I like the pix! It may be the old tradition of painting the floors of battleships red to hide the blood. 
As always, your texturing and brushwork are excellent.
>> Personal preference << Use colors from the same side of the color wheel to create a consistent "theme" for texturing. Instead of blues and reds together, use yellows, greens and blues together. If you want to keep the contrasting blues and reds, throw in a little purple (blue+red) to tie the reds and blues together.
>> Personal preference << Use colors from the same side of the color wheel to create a consistent "theme" for texturing. Instead of blues and reds together, use yellows, greens and blues together. If you want to keep the contrasting blues and reds, throw in a little purple (blue+red) to tie the reds and blues together.
You can make your "springboard" a func_physbox, attach a phys_hinge to the edge about which you want it to rotate and attach a phys_thruster to the springboard (thrust force axis pointing up with both force and torque flags checked and apply locally).
Stand on the springboard, trigger the thruster and off you go.
With a springboard 192 units long and a force of 3000, I launched myself about 1500 units into the air. Like they say, it's not the fall that hurts.. it's that sudden stop at the end.
The rectangle beyond the springboard is a pool I'm constructing to land in. A 1500 unit drop is otherwise fatal.
Here's the contraption:
Smashing into the 1500 unit high ceiling hard enough to kill me:
Getting some major air:
Stand on the springboard, trigger the thruster and off you go.
With a springboard 192 units long and a force of 3000, I launched myself about 1500 units into the air. Like they say, it's not the fall that hurts.. it's that sudden stop at the end.
The rectangle beyond the springboard is a pool I'm constructing to land in. A 1500 unit drop is otherwise fatal.
Here's the contraption:
Yeah, beam starts off and not to be on until 5 seconds elapsed.
I stand corrected. (Too much HL2 output lately to remember my HL)
No, if you trigger the mm at 5, the next instance of the mm will immediately turn the beam on that the first instance just turned off.
0 seconds - beam on
5 seconds - beam off
10 seconds - spawn 2nd multimanager which turns beam on (at its own 0 seconds)
15 seconds - 2nd multimanager turns beam off (at its own 5 seconds)
20 seconds - spawn another mm
0 seconds - beam on
5 seconds - beam off
10 seconds - spawn 2nd multimanager which turns beam on (at its own 0 seconds)
15 seconds - 2nd multimanager turns beam off (at its own 5 seconds)
20 seconds - spawn another mm
Coming from you, Habboi.. I'm flattered.
I believe the multi-manager can trigger the beam directly. Trigger the beam on at 0 seconds. Trigger it off at 5 seconds. Have the multi-manager trigger itself at 10 seconds and check the "Multithread" flag in the mm.
PIMP - I've uploaded some maps to the Example map vault which use func_useableladder, phys_pulleyconstraint, func_movelinear, item_dynamic_resupply and other entities.
No fancy brushwork or precise entity positioning here.
No fancy brushwork or precise entity positioning here.
Use an info_target instead of a func_train.
How 'bout sharing the solution for your problem? That is, which flags (or lack thereof) caused the problem?
He can just scroll to the coordinates.
If you have a super scope yourself and have access to a digital camera, taking your own images is an option, also.
You're likely done this already but:
Google->Images - search for "SNES super scope" (without the quotation remarks.
There're a couple images in there that are flat. Might take some manipulation to skin a model with it but it should provide the basics.
If you're going to distribute your model, consider whether the image(s) you use are copyrighted.
You're likely done this already but:
Google->Images - search for "SNES super scope" (without the quotation remarks.
There're a couple images in there that are flat. Might take some manipulation to skin a model with it but it should provide the basics.
If you're going to distribute your model, consider whether the image(s) you use are copyrighted.
Error:Did you make a change to the bad face listed to see if that corrects the problem?
for Face 39 (texture c1a4_silo3) at...
It would appear this site could use forum moderators.
Go for it, RM! A good book and the samples included in most software packages will give you a good start!
I've used several template libraries and don't much care for them. They work pretty well when used strictly as designed but, as you demonstrate, they don't always provide consistent interpretations when referencing, dereferencing and casting are involved.
When you cast ( (char*)s, for instance) and reference (&s), I suspect the compiler reverts to standard C++ rules and your results are as expected. Casting is not an operator function (so is not overloaded) and, I'm pretty sure, referencing isn't usually considered to be overloadable, either.
(char*)s is the pointer stored at s, (char*)t is the pointer stored at t and they should be different.
(char*)s[0] would mean "interpret the first character of the array as a pointer" and, if the s[0] and t[0] are the same, the results would be the same.
&s would be the address of the variable s, not the addresss of the array. &s[0] would be the address of the array and &s[0]==s, not &s.
Guess that's why I stick to good ol' ANSI C++!
When you cast ( (char*)s, for instance) and reference (&s), I suspect the compiler reverts to standard C++ rules and your results are as expected. Casting is not an operator function (so is not overloaded) and, I'm pretty sure, referencing isn't usually considered to be overloadable, either.
(char*)s is the pointer stored at s, (char*)t is the pointer stored at t and they should be different.
(char*)s[0] would mean "interpret the first character of the array as a pointer" and, if the s[0] and t[0] are the same, the results would be the same.
&s would be the address of the variable s, not the addresss of the array. &s[0] would be the address of the array and &s[0]==s, not &s.
Guess that's why I stick to good ol' ANSI C++!
@CP: with respect to 's', I understand. I just generalized it since he said "given string," assuming he may have to input it, etc.
With respect to string comparisons, I disagree. There isn't a "string" fundamental variable type in C++. In the case of char pointers, the == op will compare pointers, not strings. That's why the compare function(s) must be used. Matrix[x][y] and the variable s are character pointers (i.e., address variables), not the strings themselves.
E.g.:
char s[5], t[5];
strcpy(s,"abc");
strcpy(t,"abc");
if( s==t ) cout << "equal" << endl;
else cout << "not equal" << endl;
if( strcmp(s,t)==0 ) cout << "equal" << endl;
else cout << "not equal" << endl;
The output will be:
:
because the pointers s and t are not equal but the strings they point to are equal.
With respect to string comparisons, I disagree. There isn't a "string" fundamental variable type in C++. In the case of char pointers, the == op will compare pointers, not strings. That's why the compare function(s) must be used. Matrix[x][y] and the variable s are character pointers (i.e., address variables), not the strings themselves.
E.g.:
char s[5], t[5];
strcpy(s,"abc");
strcpy(t,"abc");
if( s==t ) cout << "equal" << endl;
else cout << "not equal" << endl;
if( strcmp(s,t)==0 ) cout << "equal" << endl;
else cout << "not equal" << endl;
The output will be:
because the pointers s and t are not equal but the strings they point to are equal.
It appears that the scripted_sequence doesn't automatically get to the Action Animation phase with the "Start On Spawn" flag. It will only trigger the MoveTo. It has to be triggered to actually perform the Action Animation (and proceed to the Next Sequence, if specified).
Ah.. you're probably right, SM. Wow, don't I look like the nicest guy on earth. PTS - I apologize if there was any offense in my statement.
Anyway, as I recall, "string" itself is not a variable type so one would be starting with a two-dimensional array of char arrays.
Although Captain P's outline describes the matrix, you have to use functions to compare strings.
char* matrix[width][height]; // an array of char pointers
char s[6]; // the string to find
/... load the matrix and s with null-ended char strings .../
for(i = 0; i < height - 1; i++)
for(j = 0; j < width - i - 1; j++)
if( strcmp(matrix[i][j],s)==0 ) cout<<"string found at "<<i<<", "<<j<<endl;
strcmp() returns 0 if the strings match. If case is not important then use stricmp().
Anyway, as I recall, "string" itself is not a variable type so one would be starting with a two-dimensional array of char arrays.
Although Captain P's outline describes the matrix, you have to use functions to compare strings.
char* matrix[width][height]; // an array of char pointers
char s[6]; // the string to find
/... load the matrix and s with null-ended char strings .../
for(i = 0; i < height - 1; i++)
for(j = 0; j < width - i - 1; j++)
if( strcmp(matrix[i][j],s)==0 ) cout<<"string found at "<<i<<", "<<j<<endl;
strcmp() returns 0 if the strings match. If case is not important then use stricmp().
I'll buy you a bottle of vodkaHoohaw! That's my kind of programming!
Can't help much with the second task as I'm not sure what a "quadratic matrix" is nor what a "secondary main" diagonal is.
"Secondary main" seems like an oxymoron like "sanitary sewage."
earth's gravitational field isn't strong enough for you to levitate an object purely on magnetismNot sure what you mean by "isn't strong enough."
In any case, magnetic levitation is certainly possible (google for Shanghai Maglev).
A couple of suggestions:
1. Double-check that the areaportal faces do not both touch the same area.
2. Use the cordon tool or big block method to compile and run increasingly larger portions of the map until you find the offending areaportal.
3. When the problem is fixed, make small changes then compile and run to avoid similar problems in the future. Do not make further changes until your current map is errorless.
1. Double-check that the areaportal faces do not both touch the same area.
2. Use the cordon tool or big block method to compile and run increasingly larger portions of the map until you find the offending areaportal.
3. When the problem is fixed, make small changes then compile and run to avoid similar problems in the future. Do not make further changes until your current map is errorless.
desired_endpoint = 10000; //iterations you want
xn = 1;
n=1
do {
xnext = 0.5 * (xn + a/xn);
if( abs(a/(xnext*xnext)-1) < eps )
{
cout<<"for n="<<n<<": "<<xnext<< " is invalid"<<endl; exit(1);
}
// the exit in the 'else' assumes you want to
// quit with an invalid result
n++;
xn = xnext;
} while n < desired_endpoint;
xn = 1;
n=1
do {
xnext = 0.5 * (xn + a/xn);
if( abs(a/(xnext*xnext)-1) < eps )
cout<<"for n="<<n<<": "<<xnext<<" is valid"<<endl;{
cout<<"for n="<<n<<": "<<xnext<< " is invalid"<<endl; exit(1);
}
// the exit in the 'else' assumes you want to
// quit with an invalid result
n++;
xn = xnext;
} while n < desired_endpoint;
What time zone is South Africa?If you're running Windows, open up your Date and Time Properties and check the time zone.
Rory-
Are you making maps and running them in HL2?
If so, do you get the error when you compile/run any of the sdk examples?
That should not happen for maps run under the unmodified Source engine.
Are you making maps and running them in HL2?
If so, do you get the error when you compile/run any of the sdk examples?
That should not happen for maps run under the unmodified Source engine.
our eyes have a refresh rateSay what??
Methinks maybe I can turn my head faster than my corneae can adjust to a different depth.. but due to "refresh rate??" Persistance of vision, perhaps.
Refresh rate? Uh, I don't think so.
Yeah, that's been happening to me. Steam said a couple of my games are at 0% or preloaded. The percentage games start immediately (after going to 99% or "regular" status).
However, similar to your experience, "Preloaded" doesn't start for me, either, until I restart steam.
However, similar to your experience, "Preloaded" doesn't start for me, either, until I restart steam.
Seems you're looking for an env_speaker, which is a point (not a brush) entity.
http://developer.valvesoftware.com/wiki/Env_speaker
http://developer.valvesoftware.com/wiki/Env_microphone
Implies you create an env_speaker somewhere, give it a name and target it from the env_microphone to (re)broadcast sounds from the mike location.
http://developer.valvesoftware.com/wiki/Env_speaker
http://developer.valvesoftware.com/wiki/Env_microphone
Implies you create an env_speaker somewhere, give it a name and target it from the env_microphone to (re)broadcast sounds from the mike location.