Weekly Update #03

VWORP VWORP VWORP


Have an update guys.

Exterior is done! Pat yourselves on the back guys.
Tony might need a bit of suggestions for the interior. He'll be in the lab on Wednesday, so you could drop by and give him your support.

Also Tony, because our good friends did not partition the slabs, you might have to either change the entire floor material, or add a small, maybe 12mm "carpet" slab on the existing slab for different materiality.

Here's a screenshot of what I'm talking about.

Ok. Now jobs. Jobs are cool, are they not?

---
Well, that presentation went swimmingly, eh guys?

Ian seemed happy. I guess that's good right?

RIGHT?
---


Brian
Ok, I've sent you some sample trees from my renderer's tree library. Pick out the nice ones and tell me where I should put them.

Kris
There are some modelling errors on the main model, especially with the intersection points with the roof and the curved walls.

Also, I noticed we only have one exterior exit door. Is this correct?


Justin
Synchronize with Kris with the design issues I've raised earlier. The model you sent me isn't up to sync with the model in the bimserver. Ask Kris or Brian to help intergrate the two if you aren't sure. I'd help but you'll have to meet me in the lab some time.


Tony
Ok. Interiors. Whew. Um, Kris has posted some guidelines on how the interior might look like, especially when taking the form of the building into context. I'm going to tell you there is gloss. A lot and lot of gloss. Basically, alot of shiny bits here and there. Just an fyi, since for the renders I'd probably have to swap out a ton of shaders (don't worry, I'll keep the designs, it's just an optimization thing with the material typologies and whatnot).

Also, it's probably good to colour code the material types. Kris and Brian went nuts with the materials (Surface Whitewash on the walls? Seriously guys?). You might have to change some of them.

Could be worth putting some placeholder textures/colours first, and telling me what they are when I'm in the lab. I can sync them with the renders.

Saunder
Hey cool, I'm talking to myself. I'm working on some shader presets now. I did some testing with some interior stuff, and I'll probably add the lighting and maps in once the interiors become avaliable. I'll keep you guys posted.

Also, strip lighting is a pain in the flank to intergrate.

---


That concludes this week's weekly update. STAY TUNED.

-Saunder

Weekly Update #02

Here have some update.

Most of the exterior is done now. Tony can start doing up the interiors right about now.


I won't say we hit any major icebergs on the way. Might wanna be less picky on the design guys, but that's just me.


Anyway, have some pretty clay renders.

Progress thus far.

Awesome terrain mesh from Brian. No?

Western view. Pretty, is it not?

Overview of the model boundaries, now with context!

Guys, we may have a modelling error. Don't worry, I told Brian and Justin lol.

This is how our neighbours view us.

I believe this calls for a change of blog header. :D

That's all for today folks.

Stay tuned.

-Saunder.

THE FUTURE IS NOW

 Guys, we should totally convince the university that Minecraft is the future of BiM

-Saunder

Weekly Update #01

Here, have some concept sketches. Courtesy of Justin and Kris

And this is how the model looks like now

-Saunder

Server Upload

So Brian and Kris worked on the model while I was away.

Ain't she pretty?

Also, I went to uni today to upload the model. We can totally work on this now guys.

TL;DR
GENTLEMEN, START YOUR ARCHICAD


-Saunder

This is why we're 20% cooler than all the other groups

Thanks Justin for the photo




GROUP BARBEQUE

HUZZAH!


-Saunder

Server Issues

About the server.

I'm getting reports about everyone not being able to connect to the server (myself included). Seems it won't even authenticate me as a user (AC was able to dial the actual server though)


Apparently for some reason, the University decided to block all the external ports into their network, so we can't exactly work-from-home. I've sent some e-mails (but they haven't been replied) regarding the issue, so here's some temporary workarounds...

At first, I thought it was a problem native to ArchiCAD (after some poking around at the AC problems, but now I'm almost sure it's a network issue)

1. Go to university
Not even the labs, I mean. The University is blocking access to the bimserver when connecting from other networks. As long as you're connected within the university network itself, you should be good to go.

2. Work offline
You could work offline first. Just remember to send/recieve changes whenever you're connected to the university network. The model progress can fluctuate at times, so your stuff may get out of date pretty soon. That said, it's probably the only way you can work from home now.

3. Port forwarding/Some weird hackery magic.
I'll get back to you on this.




Have a happy holiday,
(See you at the BBQ guys)


-Saunder
EDIT (17/10) : Confirmed network issue in today's lecture.