Problemen en beperkingen IDT We he

Problemen en beperkingen IDT
 We hebben slechts 1 Kaart ter beschikking om Scenario’s aan te maken
 Voertuigen en andere Items zijn beperkt (beperkte bibliotheek). Zie bijlage1.
 De 3D view werkt niet in VR forces ( we krijgen enkel balken te zien, hierdoor zijn we verplicht telkens over te gaan naar de SA software om te testen hoe onze objecten eigenlijk geplaatst zijn). Zie bijlage 2.
 Het gebeurt soms dat als we Vtg een bepaalde opdracht laten uitvoeren één type van Vtg dit zonder problemen uitvoert terwijl met een ander type Vtg dezelfde opdracht niet kan uitgevoerd worden (zonder dat wij hiervoor een logische oorzaak terugvinden).
 Maximum snelheid van 20 Km/Hr voor OpFor Vtg ? Volgens mij kunnen gepantserde Vtg vandaag hogere snelheden behalen (dit is een persoonlijke opmerking).
 Bij het uitvoeren van de scenario’s op de leerlingenpost gebeurt het wel eens dat er zich haperingen voordoen (zie later). Het merkwaardige hierbij is dat bij uitvoeren van identieke scenario’s op twee leerlingenposten er bij één post zich geen problemen voordoen terwijl op de andere post die problemen zich wel voordoen. Ook hier is er weer geen verklaring of oorzaak te vinden.
 Usermanual IDT die wij hebben is te beknopt wat betreft informatie voor het werken met VR-forces. Zo staat er in de inleiding bijvoorbeeld dat “ niet alle opties vermeld in de gebruiksaanwijzing van VR-Forces worden ondersteund in deze versie van de VR-Forces software” maar welke functies of opties niet ondersteund worden wordt niet beschreven. => dit is te vaag, waarom hebben we geen manual die volledig bij onze configuratie past?
 De help button bij VR-forces werkt niet. Dit zou nochtans een handige tool kunnen zijn (zie bijlage 3).
 Indien we zelf vegetatie plaatsen of gebouwen plaatsen in een scenario worden de labels in de SA-software onleesbaar (zie bijlage4).
 Bebouwing en agglomeratie van de kaart kunnen niet gebruikt worden in de scenario’s ( zie bijlage 5).
We hebben vastgesteld dat er soms haperingen zijn ( info van de monitoren die onze systemen gebruiken maar soms ook door ons zelf vastgesteld). Hieronder de meest voorkomende:
• Relock na Lockverlies vele malen niet mogelijk ( probleem enkel op te lossen na opnieuw opstarten scenario en/of het programma SA run SPIKE)
• LP (lock prediction op de TS thermal sight) activeert niet altijd, soms moeten ze de hoofdschakelaar terug op Stand By zetten en dan terug op ON waarna de LP wel weer correct werkt.
• Verspringen van het beeld (moeten target dan opnieuw opsporen).
• Vastlopen van programma

Results (English) 1:

Problems and limitations IDT We only have 1 card at your disposal in order to create Scenarios vehicles and other Items are restricted (limited library). See Annex1. The 3D view does not work in VR forces (we get to see, as a result, we only bars compulsory each time to move to the SA software to test how our objects actually posted). See annex 2. It happens sometimes that if we perform a certain task one type of Vtg Vtg run this without problems while not the same command with a different type of Vtg can be performed (without a logical cause found). Maximum speed of 20 Km/Hr for OpFor Vtg? I believe that armored Vtg today achieve higher speeds (this is a personal note). When running the scenarios on the students post it happens sometimes that there are hitches occur (see later). The curious thing is that running identical scenarios on two students posting one post is no problems while on the other post that problems occur. Here, too, there is again no explanation or cause. User manual IDT we have is too brief as regards information for working with VR-forces. So does the introduction, for example, that "not all options listed in the instructions for use of VR-Forces are supported in this version of the VR-Forces software" but which does not describe features or options are not supported. = > This is too vague, why have we not manual that completely fits our configuration? The help button at VR-forces does not work. This would however a useful tool (see annex 3). If we ourselves vegetation places or buildings in a scenario, the labels in the SA-software unreadable (see bijlage4). Development and agglomeration of the card can not be used in the scenarios (see annex 5).We have found that there are sometimes hitches (info from the monitors that use our systems but also sometimes adopted by ourselves). Below are the most common:• Relock after Lock loss many times not possible (just to solve problem after restart scenario and/or the program SA run SPIKE)• LP (lock prediction on the TS thermal sight) not always, sometimes they need to activate the main switch back on Stand By and then back to ON after which the LP again works correctly.• Long jump of the image (must target again detecting).• Stranding program

