0x010088F6312065A70A44B630A6848498EAD80093CFEAFE161DC94D83C7C5C9A5A748B8

In the previous iteration of the course it was 10 points. Given the course has shrunk to 7.5 the student felt that some of the more advanced content needed to be removed to focus on the core of game development. The content was reduced and there was more direction given on the collaboration tools to use.

The students felt the course learning outcomes were up-to-date and "They are generally fairly well communicated in the lectures, but since such a large part of the course is the self-managed projects, some of them (especially WRT architecture, testing, etc) can get lost during this process"This could be improved by linking the projects more tightly so that students are more in sync when it comes to what they current need to learn.The type of learning activity was good but "More coding-focused lectures feel a lot less useful for groups using non-Unity engines - the principles are often covered in previous courses, and the implementation being shown feels almost more relevant, but only WRT Unity" This suggests that we should focus on a single game engine. Allowing choice is good, but comes at a cost of detailed examples often not being quite aligned. The course was seen as research based "Got a great demonstration of Github CoPilot" but there was a lack of feedback.The course need to have a tighter feedback look so that students can see their progress towards the learning outcomes. The student impression of the effort and motivation was "Fun Course +1;I think the course is great!; It’s pretty fun; As with all group projects, it varies from student to student +1" The students felt the area of improvement were:<ul><li>"Decide on one game engine that everyone should use</li><li>because you cover engine specific things in lectures</li><li>with all groups using separate engines, the “learning environment” (for code) is really youtube and google</li><li>our group feels Godot was the best choice for our game, but we have discussed regretting picking it anyway because we feel that we would get more out of the teaching by using Unity even if it would be less suited for our game"</li></ul>These comments clearly show that the students want the course to focus on a single game engine to allow focus on the core learning outcomes, which currently is slightly diluted by the challenge of working across multiple game engines. The students were well engaged in Discord during the semester. They all produced good games which were playable, unlike some of the previous years. The student worked hard and the comments from their learning reflections at the end of the course indicated that they had developed the intended knowledge from the course.

The students were asked as part of the final report to give an evaluation of the course and talk about what the most important lesson. There were many comments talking about the group work and the challenge, and benefits of working in groups. Of the 5 groups 2 had challenges, however the groups all completed a playable game and there were lessons learnt on how to move past difficulties in teams. These lessons may not be core to game development but they are significant in the students development as professional developers.

NTNU:TIA:REST

Institutt for datateknologi og informatikk

Department of Computer Science

Engelsk

Anbefalte forkunnskaper

<a href="http://www.ntnu.no/studier/emner/PROG2051/2020</href></webLink><a href="http://www.ntnu.no/studier/emner/PROG2051/2020">PROG2051</a> Kunstig intelligens

Mer om vurdering

Forkunnskapskrav

Faglig innhold

Kursmateriell

Læringsformer og aktiviteter

Læringsutbytte

Spillprogrammering

Informasjonsteknologi og informatikk

Bachelor i ingeniørfag, data

Bachelor i spillprogrammering

Bachelor i programmering

Web/Lists(guid'8b698a2d-6ad0-4f7d-b3be-219cc1979f02')/Items(14019)/FieldValuesAsText

Spillprogrammering - IMT3603