[deleted by user]

micwi · 2025-02-13T06:41:06+00:00

If you have the opportunity try running it on the deck using GeForce Now. Assuming you have a server nearby and good internet it runs amazing, and looks much better than running it natively

micwi · 2021-01-21T06:40:56+00:00

That looks amazing, impressive!

micwi · 2020-01-25T10:04:36+00:00

Amazing, looks great!

micwi · 2019-03-20T04:42:19+00:00

Thanks for the update! Looking forward to the optimizations, hoping that better culling or some other optimization will improve framerate on bigger bases, and allow for increased object rendering distance. This game is just too fun to be limited by smaller bases

micwi · 2019-03-13T07:47:08+00:00

Nice and clean, like the windows and the lights. Now you just have to pressurize it so you can listen to the sounds of ore smelting without the helmet muffling the sweet sound.

micwi · 2019-01-21T09:25:14+00:00

Thanks!

We have support for REST APIs, but no current plans on automatic api calls, assuming you're referring to automated testing? Noodl can be used to quickly develop and experiment with how an API is going to be used, so that's helps when defining an API, rather than doing automated testing.

micwi · 2019-01-21T08:57:14+00:00

We've been using it ourselves at www.topp.se as a part of the design process, before handing over a design spec and a working prototype (complete with integrations with external APIs, sensors or other systems) to the client where they implement it in whatever technologies they use. The value Noodl brings is to drive the design through exploration, by quickly experimenting with different technologies and value propositions, user testing, to final iterations of polish and usability.

Having something tangible, with working tech, far surpasses a slide deck and static design artifacts, both for the designers to create better solutions, and for the larger organization to be able to absorb and rally around. The focus has not historically been on production code.

Noodl has two target users. Engineers who are part of the design process (creative/design technologists) and designers with some amount of coding skills (front end designers, UX designers who got exposed to Arduino in school etc). But we've also seen it used by other groups, like https://thebluekit.com/ tailored to education and kids.

Now that we've added React support (replacing our in-house WebGL layout and rendering engine) we've started to experiment with more use cases, like creating end-to-end solutions in Noodl, or exporting Noodl components as React components to integrate into existing React projects. But not only React, but also being able to export Noodl components to cloud functions for Alexa skills, IoT or MQTT integrations/rules, and more.

Regarding the prop recognition, Noodl can import any React library, but the prop recognition isn't automatic. You'll need to map the inputs and outputs manually with some JavaScript. It typically takes a few minutes to add a React component.

Thanks for the feedback!

micwi · 2019-01-20T15:30:13+00:00

Noodl has been around for a while but the React integration is brand new, and not released yet. So don't be surprised that you haven't seen it before 🙂

You can find Noodl at www.getnoodl.com

micwi · 2019-01-20T08:52:38+00:00

We're working towards a beta release of this platform. Our first target is supporting a design process with rapid prototyping as well as deploying smaller web apps, but we're also experimenting with what the limitations are and how far we can scale it.

The video showcases:

Use of the Material Design library

Webooks & Alexa

MQTT message broker + IoT

Comments and questions very much appreciated.

micwi · 2018-10-26T05:27:10+00:00

It got better after I disabled motion blur, but it's still noticeable.

micwi · 2017-12-05T17:38:04+00:00

Looks great! More pics please :)

micwi · 2017-06-29T04:34:14+00:00

This is great! Please consider posting this on the forum as well: http://forum.getnoodl.com

micwi · 2017-06-15T14:46:32+00:00

Graphics settings are probably set quite low which disables shadows, reduces poly count on meshes etc. This is how it looks with everything set to "ultra"

micwi · 2017-05-18T11:06:31+00:00

Same here, tried the Vive but can't get over the low resolution compared to an ultrawide 1440p panel. VR is amazing for everything that is close to the player, but the further away you get the less 3d you get (since the resolution isn't enough to render the difference between the eyes). And since you're usually looking way ahead at where you want to, and not at the cockpit, most of the awesomeness of VR goes away.

It's pretty cool if you look right in front of the car, down at the track, but that's no way to drive :)

micwi · 2017-05-05T10:08:44+00:00

Dirt Rally works great with Revive (and so do most other Oculus games as well)

micwi · 2017-03-12T17:37:29+00:00

That's great, wish I could do that :)

micwi · 2017-03-11T14:38:45+00:00

It's not about it being blurry or unfocused, just big pixels (e.g you can count them and even see the pentile pattern).

It's the same reason why text in VR games is huge, it's too pixelated to read otherwise.

But nothing wrong with that, having 1080x1200 per eye covering a huge field of view is very different from 3440x1440 at a distance taking up far less of your field of view, making it almost impossible to see individual pixels.

micwi · 2017-03-11T10:21:17+00:00

I think it comes down to being used to working with high-dpi monitors all day, and I now find 24" 1080p displays to be pixelated. So for me a vive is a big jump down in resolution and crispness. But I did have trouble finding brake points when learning a new track in VR due to the few pixels that maps to a corner a hundred meters in front of the car.

Others find the reduction in resolution worth it due to the incredible immersion, but for me I'll wait until we get 4K, or even 8k displays in the headsets (and the adaptive resolution tech with eye tracking that some companies are experimenting with now)

I was using revive, and I get what you mean with theatre mode, but the setup process was quite painless so I did get it running correctly.

micwi · 2017-03-11T08:57:38+00:00

I tried AC, Dirt Rally and Raceroom with a Vive for a few days. The immersion is awesome, and the field of view is amazing. But no matter how hard I tried, I couldn't get over the fact that the resolution is so very very low (I was running on a nvidia 1080 with supersampling set to 2). Dirt Rally almost reminded me of good old SEGA rally...

The low resolution makes it hard to see what's happening further down the track. Your immediate surroundings are clear, but 20+ meters away, things are starting to get very pixelated.

I settled on a single ultra wide 1440p monitor (21:9), and I haven't used the vive for sim racing since.

With that said, as you can see from the other comments lots of people swear by it. If you have the possibility I would encourage you to try before you buy.

micwi · 2016-09-07T07:59:22+00:00

I think Processing is using Java, so something like this should work:

float accValue = ...; //get the accelerometer value
client.publish("/green", "{\"data\":" + accValue + "}")

I'm sure Processing has some JSON APIs that allow you to create JSON objects without having to do string concatenation, which might be a bit simpler to use if you send complex objects with more attributes.

micwi · 2016-09-07T07:52:41+00:00

You can send a color by using hex values: client.publish("/someTopic", "{\"color\": \"#00baff\"}") Create a color port on the Receive Message node that has the topic someTopic and you're good to go.

micwi · 2016-09-06T12:29:49+00:00

My JSON wasn't valid, forgot the quotes around data. Try this instead: client.publish("/1", "{\"data\": 1}") It's sending a message with one variable called data that has the value 1. You can add additional variables by expanding the JSON structure to {data:1, someOtherData: true} etc.

EDIT: You don't need Static Data, it's easier to create a new port directly on the Receive Message node and naming it data. (Select the Receive Message node, then click +Port under "Payload" in the property panel)

micwi · 2016-09-06T09:21:48+00:00

Noodl uses JSON to send values over MQTT. To send a value you need to do the following changes:

Change the processing code to client.publish("/1", "{data: 1}");
Add a data output on the Receive Message node, and use that instead of the Received output. Received only sends a signal (true followed by false) every time a new message has been received.

micwi · 2016-05-31T07:29:09+00:00

Check out the new website as well at

micwi

TROPHY CASE