Results (English) 2:

Problems and limitations IDT
 We have only one map available to Scenario 'to create s  Vehicles and other items are limited (small library). See Annex 1.  The 3D view does not work in VR forces (we only get to see beams, thus we are obliged to always move to the SA software to test how our objects are actually installed). See Appendix 2.  It sometimes happens that when we Vtg allow a specific assignment to perform one type of Vtg this carries no problems while with another type Vtg same command can not be executed (not that we find this a logical cause).  Maximum speed of 20 Km / Hr for OpFor Vtg? In my view, armored Vtg today achieve higher speeds (this is a personal observation).  In conducting the scenario 's on students post it happens sometimes that there are hitches (see later). The odd thing is that when performing identical scenario 's two student posts, with one post there are no problems while on the other post that problems do occur. Again, there will be found no explanation or cause.  User Manual IDT that we have is too short in terms of information for working with VR - Forces. So in the introduction, for example, that "not all of the options mentioned in the manual of VR - Forces are supported in this version of the VR - Forces software" but what features and options are not supported is not disclosed. => This is too vague, why we do not have a manual which completely suits our configuration?  The help button at VR - Forces not working. This however would be a useful tool (see Appendix 3).  If we ourselves put vegetation or structures in a scenario, the labels in the SA be - software unreadable (see bijlage4).  Construction and agglomeration of the card can not be used be in the scenario 's (see Annex 5). We found that sometimes there are glitches (info from the monitors that use our systems, but sometimes defined by us). Below are the most common: • relock after Lock lose many times not possible (problem only resolve after reboot scenario and / or the program SA run SPIKE) • LP (lock prediction on the TS thermal sight) does not always triggers, sometimes they need the power switch, reset Stand By and then back ON after the LP is working correctly. • Skipping the image (target should then detect again). • Hang program

Results (English) 3:

problems and limitations  idt (we have only one card in order to make the scenarios to  vehicles and other items are limited (limited library). see bijlage1.
 the 3d view works in vr forces (we only get to see beams, this time we have to go to the sa software to test how our objects are actually placed). see annex 2. " it sometimes happens that if we perform a certain task vtg one type of vtg without problems while performing with another type vtg the contract cannot be performed (without that we find a logical reason ). the maximum speed of 20 km / hr for opfor vtg?i can achieve higher speeds armored vtg today (this is a personal note). the  in implementing the scenarios on the leerlingenpost will agree that there are problems occur (see later).the strange thing is that to perform identical scenarios on two leerlingenposten in one post has no problems while the other post problems will arise. here too there is no explanation or cause to find  usermanual idt. "we have to brief on information for working with vr forces.in the introduction, for example, states that "all options specified in the instructions for use of vr forces are supported in this version of the vr forces software" but what functions or options are not supported is described. = > this is too vague, why have we not fully fit in our manual configuration. the help button in the  vr forces doesn't work.however, this would be a handy tool (see annex 3). "if we  vegetation places or buildings places in a scenario, the labels in the sa software (see bijlage4 illegible). the  cultivation and agglomeration of the card can not be used in the scenarios (see annex 5).
we have found that there are some problems (info of the monitors our systems use but sometimes also established by ourselves). below are the most common:
(relock after lockverlies many times as possible (problem solving scenario after reboot and / or run the program sa spike) (lp (lock prediction on the ts thermal sight) activates not always.sometimes they have to switch back to the standby, and then back again on the lp and working properly. "the change of the image (to target detection (again). the end of programme.