Ken Levy - In the field in Switzerland

I tend to confuse the Max name with the Autodesk 3d program "3ds max"
Comment removed at user's request.
moofish wrote:it doesnt even work I just spent about 1h trying to uninstall this and that to get it to work, why not just make it work with the most recent version of .net, come on
Zeo wrote:Blackcomb is alive and well.....Good to know that the codename of "Blackcomb" hasn't changed! Thanks for the confirmation...hadn't heard that codename being used since early 2004
mwirth wrote:hehe. Vienna. Funny choice since the city of Vienna chose to move to linux (why, i don't really understand and it's not really a concern of mine) just funny to note
Naaah. Keep the aspect ratio like it is in this video! love it.
Why does Max not work on a non-english version of Windows?? I can't understand that. I mean Max is in english and Windows in another language. Who cares?!
Could somebody of the team, please remove that nasty messagebox and let me install the enligsh version of Max on an non-english Windows version.
littleguru wrote:Why does Max not work on a non-english version of Windows?? I can't understand that. I mean Max is in english and Windows in another language. Who cares?!
Could somebody of the team, please remove that nasty messagebox and let me install the enligsh version of Max on an non-english Windows version.
mawcc wrote:
littleguru wrote: Why does Max not work on a non-english version of Windows?? I can't understand that. I mean Max is in english and Windows in another language. Who cares?!
Could somebody of the team, please remove that nasty messagebox and let me install the enligsh version of Max on an non-english Windows version.
Seems to be an new trend. One Care Beta requires an English operating system and US English Regional Settings.
Sometimes it hurts to be a non US citizen (although it shouldn't).
I also have a more general point to make.
I am quite confused about sharing items via Microsoft products over the internet. Here is a partial list of technologies available to share files from Microsoft: Good old Windows shares, Groove folder share,
www.foldershare.com, Windows Messenger 8, you might also argue Sharepoint with offline support via 1) Groove 12 and 2) offline support within Outlook, then you can share stuff via Exchange folders and I am sure I have
missed some. They are all named quite similiar, and unless two geeks want to share stuff it is almost certain that it will take a lot time to communicate which sharing technology should be used in a particular scenario. I think there should be ONE concept
of sharing items in Windows that works across all those scenarios. One UI. Consolidation is required, I believe. Right now I have the impression that MS is creating more and more technologies, instead of unifying them, which would really be needed.
Cheers,
David
scobleizer wrote:
Zeo wrote: Blackcomb is alive and well.....Good to know that the codename of "Blackcomb" hasn't changed! Thanks for the confirmation...hadn't heard that codename being used since early 2004
Zeo: sssshhhhh, but since this video was shot the codename for Blackcomb has indeed changed to Vienna. I haven't gotten the story on this yet, though.
scobleizer wrote:
Zeo wrote: Blackcomb is alive and well.....Good to know that the codename of "Blackcomb" hasn't changed! Thanks for the confirmation...hadn't heard that codename being used since early 2004
Zeo: sssshhhhh, but since this video was shot the codename for Blackcomb has indeed changed to Vienna. I haven't gotten the story on this yet, though.
Comment removed at user's request.
Zeo wrote:Oh and for all of you thinking that Vienna is the last version of Windows Microsoft is working on, there are researchers working on post Vienna concepts...
davida242 wrote:I also have a more general point to make.
I am quite confused about sharing items via Microsoft products over the internet. Here is a partial list of technologies available to share files from Microsoft: Good old Windows shares, Groove folder share, www.foldershare.com, Windows Messenger 8, you might also argue Sharepoint with offline support via 1) Groove 12 and 2) offline support within Outlook, then you can share stuff via Exchange folders and I am sure I have missed some. They are all named quite similiar, and unless two geeks want to share stuff it is almost certain that it will take a lot time to communicate which sharing technology should be used in a particular scenario. I think there should be ONE concept of sharing items in Windows that works across all those scenarios. One UI. Consolidation is required, I believe. Right now I have the impression that MS is creating more and more technologies, instead of unifying them, which would really be needed.
Cheers,
David
Oi Bobinho-
Firstly thank you for your suggestion that I run for MS President. I can neither confirm nor deny my candidacy, but I
can tell you I have been discussing this with my family and we are leaving all our options open. I'm having campaign buttons made, just in case, and I'll make sure you get one - if my team doesn't laugh me out of the building first.
About your plea for us to run on the latest WinFX CTP, here's the deal:
Our team is operating as a real product team / ISV. That is, our goal is not to build a sample app for WinFX (useful as that may be) but rather to build a real application that actual end-users will enjoy.
To us this means shipping high quality code on a very regular basis as we go from Alpha to Beta to RTM. Our approach is to ship quarterly, that is we plan, take off, fly and land every three months. At which point we update the publicly released software.
Which means we hit zero known bugs every three months (no snickers please.) Lots of ISVs already operate along these lines, but you might be surprised how unusual this approach is within Microsoft.
Which brings us to WinFX - In order to guarantee that we can ship the thing we work on every three months, we are very stringent about any dependencies we have on external code. Our general rule (which we've bent a couple of times to help out WinFX)
is to only take dependencies on publicly redistributable bits one month before we begin a quarter of coding.
This means that we will always be a few CTPs behind WinFX. This is of course an issue for developers self-hosting the latest WinFX. It's also an issue for the WinFX team, because we can't get them feedback on the absolutely latest bits they have shipped.
But overall we've found that with quarterly releases we've been able to strike a decent balance between being on new bits of WinFX, getting WinFX feedback, and shipping high quality code.
I really do appologize for the inconvenience this is causing MSDN folks, but for now this is the best we can do.
Cheers!
- Piero
A question for these MAX guys, when they tried to show that it was not hitting on the CPU performance and only the GPU, as far as my understanding of it goes the CPU is still heavily involved creating the mesh for the 3D structures. And if you watch you can see that the CPU does hit 100%. So is this the case?
Also when do we get to see the guys who actually write the code for this stuff?
scobleizer wrote:
Zeo wrote:Blackcomb is alive and well.....Good to know that the codename of "Blackcomb" hasn't changed! Thanks for the confirmation...hadn't heard that codename being used since early 2004
Zeo: sssshhhhh, but since this video was shot the codename for Blackcomb has indeed changed to Vienna. I haven't gotten the story on this yet, though.
Zeo wrote:Everyone thinks that Microsoft only works on N+1 technologies…like Vista and 012. But when I was at Microsoft’s campus in summer for a job interview….one of the people I met was interviewing for an 0ffice 13 PM position.
littleguru wrote:Why does Max not work on a non-english version of Windows?? I can't understand that. I mean Max is in english and Windows in another language. Who cares?!
Could somebody of the team, please remove that nasty messagebox and let me install the enligsh version of Max on an non-english Windows version.
allAccess wrote:
littleguru wrote: Why does Max not work on a non-english version of Windows?? I can't understand that. I mean Max is in english and Windows in another language. Who cares?!
Could somebody of the team, please remove that nasty messagebox and let me install the enligsh version of Max on an non-english Windows version.
i'm strongly agree...just less people are willing to install a seperat system just for playin around with new beta-tools?!
whats the dealio about this language-restrictions...if you wanna tryin 2 find a wide group of using your products to establish them in the market you should think about it...even internet-related tools with share-functions, often used worldwide
nevertheless i think MAX is a pretty good program based on some good ideas...thats what i think after watching this short movie...but unfortunatly without tryin by myself
littleguru wrote:
I'm wondering why nobody of the team answered my question... One of the guys posted something here, but did not mention my question... STRANGE!
davida242 wrote:I think there should be ONE concept of sharing items in Windows that works across all those scenarios. One UI. Consolidation is required, I believe.
FYI, Max is properly 'localized' from a development perspective. We run fxcop to ensure all our string operations are done with localization in mind and we use resources to make the substitution of other language strings simple.
As we all know, this is just one step in the process though. We have to translate the strings & test on the different language OSes. This is where we ran short on resource and had to make choices.
You've made your point to the right place. While Piero may not write code for a living, he is one of the key people on the team when it comes to arguing for and changing the policy on whether we block installation on untested languages. Hopefully we'll do
better in the future.
- jcb (yes, I write code in Max for a living)
Jay.Beavers wrote:Well, a couple of us are here now. Does it really surprise you that Piero had to walk down the hall and yell, "Hey programmer goobers. Close Visual Studio for a second and, like, talk to your customers!"
davida242 wrote:
That is great and much appreciated. I enjoyed the postings a lot, exactly what I was hoping to get! Sorry if my previous messages sounded unfriendly, I thought a little shaking wouldn't hurtKeep it up that way!
Rolleyes. The US is the great satan, yadda yadda yadda. There is a German and Japanese version of Microsoft Max available for a while now. As your profile says, you're working for a german .NET magazine, so there you go, get your german version of it. HELLO MESS! (lol) WTF?!littleguru wrote:mawcc said:
littleguru wrote: Why does Max not work on a non-english version of Windows?? I can't understand that. I mean Max is in english and Windows in another language. Who cares?!
Could somebody of the team, please remove that nasty messagebox and let me install the enligsh version of Max on an non-english Windows version.
Seems to be an new trend. One Care Beta requires an English operating system and US English Regional Settings.
Sometimes it hurts to be a non US citizen (although it shouldn't).
Yep. Those are weird requirements. Each application should be programmend independent of it's culture.
Since this is a managed app it requires only one line of code to set the culture to english...
I can't understand this limitation. This is not an open beta, this seems to be an open-for-america beta
"Seems to be an new trend. One Care Beta requires an English operating system and US English Regional Settings. Sometimes it hurts to be a non US citizen (although it shouldn't)." |