This is a summary in my own words, based on my own notes, taken whilst watching SCL. I'll mostly be paraphrasing here rather than directly quoting anyone, and occasionally I might add my own comments which are identifiable through the use of Italics within brackets. I've included links below for the YouTube and Twitch VODs respectively.
In this week's episode of SCL, "Simon Bursey and Zane Bien join us [...] to talk all things UI development including vehicle HUDs, kiosks, and more.
" For reference, Simon is the UI Director, and Zane is now the/a Principle UI Core Tech Developer. Total:
25 Questions. Q01) What can you tell us about plans to let users customise their various HUD elements? (e.g. prioritising features, re-sizing elements, changing the colour) [03:28] TL;DR Customisation can only be developed after they've got the default UI working in a way that's functional, and that they're happy with, otherwise it'd create a lot more work as they try to iterate on the UI's development to get it right. As such, they're more interested in why people want customisation, and whether there are other solutions to those problems. The difficulty in seeing some UIs in certain situations is addressed later.
First they'd ask: why do people want to customise things? Their first thought is that it's because the current UI isn't working for people, so then they'd need to know what people don't like. In relation to this, they're reworking the HUD, Multi-Function Displays, and the FPS visor. Jared posits that one of the reasons people want to be able to change the HUD colour is because it can be difficult to read at times, so being able to change the colour could help with that, but also sometimes people just like different colours, or it could even be related to colour blindness. He continues by saying that it's important to get the basic building blocks of UI done first, before they implement customisation. Zane talks about how they're moving away from having static UI building blocks, to much more flexible ones that should help in solving UI issues. Regarding changing colours to make things easier to read, Zane suggests that there might be a solution to that problem that goes beyond UI (this gets talked about later
). Jared reiterates that whilst they're still in development, they want to make the best default standard UI possible, which requires everyone to be using the same thing so that the feedback is unified rather than skewered, because otherwise the feedback would be in regards to specific customisations that would be hard to follow (because there'd be so many different setups). Simon specifies that they are interested in getting feedback about problems people are having with UI right now, and encourages people to share that feedback with them. Q02) Currently, UI elements like icons of station turrets or mission points can be very invasive, sometimes filling the screen. What can be done to make this more user-friendly/diegetic? [08:38]
It's something that they're interested in looking at, but they're not sure how soon they're going to get to it. What they want is some sort of intelligent system that works based on how far away things are, based on a priority that the designers have somehow set, which then works out which things to show and how many of them to show - i.e. choosing which options from a massive selection are the most important to show. This would be the starting point to addressing the issue. Q03) As the universe becomes more complex, more entities are vying for space on the HUD: notifications, Points-of-Interest, QT destinations, ships, mission markers, etc. What can be done to manage all of this information? [09:49] TL;DR They're moving towards a new UI tech system that will allow certain HUD elements to contextually minimise or disappear when they're not needed - a good example of this is the Target Box that often just sits there saying "No Target". On top of this, they want to avoid having information repeated (such as the same info being on the visor HUD as the ship HUD), as well as Players being able to choose what appears on their visor. Jared hints that they'll show off some UI WIPs in Q3 of ISC.
Zane says that when they have easily flexible layouts, they can start thinking more about how to make things smarter regarding when info is displayed. He brings up an example that CR has referred to previously this year: the "Target Box" which often just sits there saying "No Target", saying that if you don't have a target, why don't they just not have the box there at all. Typically that extends across all UIs too, such as the MFDs, where if you don't need to view something at that time, it can disappear out of view and reappear when they're needed, i.e. being more contextual. Simon adds that as they've been developing, they've been adding more and more things, so now they can take a step back and figure out what they want to show and how best to do that. They refer to the Chat box as an example of how it's almost constantly overlapping other UI elements when really it needs its own space on the screen, which Zane says is because the Chat box and the Ship UIs are on two different contexts, so they don't know about each other's sizes. He mentions how they're reworking the MFDs right now, creating a whole new system that's much more systemic, where it has a grid system "where everything kind of fits into each other and you can create different sizes of widgets", and suggests that that's probably how it'd be when they revamp the rest of the UI too. They want to be able to not have information repeated, such as being on the helmet visor as well as being on an MFD, as well as Players then being able to specify what information/HUD element they want on their visor. This requires building the foundation first into the overall design, which is something they're spending a lot of time working on right now as the tech is being developed in parallel. So they're building the tools to help them as developers to make really good UI, and then when that's done they can put the good UI into the game for everyone to see and use it, and hopefully to give feedback on it. Jared hints that the next quarter of ISC will show off some of this UI work that's in-progress. Q04) Is the messsage-spam that keeps popping up on the HUD a bug or a design feature? [14:39] TL;DR No; everything's competing for attention due to this problem only appearing after so many things were added into the game separately. Otherwise they need to investigate how to make the messaging system work, in relation to the visor HUD. They have a few ideas on how to do this, such as timers, limits to how many messages can appear, and more direct changes to how Players are notified about new messages.
Simon thinks that it's a legacy feature from having so many things added to the game; that they're all competing for attention. It's something they're planning on investigating - the visor display generally - which is: what do we do to this messaging system to make it work for people. For example, they could give messages priority, so that something really important could override other stuff. They could implement timers so that they stay on for a set time. They could restrict how many messages show within a certain amount of time. Zane adds that they need a smarter system that knows what messages should be displayed there, and suggests that maybe the missions could just be a pulsating icon with a number on it, so that Players can see how many unread new missions there are at a glance. Simon adds that they want to split the mission notifications so that messages are in one place, and that they have a mission objective area showing the current mission related stuff, and somewhere separate perhaps for keyboard shortcut hints that might pop up, essentially trying to avoid having them compete for the same space on the screen. Q05) What are we doing to support non-1080p resolutions? Many Citizens have 21:9 or wider monitor resolutions. [17:15]
Zane says that part of the issue is that the UI is currently very static. They're developing the ability to have flexible layouts, and those could potentially resize depending upon the aspect ratio of the Player's monitor, so that everything remains visible on the screen. The challenge though is that things are also in-world, such as the MobiGlas, which could be scaled, and also Field of View changes although FoV is something they're still looking into in terms of getting it all to work. Ultimately it comes down to prioritisation, and unfortunately making sure the UI works well with wider monitor resolutions isn't a priority right now. Q06) Are there any plans to add keyboard integration for navigating the various interfaces we encounter, so that it's not restricted to the mouse? (i.e. being able to use the arrow keys to scroll up and down on something like a kiosk screen [19:40]
They want to design their UI so that it's much more keyboard-friendly. Right now you can only use the mouse, which is rubbish, because using the keyboard can at times be faster. They add that making the UI more keyboard-friendly can simplify it, which is generally good because then it's more likely to work well across other input devices too, such as a gamepad. The MFDs should be the first bit of UI to feature the more uniform control method that caters for most people. Q07) In a previous show they mentioned that they were moving away from the Flash and Scaleform stuff for HUD UI, in favour of a homegrown solution. What progress have they made with this? [22:18]
(Scaleform is a game implementation of Flash - Chris talked about this earlier this year, which was my first summary. Go here: https://www.reddit.com/starcitizen/comments/b75cw3/a_summary_of_rtv_all_about_alpha_35/ then scroll down to [UI]
) TL;DR They still use Flash, but are working towards transitioning away from it, where instead they'll use their own code in a data-driven system. They still use Scaleform, but only for rendering, and that too will eventually be replaced with their own code. Moving away from Flash and Scaleform makes it quicker and easier for them to develop UIs, because Flash is outdated, time extensive, and it makes iterative development difficult due to not being able to see how something looks in-game as they're working on it.
They used Flash and are still using it now, but they're trying to transition away from it by baking their assets into a much more data-driven system. Previously in Flash, you set things up in a static way where you can't see how it looks in-game until you export it and reload the editor. With the data-driven system, the interface with the game code is much more simplified, and they have a standard API so that a task such as creating UI for an ammo counter is really simple and updates live. This means that they can be in-game and have an editor open and work on the UI at the same time, to see what it looks like as they work on it. It's still using Scaleform as a renderer, meaning that they've cut out the process of authoring the UI in Flash, but they're still using Scaleform to draw the vectors but only for that rendering task, and the rest of the work is done by their own code instead. At some point though, they'll build their own render to replace Scaleform. Jared jokingly asks Zane how long he's been waiting to kill Flash, who says he's been waiting since he started working at the company, 6+ years ago (for those who many not know, Zane was an early hire straight out of college and originally worked in the Austin office, which back then was just a house, and this was also during the days of Wingman's Hangar
). Simon adds to the discussion by explaining that Flash was originally designed as an animation system for web stuff, so it can be used for things like UI but it's hard to do iterative work with it where things change based upon feedback, which is because it's time extensive. Conversely, with the building blocks stuff it's quick and simple and they have a lot of control. Zane goes on to say that that's also true because it's a fully data-driven system, so the UI is programmatically drawn and driven from data so they don't worry about artists stepping on each others toes, because the changes the artists make can be merged together. Q08) Has there been any discussion about adding a compass ribbon, giving us cardinal directions on planets or moons? [27:24] TL;DR There's no outright yes-or-no answer. It's something they may consider, but it's also possible that there are other solutions to the problem, such as a personal radar on the visor HUD. They recognise though that having a compass would require being able to set magnetic poles on the planets, and for the compass to then be able to access that information and display it, which might not be so simple due to the procedural nature of the planets.
According to Simon, this is another situation where you need to understand the reason for wanting it, and that there may be other ways of solving the problem without creating a compass widget. He suggests that a personal radar or mini-map could show the Player their direction. However, he says that as they revise the visor HUD (which they're starting at the moment) if it seems that a compass is necessary then they'd consider and investigate it. Zane adds that it's not out of the question, but they would need a way to define what's North/East/South/West on these procedural planets, with Jared suggesting they'd have to be able to create and position magnetic poles. Simon suggests that some sort of Sat-Nav system may also solve the problem. Jared adds though that implementing a compass ribbon would be more than just UI work anyway, as it would need to involve system design.
(it seems odd to me that they don't seem to recognise the value of having a compass, particularly for FPS situations where it can be incredibly helpful to be able to say "contact at 220" and for other Players to be able to quickly identify the location of those hostile targets - of course, if it's just not possible then okay fine, but perhaps then there might be partial solutions instead, such as a compass that Players would have to manually adjust per Planet/location
) Q09) Is it possible to have a button to hide/toggle the HUD? (such as for taking screenshots) [30:05] TL;DR They imply that it's possible, and say that as they're going through the different UIs, they'll also end up improving the Director Cam system, and so they'll look into including a way to toggle on/off certain bits of the UI, if not all of it. They reiterate though that they really only want UI information that's relevant to the Player at that time to appear on the screen, with the rest minimising or disappearing until they're needed again.
They get a lot of Developers asking about how to do this. Zane says that as they overhaul their UI, they'll be improving the Director Cam system, so it's something they'll take into account at that time, especially since it'd also be helpful for the Devs. He suggests though that it could go further, such as being able to choose what you want to hide, like only the visor HUD, or maybe to hide all of the UI but not what's in the environment that brings it to life - like "background fluff screens". Simon adds that for the general UI, especially the visor HUD for FPS gameplay, they want to have a system which only shows you the UI that's relevant for you at the time, so if you put your weapon away you wouldn't need to see the weapon UI in the corner of your screen, or maybe you wouldn't show Health unless you get injured. This kind of work, which will result in only showing things when they're needed, should also help to de-clutter the screen. Q10) Are there any plans to allow a Chat UI to be viewed when not wearing a helmet? (such as through a contact lens or something) [32:13]
Yes. It's vital to always be able to see the Chat in a multiplayer game, and they do have plans for it to be visible almost all of the time, even potentially in third person, and they'd "like to have that in sometime soon". Q11) What progress have they made on the interio3D/mini-map? [32:59]
They have a developer version that's kinda halfway there at the moment, but fairly recently they made a decision to focus on getting the ship HUDs and the FPS HUDs sorted out first, because they're more integral to the overall gameplay and therefore they want to make sure they get them right and working well. After this, they'd then go back to the area map stuff, which will hopefully be "really soon". Simon clarifies that there'll be a full-screen version where you can look around the whole area, and a mini-map for the visor, which will be particularly useful when exploring interiors. Q12) Why does Quantum Calibration mode, Scanning mode, Mining mode, and any other sub-UI mode, take away or hide crucial flight information such as speed and altitude? [34:28] TL;DR Essentially they were developed separately, and it wasn't their intention for crucial flight information to be removed when using those modes. Whilst they don't say it specifically, the new UI tech will help them to make sure that that information the Players need will be there, due to it being data-driven rather than a static UI.
They were basically developed under the hood as "different contexts", and in their overhaul of the design they're factoring in all of the flight information so that it'll be available to Players regardless of what mode they're in, because it's still relevant when they're still flying, and therefore the information should be retained. In these modes referenced in the question, they're looking at potentially contextually changing out the "screens of cells" so that rather than the HUD changing for the different modes, they can shift elements around so that relevant information can still be displayed, rather than the new HUD for that mode just taking up the whole screen. Jared adds that it wasn't intentional to take away crucial information when using these modes, and that it's just something that's happened over the course of development that needs resolving. Simon adds that sometimes you don't realise it's going to cause issues until you try it, and this is one of those situations. Jared goes on to say that things can be developed in isolation, and then when they're integrated together into their game-dev branch, that's when they can see collisions and thus the creation of bugs. Q13) Are there any updates regarding their plans for the landing UI improvements which are needed for the implementation of Hover mode? [36:45] TL;DR The previous UI they had implemented, typically seen prior to 3.0, used a different renderer (3Di) and now they use Render-to-Texture. As a result, it's not long compatible. They need to recreate this landing UI, but they're busy focusing on the MFDs right now, and they recognise they'll probably need some other stuff, such as a guidance system and AR elements
A while back they changed the method that they used to render the UI, from what was called 3Di to Render-to-Texture, so now it's actually rendered as part of the screens and can be affected by post-effects. The original landing UI replaced the radar, which was built using 3Di and therefore wasn't compatible with Render-to-Texture, and that's why it was removed. They're now looking at bringing it back in some way, but maybe with a better design (this was a bit confusing, regarding whether Zane meant that the "original landing UI" or the "radar" was built using 3Di. I think all he's getting at is that the 3D representation we had pre-3.0 that was used for landing, was built using 3Di but wasn't compatible any more when they switched to RtT - this was addressed in Q03 of the previous episode of SCL. Here's my summary for that: https://www.reddit.com/starcitizen/comments/ca7xxy/a_summary_of_star_citizen_live_all_about/
). They're focusing on the structure and the layout of the MFDs right now, and also recognise potentially needing some sort of guidance system, as well as having some Augmented Reality elements that are displayed in conjunction with that. Q14) How do they intend to improve the legibility of UI elements that tend to sit over the environment, which can be very glaring, making the UI hard or even impossible to read? [38:15] TL;DR The solution they're aiming for involves keeping the UI in-world. They'll have the UI displayed on geometry, and then that geometry can be dynamically tinted depending on the environment. At the same time, the text/info can be dynamically brightened to make sure it's still readable. They may also be able to use some sort of effect to achieve the same kind of goal, such as a blurred frosted glass effect. They can consider a back-shadow or black highlight, but they're concerned that it will conflict too much with their aesthetic aims.
They're looking at a few in-world solutions. The obvious thing to do is to add a drop-shadow to the UI or just make it black, but that somewhat destroys the aesthetic of it. So what they're looking at, which they started looking at with the Gladius but isn't finished yet, is having a system where it's contextually and dynamically reading the brightness of the environment and adjusting the brightness of the UI in response to that. Additionally, to make sure the HUDs look like they exist in-world, they want them displayed on actual geometry to ground it, and they can leverage that to maybe dynamically tint the geometry that the UI is on, as well as then brightning the UI if needs be (depending on the environmental conditions). This solution is ideal because of being in-world (and thus not hindering immersion) but also because it leverages the in-game elements, making it more convincing. Jared asks for clarification, and Zane specifies that it'd involve tinting the physical glass pane but then also brighting the UI, like if you have your phone on automatic brightness and go outside into the sunlight, it'll auto-adjust to make it more readable (This is a thing?! My phone must be old
). He adds that it's also an issue with the eye adaptation feature (where the Player's "eyes" adjust depending on how bright it is), because the UI becomes dim when you're on a planet during the daytime, as compared to being lit by the sun in space. They could potentially also have some sort of effect in the UI rendering tech, such as a blurred frosted glass effect, that could help with readability (particularly for the visor HUD in your helmet), and the same is true for busy backgrounds and not just bright ones. Regarding a potential back-shadow, or a black highlight around the words and numbers on the UI (as often suggested by backers) it's definitely something they can consider but it'll depend on how subtle it can or can't be to work, because that might not fit with the aesthetic they're aiming for, which would therefore require them looking for a different solution. Simon adds that as with a lot of the UI, they'll concept different ideas to figure out which is the best way to solve the problem, before committing to implement something. Q15) Currently the MFDs on ships have a default configuration that must be changed each time the pilot enters the pilot seat. Are there intentions to add the ability to save MFD configuration presets of an individual Player's preferences? [43:24]
TL;DR Yes, and this is something that has to persist. The work they're doing on the MFDs will require them to load their state from something like an entity or the server. They're hoping that by the time they're done with the MFDs, that info will be available in those places (likely the server). They'll also be redesigned to have the most important information displayed by default, and hopefully it'll be possible to create and save presets for quick activation.
Yes, that's got to persist at some point, and the issue right now is just that it doesn't. In their new UI tech, the UI will be what they call "stateless", meaning it won't store any state about itself and instead takes everything from an entity or from what's on the server. As such, when they develop the MFD or implement the new design they're working on, they hope they'll be able to persist the current state of the MFDs as they were before the Player exited the seat/cockpit, even if the Player had changed tabs or moved things around. Simon adds that when they do this pass on the MFDs, they want to make sure that the most important information is shown by default, so hopefully there'll be less need to change things around. Zane adds that potentially they'll also be able to make it so that presets could be created, saved, and then activated quickly (he actually just said the "activated" part but that implies creating and saving presets
). Q16 ) Is there anything they can tell us about the ongoing process of refactoring the ship MFDs? [45:45] TL;DR They want to move to a system where, when you're looking forwards, the MFDs will display a minimal configuration of information that is readable and useful whilst you're flying, but then they can show more in-depth information if you specifically focus on the screens. Additionally, the new UI tech they're developing (as part of moving away from Flash and Scaleform) will allow them to have just one binary file that they need to make changes in, which makes it easier to maintain the UIs.
Right now the MFDs are small, scaled down, and not readable. Previously they used to have what they called "support screens" which were screens with minimal information on them, with a font size that made the information more legible. They're looking to have a system where by default, the MFDs will be in this minimised configuration where they only show the information that you really need to know, and they do so in a way that's readable without focusing on the display. However, when you then focus on the display, they want it to contextually change to something more in-depth, which can work because now the MFD has more screen-space to show readable information. Zane adds that the cool thing about the UI tech he's helping to develop, is that they're taking cues from web development (which is also his background so he knows a lot about it) where there's a thing called "responsive design". This is where you can have a rule set up so that, if there's a box in their UI that goes beyond a certain point, it then shrinks down, and you can have different styles applied to that, and conditionally so depending on the size of the box. As such they're leveraging that to help with the reformulation of the UI on screens, and it could also be helpful when they potentially implement customisation of HUDs/UIs as a tool to manage and maintain it. Right now in-game they have different sized screens, where each size has its own binary file, meaning that if they want to change one then they have to go into each binary file and make a change. But if they can maintain just one UI, which then has different style rules applied to it, then that makes it much easier to maintain. So changing one thing would then make that change for each different manufacturer, and every kind of configuration. Simon adds that regarding the actual process right now, they're looking through the designs that already exist in-game and working closely with the vehicles team to figure out what they want to show on the screens, to plan out what's going to be in all of the MFDs, so that they can then redesign each screen to achieve its maximum potential based upon what information needs to be shown. After that, the UI tech will eventually reach a point where the screen's are redesigned and the tech's ready to be put into the game. Q17) Currently Players have to go to a kiosk to view the cargo inventory for their ships. Are there any plans to implement some sort of on-ship cargo UI so that Players can view their cargo inventory without finding a kiosk to do that? [50:18]
It's something that they will look at; they know that it's needed. What they're unsure of is when they'll get around to doing it (again, it comes down to prioritising and there'll be higher priorities right now, such as the HUD reworks they've extensively talked about so far
). Q18) Are there any plans to allow Players to prioritise the use of missiles or torpedoes through the MFDs? [50:58]
This is another thing they're going to look at. They're under the impression that they had this functionality previously, but it later broke. Simon adds that the UI does currently support this functionality, but that there's some refactoring that needs doing to get the weapons to "match up". It's something they want to do, which will be possible in the future, and with a better design. Q19) Are there any plans to allow Players to see Points-of-Interest in other UI modes? Right now they're only view-able in the Quantum Drive mode. [51:41]
It's something that Simon's interested in doing, although he says it relates back to how they're going to manage what information is being shown, when it's being shown, and how. If they get to a point where the on-screen icons have been cut down to a sensible level, then they could consider whether it's worth having PoIs visible in other modes as well, and thus it'd be something that's worth having them look into. He says it's definitely the sort of thing you'd want to try out as you're developing it so that it can be iterated upon. Q20) Would it be possible to have an ETA marker to show when a ship in Quantum Travel will arrive at its destination, rather than just showing the remaining distance? [52:26]
They think that this is a good idea, and so they'll be looking into it. Zane adds that they have an ETA for when a Player's Oxygen runs out, so they should be able to have one for QT.
(side note: shouldn't Oxygen/O2 in-game be Air instead?
:thinking: ) Q21) How do they feel about the current implementation of the Inner Thought system, and are there any plans to continue iterating on it? [53:07] TL;DR There's an issue where the Inner Thought system displays text when it's not necessary to do so, such as you're using an airlock and the text that exists on the console then also appears in the form of Inner Thought - this is unnecessary and needs to be resolved, which it soon will be thanks to their new UI tech. They'll also eventually revisit the visuals of the system, to make it look as good as possible. They also hint again that there's some UI WIP that isn't ready to show yet, but might be shown in a Q3 ISC episode.
Zane says that there are situations where the Inner Thought text appears when it shouldn't, such as over screens. A good example of this is when a Player is in an airlock and goes to use the console, and the Inner Thought text then appears over the console despite that same information already existing on the console (it's the same thing as when the door panel reads "Open" but then when you go to use it, the Inner Thought text appears on top of that as well
). Their UI tech now allows for not having the IT text appear, which is particularly useful for things like elevators where the required information can be on or next to the buttons, without needing to use Inner Thought. They'll also be looking at the visuals of Inner Thought too, because although it looks okay now they feel it could be better. On a similar note, there's some other work they're doing at the moment on interactions that they're still figuring out, but it's something that's not quite ready to show just yet (Jared already said in the answer to Q03 of this episode that the Q3 ISC episodes will include some more looks at ongoing UI work, so it's possible that this will be shown as part of that
). Q22) A long time ago they talked about the potential of manufacturer-specific UIs. Is that still the plan? [54:39] TL;DR Yes it is, and their new UI tech makes it even more possible, because it'll mean they don't have to have a binary file per manufacturer, but just one binary file for everything. They then have a "style sheet system" which allows them to have a white box outline for UI, which can then have different designs applied to it, and is a lot more simple than what it would otherwise be if working with Flash. They also talk about investigating the possibility of creating 3D UIs, which will mostly be used for the more advanced ships, like those from Origin or MISC.
Yes, and it's much more possible now with the UI tech because they have a "style sheet system". Previously (or currently?
) this would require having a binary file for each manufacturer, which would be a pain to maintain, but the new UI tech (as mentioned previously) will allow for only one file so that only one change would need to be made to affect everything across the board. Zane explains further that the style sheet system is kind of like having a white box outline which can then have a visual description defined and applied to it, and changing between the different styles is simple because they can just use a drop-down menu to switch between manufacturers, and then see the visual description change between them. Simon adds that once the system is in place it gives them more opportunities to hand it over to the graphic designers who can create really nice designs which would then be a lot easier to just drop into the game, as opposed to being dependent on someone going into Flash and knowing how to code within Flash. Zane adds that with these style rules there are a lot of possibilities to differentiate between manufacturers, but also there are ways to do this through changing the layout, such as Origin and MISC having more holographic UIs. They're also investigating the initial engineering requirement to make it so that they can have 3D UIs as well, which would make holographic UIs look even more holographic. This would be particularly good for the more advanced ships, rather than the more retro ones. Zane comments about how right now every ship just has the retro UI, and that they want to significantly differentiate between the different tech levels of ships. Q23) The responsiveness of the MobiGlas can sometimes be a little slow. Is this an engineering problem? A UI problem? Something else? [58:18]
Zane reckons that the time it takes for the arm animation to play, as well as how long it takes for the MobiGlas to boot-up, could be reduced, but they're not focused on MobiGlas at the moment. He does reiterate though that they're looking to overhaul the whole UI (which would most likely include the MobiGlas). They've just got to set a target time for how long it should take between the Player pressing the button to open the MobiGlas, and the MobiGlas being open and ready to use. Simon adds that because the MobiGlas is supposed to be a holographic display, they could have that display start to show before the Player's arm has finished moving. Q24) Is there anything you can tell us about the future of MobiGlas? (despite it not being the focus right now) [59:36]
It's kinda similar to what they're doing with the ship MFDs. Once the ship and visor UIs are done, they'll probably look at the MobiGlas, and part of that will likely involve talking to the game designers to make sure that the MobiGlas works as is needed, and they can also incorporate the new tech at the same time. It's due an overhaul though, and Simon's looking forward to it. Zane adds that because the MobiGlas is 3D, it also depends on the UI tech being able to do 3D UIs as well, which will need to be sorted out before they can make the MobiGlas holographic UI 3D. Q25) Is the UI team hiring, and what skills are needed most? [01:00:57]
Yes. The job specs on the website are slightly out of date though and they'll update them soon. They're looking for at least a programmer. They're not currently looking for artists and graphic designers, but that could change in the future. For programmers, the essential things they're looking for are an ability to show experience, and having a knowledge of what makes good UI, such as why things work in other games. For artists they look at a lot of graphic design work because of how relevant that is to UI work, but they also look for an understanding of why a particular screen might be good on a particular app, or how it could be improved. Zane adds that it'd be helpful to have a tools programmer as well. He goes on to say that because the UI is becoming data-driven, that means they're actually dealing with a lot of raw data. As a result, they need to create a UI Editor that the designers and artists will interface with, which would need to be intuitive and easy to use, so a tools programmer that could help with that would be very handy.
Here's a link to CIG's Jobs page: https://cloudimperiumgames.com/join-us
- - - - -
The End. This one's a little later than usual 'cause I've been busy and shit. I wasn't even sure I'd get it done for today so I'm glad it worked out.
As always, I hope you all like this summary. Remember to be kind to each other, and I'll see you with the next one.
United States v. Lee Elbaz Court Docket No.: 18-cr-00157 (D. Maryland) the former CEO of the Israel-based company, ” services for two websites, known as BinaryBook and BigOption, that were used to promote and market purported binary options, and that those binary options were fraudulently sold and marketed. Binary.com gives everyone an easy way to participate in the financial markets. Trade with as little as $1 USD on major currencies, indices, commodities, and synthetic indices. Binary.com is a United Kingdom-based financial services company that specializes in binary trading. Through its platform, the company allows users to trade binary options 24/7 and connect with the world’s best financial markets. The company was established in 1999 and has grown to add to its website the ability for customers to trade The former CEO of the Israel-based company Yukom Communications, a purported sales and marketing company, was found guilty yesterday for orchestrating a scheme to defraud investors in the United States and worldwide by fraudulently marketing approximately $145 million in financial instruments known as “binary options.” Welcome to the free List of Best Companies for Flexible Bilingual Jobs! Based on years of researching companies that hire for remote, part-time, flextime, or freelance jobs, FlexJobs has compiled and made public a list of 100 of companies that specifically have hired for Bilingual jobs with at least one of these flexible working options.
The largest collection of binary options brokers. http://binaryoptionsbonusguide.com/ For those who reside while in the US, or Even though you undoubtedly are a US citizen residing elsewhere on the planet, you should constantly select a US-based binary options broker for the ... For those who reside while in the US, or Even though you undoubtedly are a US citizen residing elsewhere on the planet, you should constantly select a US-based binary options broker for the ... Nadex is the leading US-based CFTC-regulated financial exchange for binary options and option spreads. We’re located in the heart of Chicago’s financial district. Subscribe to learn more about ... Nadex is the leading US-based CFTC-regulated financial exchange for binary options and option spreads. We’re located in the heart of Chicago’s financial district. Subscribe to learn more about ...