I left Spark running and went to class for a few hours. Came back and the render context was not refreshing. Tried to select a few different tools and was met by very colorful artifact garbage covering the entire viewport. Restarted it and everything was normal again.
pSyk0mAnNerdish by NatureGermanyJoin Date: 2003-08-07Member: 19166Members, NS2 Playtester, Squad Five Silver, NS2 Community Developer
edited November 2009
<!--quoteo(post=1739937:date=Nov 24 2009, 11:42 PM:name=garvani)--><div class='quotetop'>QUOTE(garvani @ Nov 24 2009, 11:42 PM) <a href="index.php?act=findpost&pid=1739937"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->well so far we can come to the conclusion that a range of the Xseries of Radeon cards have issues.. as wel;l as the fx series geforce
now the x300-x1300 are a directx 9.0-9.0b generation card. Its only the x1300-x1600 that are a directx 9.0c compliant card, my money is on the fact that it needs to support direct x9.0c, nothing less. Can anyone confirm with a x1300-1600 that they arn't getting the black texture issue? (apart from sloppy joe, your problem is different) The geforce FX series is also a 9.0b generation card. i believe ive just cracked the problem lol.. wheres my cookie?!!<!--QuoteEnd--></div><!--QuoteEEnd--> No cookie for you!
They clearly stated that those 9.0b cards with lower shader version are supported by the game. In fact I didn't preorder with my crappy x700 until they finally answered this question and I wasn't the only one asking. Anyway, maybe you are right though that this difference is causing the bug.
And just to clarify this bug: The textures aren't missing, because you can see the full-lit parts of models that are representing lights. And I've also noticed that you can see the proper lit texture a few ms after adding the prop, before it turns all black, except of the light parts. In the texture-/ and prop-browser everything is black aswell.
<!--quoteo(post=1740307:date=Nov 26 2009, 05:19 AM:name=pSyk0mAn)--><div class='quotetop'>QUOTE(pSyk0mAn @ Nov 26 2009, 05:19 AM) <a href="index.php?act=findpost&pid=1740307"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->And just to clarify this bug: The textures aren't missing, because you can see the full-lit parts of models that are representing lights. And I've also noticed that you can see the proper lit texture a few ms after adding the prop, before it turns all black, except of the light parts. In the texture-/ and prop-browser everything is black aswell.<!--QuoteEnd--></div><!--QuoteEEnd-->
Yes I can confirm that. The fact that the lit texture is visible for a ms at prop creating makes me think that the card itself can handle the graphics, but the editor has something against it.
first of i dont know if this is a bugg or nor or if been posted.
But when you scale the windows (layer, edit, prop window etc) to maximize the view of work space it changes when you change tools. I like to have my layer window small (drag to the left side, like a thin line as i only use works as light, prop, map etc) as i run 1920x1080.
when you create a huge level with lots of details and lights, it starts lagging when you turn on lighting (even when you're just showing a small room with nothing much in it).
Is the editor also rendering stuff that is not in view range? Can anyone confirm my observation?
<!--quoteo(post=1740410:date=Nov 26 2009, 02:53 AM:name=Namron)--><div class='quotetop'>QUOTE(Namron @ Nov 26 2009, 02:53 AM) <a href="index.php?act=findpost&pid=1740410"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Everything is black for me too. I've got a Radeon 9800 XT (latest drivers). Textured, unlit:
<img src="http://photos-e.ak.fbcdn.net/hphotos-ak-snc3/hs050.snc3/13749_1210559677203_1625082982_556120_2423165_n.jpg" border="0" class="linked-image" /><!--QuoteEnd--></div><!--QuoteEEnd--> Sense you dont have any lights in there, make sure your Perspective mode is on Textured Unlit, instead of Lit.
pSyk0mAnNerdish by NatureGermanyJoin Date: 2003-08-07Member: 19166Members, NS2 Playtester, Squad Five Silver, NS2 Community Developer
<!--quoteo(post=1740476:date=Nov 26 2009, 02:18 PM:name=WhiteZero)--><div class='quotetop'>QUOTE(WhiteZero @ Nov 26 2009, 02:18 PM) <a href="index.php?act=findpost&pid=1740476"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Sense you dont have any lights in there, make sure your Perspective mode is on Textured Unlit, instead of Lit.<!--QuoteEnd--></div><!--QuoteEEnd--> Make sure you read what you quote..
I hope this bug gets fixed soon. I can't even check out all the juicy textures and props.
Seems like most people are having the same issues as me.
<!--quoteo(post=1739498:date=Nov 24 2009, 10:49 AM:name=Ghozer)--><div class='quotetop'>QUOTE(Ghozer @ Nov 24 2009, 10:49 AM) <a href="index.php?act=findpost&pid=1739498"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->following through the first video tutorial, when the guy draws the second rectangle on the wall, then shows you that there's two there by selecting one, then the other. then he extrudes it to create a corridor...
When I attempt to select one, then the other, it will only select the big 'back' wall, and wont allow me to extrude the smaller 'corridor' rectangle.
if I extrude the back wall, it leaves an unfilled outline of where the corridor rectangle is, but nothing selectable...
For the line on the wall issue, I found that I sometimes have to go over the line again, make sure the wall is actually flat, and be sure you have done all four sides of the block.
If it works you will then probably get the next issue I have been having, one side of the split wall will change to the default texture and become grey. Which means if I make a room, and then decided I would like another corridor or doorway in the room, I have to re-texture the room. Not fun when you are adapting a map and have spent hours texturing.
<!--quoteo(post=1739630:date=Nov 24 2009, 02:54 PM:name=Nazul)--><div class='quotetop'>QUOTE(Nazul @ Nov 24 2009, 02:54 PM) <a href="index.php?act=findpost&pid=1739630"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->i'm not having troubles at al which stuns me seeing so many people do ( im usually one of those... )
Ok so my problem is that when i made a wall> place a cylinder on it > extrude > make room on other side > it does not merge the cylinder with the new room.. and there is no option to do so.
though i seriously like the editor , somewhere i read it was like SkecthUp and Ed combined, second that and love it ^^
edit: ok found problem 2 :D when i'm looking in a particular angle the whole map goes unlit. haha random-ness<!--QuoteEnd--></div><!--QuoteEEnd-->
Yeah, I hate the I can't join two rooms together! You have to go into the relevant view (top, side, front, etc.) and draw out the place you want the hole in your second room, and cut it out. Kinda makes scenes when you think about putting rooms next to each other, but it wasn't exactly what I expected to happen. I expected the hall to join the room, and the wall that joins it to be separate so you could delete it if you needed to.
<!--quoteo(post=1739515:date=Nov 24 2009, 11:25 AM:name=Kerotan)--><div class='quotetop'>QUOTE(Kerotan @ Nov 24 2009, 11:25 AM) <a href="index.php?act=findpost&pid=1739515"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Spotlights crash the editor.
Just me or are others getting this?<!--QuoteEnd--></div><!--QuoteEEnd-->
Yeah same here, crashes every time, I am yet to see the pretty shadow effects. I have a NVIDIA GeForce 7600 GT, I know, from the manual, that the 7900 doesn’t work, could it be more of the NVIDIA range? Also, how will this effect my chances of being able to play the final game, will all the maps with spot lights in crash out? LOL! :S
EDIT: sorry, I forgot to say, I did acctually have spotlights working at one point, but not for long, and now I have no idea how to get them working again.
Nice to finally have the editor though, I hope the next patch fixes these bugs. Keep up the good work!
I seem to have 2 major problems with Spark, first one being the fact that the background's in my views ( 3D , Top , Left and Right ) are all black ... so its almost impossible to see the props in the 2D views, all the screenshots of spark that i see, i see those views with a grey background ... I even reinstalled and I'm still gettin the black viewport backgrounds.
My second problem is that in my top and right viewports the grid seems to be activated somehow without working in those specific viewports ... this only happens in select mode, when i click on other tools it goes back to normal untill i go into select mode.
I was creating some rock faces and stumbled upon this. <a href="http://img88.imageshack.us/img88/6062/ns2badselect01.png" target="_blank"><img src="http://img694.imageshack.us/img694/8039/ns2badselect01small.jpg" border="0" class="linked-image" /> (Click to enlarge)</a> This geometry cannot be selected consistently.
Try clicking in the holes from the saved camera position - only one of them deselects the geometry, the rest select it. Also, clicking in some other places outside of the geometry to deselect still results in selection.
This geometry was created by using the line tool to create triangles and manipulating the vertices along all axes. Selecting appeared to work fine at this stage. Then, the resulting geometry was rolled and selection stopped working properly.
The geometry can sometimes be selected when it is entirely out of view. Ability to select changes drastically with camera position. <a href="http://eagle.undo.it:8083/download/?id=9&act=url" target="_blank">ns2_selection_01.level</a>
(Oh, and the holes are intentional. The geometry is represented as intended.)
Anyone know about sharing vertices? Whenever I draw a block next too another, they tend to share vertices and I can no longer alter the new block without messing up the old.
Check this image to see what I mean <a href="http://dl.dropbox.com/u/1288771/spark%20error.jpg" target="_blank">http://dl.dropbox.com/u/1288771/spark%20error.jpg</a>
Night_Eagle that isn't supported yet. Totally forgotten what the word for that kind of geometry is, but basically they haven't designed the editor to do complex geometry like that yet, so you are bound to come up with issues with it. Stick to the props for rock faces for the time being. Oh... no hills either. Its on this thread somewhere, or on the map pic thread, not sure which.
d$k have you tried going into settings and changing the colours of the background/lines... also try changing the grid size, "[" and "]" keys should do it. I think both issues are just because you have the colour settings wrong on the background... no idea why. Also, you seem to have the windows set up wrong, I think that you may have downloaded the file with odd settings, the widows should be Perspective, Top, Front and Side. Not two perspectives... that can easily be changed in the corner of each window. Hope that works out ok for you.
ratclaw, try deleting the adjoining line, or creating the brush else where and dragging it into place. I think you'll have to do this a lot with this editor. I have found copy and paste work well, and then delete the original, that way you select all edges, dots, what ever, rather than just the sides.
When ever I go to manually change a model with a different one through the mesh browser, when I press enter (instead of clicking OK) it crashes with the error report screen. EDIT: Same thing happens if I double click on a model. I HAVE to press OK to get it to change.
Thanks for the quick response INKEDOUT. I was hoping there was already a fix for this. The copy and paste works good enough for me right now. Next is to figure out why my level always becomes un-aligned with the grid every time I load the editor...
<!--quoteo(post=1739498:date=Nov 24 2009, 05:49 AM:name=Ghozer)--><div class='quotetop'>QUOTE(Ghozer @ Nov 24 2009, 05:49 AM) <a href="index.php?act=findpost&pid=1739498"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->following through the first video tutorial, when the guy draws the second rectangle on the wall, then shows you that there's two there by selecting one, then the other. then he extrudes it to create a corridor...
When I attempt to select one, then the other, it will only select the big 'back' wall, and wont allow me to extrude the smaller 'corridor' rectangle.
if I extrude the back wall, it leaves an unfilled outline of where the corridor rectangle is, but nothing selectable...<!--QuoteEnd--></div><!--QuoteEEnd-->
I am experiencing this issue as well. I tried creating different rooms of varying sizes and this occurred every time. The odd thing is that triangulation changes when I draw the rectangle within, indicating that it has been added to the wall, but the triangles don't look anything like they should. It may be worth noting, however, that drawing a rectangle within the floor or ceiling and extruding that works perfectly fine.
(edit: After more testing, it appears this problem only occurs when drawing a rectangle that touches the floor/ceiling of the room. If I draw a rectangle above floor level, it works perfectly.)
Consider the triangulation in these images. <img src="http://www.mikael-ange.ca/rectangleissue1.jpg" border="0" class="linked-image" />
<!--quoteo(post=1740681:date=Nov 27 2009, 02:25 AM:name=LethalShadow)--><div class='quotetop'>QUOTE(LethalShadow @ Nov 27 2009, 02:25 AM) <a href="index.php?act=findpost&pid=1740681"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->I am experiencing this issue as well. I tried creating different rooms of varying sizes and this occurred every time. The odd thing is that triangulation changes when I draw the rectangle within, indicating that it has been added to the wall, but the triangles don't look anything like they should. It may be worth noting, however, that drawing a rectangle within the floor or ceiling and extruding that works perfectly fine.<!--QuoteEnd--></div><!--QuoteEEnd-->
Just a note which someone put on here, which worked for me as a 'work around', instead of drawing the corridor rectangle with the retangle tool, use the pen tool and draw the 4 edges seperatly, this has worked without a problem for me, and i'm well on the way to playing with other stuff now, and getting used to the editor a bit more :)
On another note, I read on the thread about creating adjoining rooms, I found the easiest way to do this was to build a room around an already made corridor for example, then use the pen tool to draw round the corridor directly, where the rooms walls were, then just delete the remaining faces..
I also expected o be able to extrude a corridor into a room and it create an opening, sort of like the add and subtract features of UnrealEd, it would be nice if the editor auto detected when you did this sort of thing, oh, and with an option to 'ignore' too, as there will be cases when you might not want it to do it automatically.
I don't think lights are supposed to go through walls, are they? Here you can see the red light is first going through a wall inside those vents, then coming in through the corridor wall. <a href="http://img4.imageshack.us/img4/391/lighthroughwall.png" target="_blank">http://img4.imageshack.us/img4/391/lighthroughwall.png</a>
<!--quoteo(post=1740813:date=Nov 27 2009, 08:27 AM:name=Vemarkis)--><div class='quotetop'>QUOTE(Vemarkis @ Nov 27 2009, 08:27 AM) <a href="index.php?act=findpost&pid=1740813"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->I don't think lights are supposed to go through walls, are they? Here you can see the red light is first going through a wall inside those vents, then coming in through the corridor wall. <a href="http://img4.imageshack.us/img4/391/lighthroughwall.png" target="_blank">http://img4.imageshack.us/img4/391/lighthroughwall.png</a><!--QuoteEnd--></div><!--QuoteEEnd--> This has been addressed.
Point lights do not cast shadows yet (which would fix your problem). Only spot lights do (and the shadow fades away the further you move from the light).
My editor crashes after starting it and gives errors in the output
IDirect3DDevice9::CreateTexture failed (Invalid call) IDirect3DDevice9::CreateTexture failed (Invalid call) IDirect3DDevice9::CreateTexture failed (Invalid call) IDirect3DDevice9::CreateAdditionalSwapChain (349x208) failed (Out of video memory) IDirect3DDevice9::CreateAdditionalSwapChain (349x209) failed (Out of video memory) IDirect3DDevice9::CreateAdditionalSwapChain (349x209) failed (Out of video memory) IDirect3DDevice9::CreateTexture failed (Out of video memory) IDirect3DDevice9::CreateTexture failed (Out of video memory) IDirect3DDevice9::CreateTexture failed (Out of video memory) IDirect3DDevice9::CreateAdditionalSwapChain (349x208) failed (Out of video memory) IDirect3DDevice9::CreateAdditionalSwapChain (349x209) failed (Out of video memory) IDirect3DDevice9::CreateAdditionalSwapChain (349x209) failed (Out of video memory)
Running Vista 32 with 2GB RAM, 8800GT (191.07), and a Q6600 (at stock speed) and I'm crashing left and right.
I make a room, throw in a couple of props - crash. Extrude some simple geometry - crash.
Ran memtest wondering if my ram was failing - let it run for a few tests (30+ minutes) and it didn't get any errors.
It's just so frustrating given that each time it crashes it rarely saves any adjusted settings (undocking windows, adjusted shortcuts). Any suggestions to make my system more stable? Driver tweaking?
***Edit - yea, this is ridiculous - can't seem to manage more than 5 minutes before crashing each and every time.
***Edit #2 - Tried a couple of things without restarting windows. Turned off themes and switched to classic (turning off Aero). Additionally, I went through services and turned off anything that looked unnecessary, including NVIDIA's stereo view service (for 3d-vision stuff). Started up Editor.exe and was actually able to spend a lot more time placing props in a simple 256 x 256 x 1024 hallway. However, after about 15 minutes and maybe 20 props later (using default textures, and having not added any lights), I got another crash. Typically my crashes seem to be the result of placing a prop, rotate it to position, move it into position, and then selecting the "select tool" either via short cut or clicking on it's icon in the toolbar -- CRASH.
Going to load up my last save / auto save and keep on plugging.
<!--quoteo(post=1739973:date=Nov 24 2009, 06:35 PM:name=Comprox)--><div class='quotetop'>QUOTE(Comprox @ Nov 24 2009, 06:35 PM) <a href="index.php?act=findpost&pid=1739973"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->This is good to get actually. This error is being send directly to UWE when you see this screen. Fill in any information that might help and hit submit (I know you can't, but just posting for others to see). I can't tell what the error exactly is, but UWE gets the information in the dump file.<!--QuoteEnd--></div><!--QuoteEEnd-->
I am getting the same error. Where is the minidump file located? The Editor just exits after I get the error.
Windows Xp Professional service pack 2 Radeon 9600 Sapphire Atlantis 256MB DDR AGP 8X 1 GB Corsair 3200 Memory Abit NF7-S V1.0 Motherboard AMD Athlon 2600 333fsb overclocked to 400fsb to match memory speed DirectX 9.0c
I was having the application error too, but I downloaded the fix and then this one started popping up instead.
EDIT: I updated my video drivers to the newest ones on the windows update site, 2/3/2009 version 8.582.0.0, and the editor loads right up now.
Unfortunately, I too seem to have a card with the missing blacked out textures problem.
Anyone find a work around yet?
Also, I noticed the editor deleted some files while it was updating, could it maybe have removed needed files and broken the update? Just a thought.
I've been sent other peoples levels to help them with problems, however they've been unusable for me. All editing area's are black, I can run another instance of Spark and load my levels fine.
I don't know if this is due to the way the editor is perhaps saving files due to OS and 32/64 bit or anything like that? Might be worth people swapping save files amongst different versions of OS to test this one.
I've got an obscure one: I was dragging around a prop browser on my secondary monitor. I discovered that when I released the window in certain places it would snap back over to my main monitor. I deduced that the logic it uses to decide whether to snap a subwindow into the main window doesn't take into account multiple monitors. If the coordinates of the mouseup are near the toolbar at the top, the subwindow snaps in, regardless of the fact the cursor is 1680px to the left of where it thinks it is.
Comments
Windows XP-32bit
Nvidia-7950GT
now the x300-x1300 are a directx 9.0-9.0b generation card. Its only the x1300-x1600 that are a directx 9.0c compliant card, my money is on the fact that it needs to support direct x9.0c, nothing less. Can anyone confirm with a x1300-1600 that they arn't getting the black texture issue? (apart from sloppy joe, your problem is different)
The geforce FX series is also a 9.0b generation card. i believe ive just cracked the problem lol.. wheres my cookie?!!<!--QuoteEnd--></div><!--QuoteEEnd-->
No cookie for you!
They clearly stated that those 9.0b cards with lower shader version are supported by the game.
In fact I didn't preorder with my crappy x700 until they finally answered this question and I wasn't the only one asking.
Anyway, maybe you are right though that this difference is causing the bug.
And just to clarify this bug:
The textures aren't missing, because you can see the full-lit parts of models that are representing lights.
And I've also noticed that you can see the proper lit texture a few ms after adding the prop, before it turns all black, except of the light parts.
In the texture-/ and prop-browser everything is black aswell.
The textures aren't missing, because you can see the full-lit parts of models that are representing lights.
And I've also noticed that you can see the proper lit texture a few ms after adding the prop, before it turns all black, except of the light parts.
In the texture-/ and prop-browser everything is black aswell.<!--QuoteEnd--></div><!--QuoteEEnd-->
Yes I can confirm that.
The fact that the lit texture is visible for a ms at prop creating makes me think that the card itself can handle the graphics, but the editor has something against it.
But when you scale the windows (layer, edit, prop window etc) to maximize the view of work space it changes when you change tools. I like to have my layer window small (drag to the left side, like a thin line as i only use works as light, prop, map etc) as i run 1920x1080.
<img src="http://photos-e.ak.fbcdn.net/hphotos-ak-snc3/hs050.snc3/13749_1210559677203_1625082982_556120_2423165_n.jpg" border="0" class="linked-image" />
Is the editor also rendering stuff that is not in view range? Can anyone confirm my observation?
<img src="http://photos-e.ak.fbcdn.net/hphotos-ak-snc3/hs050.snc3/13749_1210559677203_1625082982_556120_2423165_n.jpg" border="0" class="linked-image" /><!--QuoteEnd--></div><!--QuoteEEnd-->
Sense you dont have any lights in there, make sure your Perspective mode is on Textured Unlit, instead of Lit.
Make sure you read what you quote..
I hope this bug gets fixed soon. I can't even check out all the juicy textures and props.
<!--quoteo(post=1739498:date=Nov 24 2009, 10:49 AM:name=Ghozer)--><div class='quotetop'>QUOTE(Ghozer @ Nov 24 2009, 10:49 AM) <a href="index.php?act=findpost&pid=1739498"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->following through the first video tutorial, when the guy draws the second rectangle on the wall, then shows you that there's two there by selecting one, then the other. then he extrudes it to create a corridor...
When I attempt to select one, then the other, it will only select the big 'back' wall, and wont allow me to extrude the smaller 'corridor' rectangle.
if I extrude the back wall, it leaves an unfilled outline of where the corridor rectangle is, but nothing selectable...
<img src="http://www.clanscf.com/spark1.jpg" border="0" class="linked-image" /><!--QuoteEnd--></div><!--QuoteEEnd-->
For the line on the wall issue, I found that I sometimes have to go over the line again, make sure the wall is actually flat, and be sure you have done all four sides of the block.
If it works you will then probably get the next issue I have been having, one side of the split wall will change to the default texture and become grey. Which means if I make a room, and then decided I would like another corridor or doorway in the room, I have to re-texture the room. Not fun when you are adapting a map and have spent hours texturing.
<!--quoteo(post=1739630:date=Nov 24 2009, 02:54 PM:name=Nazul)--><div class='quotetop'>QUOTE(Nazul @ Nov 24 2009, 02:54 PM) <a href="index.php?act=findpost&pid=1739630"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->i'm not having troubles at al which stuns me seeing so many people do ( im usually one of those... )
Ok so my problem is that when i made a wall> place a cylinder on it > extrude > make room on other side > it does not merge the cylinder with the new room.. and there is no option to do so.
though i seriously like the editor , somewhere i read it was like SkecthUp and Ed combined, second that and love it ^^
edit:
ok found problem 2 :D when i'm looking in a particular angle the whole map goes unlit. haha random-ness<!--QuoteEnd--></div><!--QuoteEEnd-->
Yeah, I hate the I can't join two rooms together! You have to go into the relevant view (top, side, front, etc.) and draw out the place you want the hole in your second room, and cut it out. Kinda makes scenes when you think about putting rooms next to each other, but it wasn't exactly what I expected to happen. I expected the hall to join the room, and the wall that joins it to be separate so you could delete it if you needed to.
<!--quoteo(post=1739515:date=Nov 24 2009, 11:25 AM:name=Kerotan)--><div class='quotetop'>QUOTE(Kerotan @ Nov 24 2009, 11:25 AM) <a href="index.php?act=findpost&pid=1739515"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Spotlights crash the editor.
Just me or are others getting this?<!--QuoteEnd--></div><!--QuoteEEnd-->
Yeah same here, crashes every time, I am yet to see the pretty shadow effects. I have a NVIDIA GeForce 7600 GT, I know, from the manual, that the 7900 doesn’t work, could it be more of the NVIDIA range? Also, how will this effect my chances of being able to play the final game, will all the maps with spot lights in crash out? LOL! :S
EDIT: sorry, I forgot to say, I did acctually have spotlights working at one point, but not for long, and now I have no idea how to get them working again.
Nice to finally have the editor though, I hope the next patch fixes these bugs. Keep up the good work!
<img src="http://users.telenet.be/berten83/grid.JPG" border="0" class="linked-image" />
My second problem is that in my top and right viewports the grid seems to be activated somehow without working in those specific viewports ... this only happens in select mode, when i click on other tools it goes back to normal untill i go into select mode.
<img src="http://users.telenet.be/berten83/blackground.JPG" border="0" class="linked-image" />
<a href="http://img88.imageshack.us/img88/6062/ns2badselect01.png" target="_blank"><img src="http://img694.imageshack.us/img694/8039/ns2badselect01small.jpg" border="0" class="linked-image" />
(Click to enlarge)</a>
This geometry cannot be selected consistently.
Try clicking in the holes from the saved camera position - only one of them deselects the geometry, the rest select it.
Also, clicking in some other places outside of the geometry to deselect still results in selection.
This geometry was created by using the line tool to create triangles and manipulating the vertices along all axes. Selecting appeared to work fine at this stage. Then, the resulting geometry was rolled and selection stopped working properly.
The geometry can sometimes be selected when it is entirely out of view. Ability to select changes drastically with camera position.
<a href="http://eagle.undo.it:8083/download/?id=9&act=url" target="_blank">ns2_selection_01.level</a>
(Oh, and the holes are intentional. The geometry is represented as intended.)
<b>Edit:</b>
Whoops, wrong link.
Anyone know about sharing vertices? Whenever I draw a block next too another, they tend to share vertices and I can no longer alter the new block without messing up the old.
Check this image to see what I mean
<a href="http://dl.dropbox.com/u/1288771/spark%20error.jpg" target="_blank">http://dl.dropbox.com/u/1288771/spark%20error.jpg</a>
<!--quoteo(post=1740583:date=Nov 26 2009, 07:12 PM:name=Night_Eagle)--><div class='quotetop'>QUOTE(Night_Eagle @ Nov 26 2009, 07:12 PM) <a href="index.php?act=findpost&pid=1740583"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec--><!--QuoteEnd--></div><!--QuoteEEnd-->
<!--quoteo(post=1740612:date=Nov 26 2009, 09:13 PM:name=ratclaw)--><div class='quotetop'>QUOTE(ratclaw @ Nov 26 2009, 09:13 PM) <a href="index.php?act=findpost&pid=1740612"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec--><!--QuoteEnd--></div><!--QuoteEEnd-->
Night_Eagle that isn't supported yet. Totally forgotten what the word for that kind of geometry is, but basically they haven't designed the editor to do complex geometry like that yet, so you are bound to come up with issues with it. Stick to the props for rock faces for the time being. Oh... no hills either. Its on this thread somewhere, or on the map pic thread, not sure which.
d$k have you tried going into settings and changing the colours of the background/lines... also try changing the grid size, "[" and "]" keys should do it. I think both issues are just because you have the colour settings wrong on the background... no idea why. Also, you seem to have the windows set up wrong, I think that you may have downloaded the file with odd settings, the widows should be Perspective, Top, Front and Side. Not two perspectives... that can easily be changed in the corner of each window. Hope that works out ok for you.
ratclaw, try deleting the adjoining line, or creating the brush else where and dragging it into place. I think you'll have to do this a lot with this editor. I have found copy and paste work well, and then delete the original, that way you select all edges, dots, what ever, rather than just the sides.
EDIT: Same thing happens if I double click on a model. I HAVE to press OK to get it to change.
It looked like triangulation was doing such a great job, too :(
When I attempt to select one, then the other, it will only select the big 'back' wall, and wont allow me to extrude the smaller 'corridor' rectangle.
if I extrude the back wall, it leaves an unfilled outline of where the corridor rectangle is, but nothing selectable...<!--QuoteEnd--></div><!--QuoteEEnd-->
I am experiencing this issue as well. I tried creating different rooms of varying sizes and this occurred every time. The odd thing is that triangulation changes when I draw the rectangle within, indicating that it has been added to the wall, but the triangles don't look anything like they should. It may be worth noting, however, that drawing a rectangle within the floor or ceiling and extruding that works perfectly fine.
(edit: After more testing, it appears this problem only occurs when drawing a rectangle that touches the floor/ceiling of the room. If I draw a rectangle above floor level, it works perfectly.)
Consider the triangulation in these images.
<img src="http://www.mikael-ange.ca/rectangleissue1.jpg" border="0" class="linked-image" />
Just a note which someone put on here, which worked for me as a 'work around', instead of drawing the corridor rectangle with the retangle tool, use the pen tool and draw the 4 edges seperatly, this has worked without a problem for me, and i'm well on the way to playing with other stuff now, and getting used to the editor a bit more :)
On another note, I read on the thread about creating adjoining rooms, I found the easiest way to do this was to build a room around an already made corridor for example, then use the pen tool to draw round the corridor directly, where the rooms walls were, then just delete the remaining faces..
I also expected o be able to extrude a corridor into a room and it create an opening, sort of like the add and subtract features of UnrealEd, it would be nice if the editor auto detected when you did this sort of thing, oh, and with an option to 'ignore' too, as there will be cases when you might not want it to do it automatically.
<a href="http://img4.imageshack.us/img4/391/lighthroughwall.png" target="_blank">http://img4.imageshack.us/img4/391/lighthroughwall.png</a>
<a href="http://img4.imageshack.us/img4/391/lighthroughwall.png" target="_blank">http://img4.imageshack.us/img4/391/lighthroughwall.png</a><!--QuoteEnd--></div><!--QuoteEEnd-->
This has been addressed.
IDirect3DDevice9::CreateTexture failed (Invalid call)
IDirect3DDevice9::CreateTexture failed (Invalid call)
IDirect3DDevice9::CreateTexture failed (Invalid call)
IDirect3DDevice9::CreateAdditionalSwapChain (349x208) failed (Out of video memory)
IDirect3DDevice9::CreateAdditionalSwapChain (349x209) failed (Out of video memory)
IDirect3DDevice9::CreateAdditionalSwapChain (349x209) failed (Out of video memory)
IDirect3DDevice9::CreateTexture failed (Out of video memory)
IDirect3DDevice9::CreateTexture failed (Out of video memory)
IDirect3DDevice9::CreateTexture failed (Out of video memory)
IDirect3DDevice9::CreateAdditionalSwapChain (349x208) failed (Out of video memory)
IDirect3DDevice9::CreateAdditionalSwapChain (349x209) failed (Out of video memory)
IDirect3DDevice9::CreateAdditionalSwapChain (349x209) failed (Out of video memory)
Problem signature:
Problem Event Name: BEX
Application Name: Editor.exe
Application Version: 0.0.0.0
Application Timestamp: 4b0c7405
Fault Module Name: MSVCR80.dll
Fault Module Version: 8.0.50727.4918
Fault Module Timestamp: 49d43de9
Exception Offset: 00008aa0
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.1.7100.2.0.0.256.1
Locale ID: 3081
Additional Information 1: 7bbe
Additional Information 2: 7bbe909980cb72ccccb9331f6a4bb78d
Additional Information 3: 9dab
Additional Information 4: 9dab8dfe380803fb9683b1d6a26400fd
Problem signature:
Problem Event Name: BEX
Application Name: Editor.exe
Application Version: 0.0.0.0
Application Timestamp: 4b0c7405
Fault Module Name: MSVCR80.dll
Fault Module Version: 8.0.50727.4918
Fault Module Timestamp: 49d43de9
Exception Offset: 00008aa0
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.1.7100.2.0.0.256.1
Locale ID: 3081
Additional Information 1: f39f
Additional Information 2: f39f0ebfb229614452e39ca7e9c8c4b1
Additional Information 3: 7dab
Additional Information 4: 7dabf6e377e4ae3e25f013541d30f94e
Running Vista 32 with 2GB RAM, 8800GT (191.07), and a Q6600 (at stock speed) and I'm crashing left and right.
I make a room, throw in a couple of props - crash.
Extrude some simple geometry - crash.
Ran memtest wondering if my ram was failing - let it run for a few tests (30+ minutes) and it didn't get any errors.
It's just so frustrating given that each time it crashes it rarely saves any adjusted settings (undocking windows, adjusted shortcuts). Any suggestions to make my system more stable? Driver tweaking?
***Edit - yea, this is ridiculous - can't seem to manage more than 5 minutes before crashing each and every time.
***Edit #2 - Tried a couple of things without restarting windows. Turned off themes and switched to classic (turning off Aero). Additionally, I went through services and turned off anything that looked unnecessary, including NVIDIA's stereo view service (for 3d-vision stuff). Started up Editor.exe and was actually able to spend a lot more time placing props in a simple 256 x 256 x 1024 hallway. However, after about 15 minutes and maybe 20 props later (using default textures, and having not added any lights), I got another crash. Typically my crashes seem to be the result of placing a prop, rotate it to position, move it into position, and then selecting the "select tool" either via short cut or clicking on it's icon in the toolbar -- CRASH.
Going to load up my last save / auto save and keep on plugging.
I am getting the same error. Where is the minidump file located? The Editor just exits after I get the error.
Windows Xp Professional service pack 2
Radeon 9600 Sapphire Atlantis 256MB DDR AGP 8X
1 GB Corsair 3200 Memory
Abit NF7-S V1.0 Motherboard
AMD Athlon 2600 333fsb overclocked to 400fsb to match memory speed
DirectX 9.0c
I was having the application error too, but I downloaded the fix and then this one started popping up instead.
EDIT: I updated my video drivers to the newest ones on the windows update site, 2/3/2009 version 8.582.0.0, and the editor loads right up now.
Unfortunately, I too seem to have a card with the missing blacked out textures problem.
Anyone find a work around yet?
Also, I noticed the editor deleted some files while it was updating, could it maybe have removed needed files and broken the update? Just a thought.
I don't know if this is due to the way the editor is perhaps saving files due to OS and 32/64 bit or anything like that? Might be worth people swapping save files amongst different versions of OS to test this one.
<img src="http://img694.imageshack.us/img694/2513/error2.png" border="0" class="linked-image" />
Edit: It appears like this in all screen modes. (Textured, wireframe, top, front, etc.)
Edit: Another screenshot. Also shows the model pictures all bugged.
<img src="http://img402.imageshack.us/img402/615/error3.png" border="0" class="linked-image" />
--Scythe--